https://bugzilla.redhat.com/show_bug.cgi?id=2389767
Bug ID: 2389767
Summary: The brise package is deprecated upstream since 2018
and providing outdated data files for ibus-rime,
fcitx5-rime etc
Product: Fedora
Version: 42
OS: Linux
Status: NEW
Component: brise
Keywords: Desktop, RFE
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: alt.euyis(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Per the readme file in the upstream repo
(https://github.com/rime/brise/blob/master/README.md) brise is deprecated and
the last release version of 0.38 dating back to 2018 is still being served as a
dependency package for Rime front-ends in Fedora (ibus-rime, fcitx5-rime, etc).
As the schema files in the package are essentially what actually provide the
user-facing input features of Rime, the fact that they are several years
outdated when newer, current version are available with updates & bug fixes are
readily available is clearly not ideal. In fact, this bug report is prompted by
me running into an upstream bug (https://github.com/rime/home/issues/831) that
was fixed all the way back to 2021 yet still present Fedora 42, due to the
schema files being stuck in 2018.
Would it be possible to either update the files provided by the brise package
to the latest versions available, or move them to a new dependency package for
Rime front-end packages, since a update version would clearly not be
specifically brise anymore so the name would be misleading in that case?
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2389767
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2422135
Bug ID: 2422135
Summary: [abrt] ibus-typing-booster: Py_Exit(): python3.13
killed by SIGABRT
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:1016fbf3f898a8e267bb35897e7a7417c6d30f73;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: htl10(a)users.sourceforge.net
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
ibus-typing-booster seems to often crash on gnome-shell logging out, and
crashes gnome-shell on the way too.
Version-Release number of selected component:
ibus-typing-booster-2.28.6-1.fc42
Additional info:
reporter: libreport-2.17.15
executable: /usr/bin/python3.13
rootdir: /
kernel: 6.16.8-200.fc42.x86_64
journald_cursor:
s=d85d4e6a420649199e9c9ed3c18b1efe;i=92a38d;b=d547d11eb0634f1fa7e01d689bbad122;m=50aa753cbc;t=645f2872f7a59;x=86672d859f327ae2
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
runlevel: N 5
uid: 1000
backtrace_rating: 4
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
type: CCpp
reason: python3.13 killed by SIGABRT
package: ibus-typing-booster-2.28.6-1.fc42
comment: ibus-typing-booster seems to often crash on gnome-shell logging
out, and crashes gnome-shell on the way too.
crash_function: Py_Exit
Truncated backtrace:
Thread no. 1 (4 frames)
#5 Py_Exit at
/usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pylifecycle.c:3523
#6 handle_system_exit at
/usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:679
#7 _PyErr_PrintEx at
/usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:688
#8 PyErr_PrintEx at
/usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:768
Potential duplicate: bug 2185830
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2422135
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Bug ID: 2395836
Summary: don't combine pinyin Chinese IME and bopomofo Chinese
IME into one single package
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-libpinyin
Keywords: Desktop, RFE
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: lutingrong(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Hello the authors of ibus-libpinyin ,
I'm using ibus-libpinyin on fedora 42 . I found ibus-libpinyin provides both
pinyin Chinese IME and bopomofo Chinese IME . Could you please consider split
ibus-libpinyin into ibus-libpinyin and ibus-libbopomofo ? The reason is that
those who use pinyin IME doesn't know bopomofo IME at all , and vice verse
those who use bopomofo IME doesn't know pinyin IME neither . So I can install
only the package which I use . Why must combine pinyin IME and bopomofo IME
into one single package ? Most hope there is no unnecessary codes in their
computers . Hope ibus-libpinyin more modularized and more divided ! Thanks for
your time and consideration!
Best regards,
Tingrong
Reproducible: Always
Steps to Reproduce:
1. sudo dnf install ibus-libpinyin
2. ibus-setup
3. will see there are both pinyin Chinese IME and bopomofo Chinese IME
Actual Results:
one single package -- ibus-libpinyin provides more than one IME .
Expected Results:
one package provides only one IME .
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2395207
--- Comment #1 from Fedora Release Engineering <releng(a)fedoraproject.org> ---
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on
2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
'version' of '42'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora Linux 42 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2395207
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2372839
Bug ID: 2372839
Summary: cinnamon-screensaver segfault with uim-1.9.6.
Product: Fedora
Version: 42
OS: Linux
Status: NEW
Component: uim
Keywords: Desktop, Upgrades
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: ta1yanagiya+rh(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Cinnamon-screensaver does not work after updating to uim-1.9.6.
The following logs are output to journal:
```
systemd[2183]: Started dbus-:1.2-org.cinnamon.ScreenSaver@3.service.
cinnamon-screensaver[5935]: CsNotificationWatcher: Could not add match rule to
bus - GDBus.Error:org.freedesktop.DBus.Error.MatchRuleInvalid: Invalid match
rule
cinnamon-screensaver[5935]: Loading AccountsService
cinnamon-screensaver[5935]: Fractional scaling active: False
cinnamon-screensaver[5935]: Trying to connect to logind...
cinnamon-screensaver[5935]: Starting screensaver...
cinnamon-screensaver[5935]: Cinnamon Screensaver support not found in current
theme - adding some...
audit[5935]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 pid=5935
comm="cinnamon-screen" exe="/usr/bin/python3.13" sig=11 res=1
kernel: cinnamon-screen[5935]: segfault at a6e ip 00007f27627571dd sp
00007ffdedc4a278 error 4 in libc.so.6[1491dd,7f276260e000+16f000] likely on CPU
5 (core 2, socket 0)
kernel: Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa
c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd
d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66
kernel: audit: type=1701 audit(1749905665.970:333): auid=1001 uid=1001 gid=1001
ses=3 pid=5935 comm="cinnamon-screen" exe="/usr/bin/python3.13" sig=11 res=1
(snip)
```
Reproducible: Always
Steps to Reproduce:
1. Log in to cinnamon session.
(The following versions)
uim-1.9.6-1.fc42.x86_64
uim-anthy-1.9.6-1.fc42.x86_64
uim-gtk3-1.9.6-1.fc42.x86_64
cinnamon-6.4.9-1.fc42.x86_64
cinnamon-screensaver-6.4.0-2.fc42.x86_64
2. Press Alt-Ctl-L.
Actual Results:
The screensaver does not work.
Expected Results:
The screensaver works.
Additional Information:
Cinnamon-screensaver works when downgrades to uim-1.8.9.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2372839
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…