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=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…
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
Bug ID: 2368622
Summary: ibus-daemon uses insane amounts of CPU and causes a
laggy experience
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Keywords: Desktop
Severity: high
Assignee: tfujiwar(a)redhat.com
Reporter: torvalds(a)linux-foundation.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Not a lot of details here, but I decided that instead of just fixing it with
killall ibus-daemon
which gets rid of that broken thing, I would at least open a bug report to see
if there is some official fix for this.
Google shows a lot of people complaining about this going back years, so it's
not me.
There's no crash, and no obvious system logs either. All I see in system logs
is gdm-wayland-session activating, and when I kill it systemd seems to log
consumtion information like
org.freedesktop.IBus.session.GNOME.service: Consumed 26min 22.196s CPU
time, 125.1M memory peak.
(That was after the system had been up for one day, so 26 min of CPU time seems
pretty excessive)
Reproducible: Sometimes
Steps to Reproduce:
1. Boot the system
2. Be happy
3. Some time randomly later, notice laggy behavior and ibus-daemon using 100%
CPU in top
Actual Results:
Slow keyboard response on a fast system
Expected Results:
Snappy action
Additional Information:
Sorry for the horrible bug report, but can we please just disable ibus-daemon
by default as a useless problem-causing thing?
When google shows this problem going back AT LEAST to 2020 (and probably
longer), with the solution invariably being "kill, restart or disable
ibus-daemon to fix the problem temporarily", why is that thing enabled by
default in the first place?
Please at least give a good setting for this, so that the answer can be for
people to not enable that thing.
And if somebody has "please debug this next time it happens by doing Xyz", I'll
happily do that. But you need to tell me what Xyz is, because I don't know the
first thing about ibus-daemon.
I know that the "i" is supposed to stand for "intelligent". But honestly, I can
come up with a lot better suggestions for what that "i" might stand for. And
absolutely *none* of them are polite.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
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=2364700
Bug ID: 2364700
Summary: [abrt] ibus: __strcmp_evex(): ibus-x11 killed by
SIGSEGV
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:184db64f4234731aa826b676bd01b8507c23e6da;VAR
IANT_ID=compneuro;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sanjay.ankur(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-1.5.32-1.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-x11 killed by SIGSEGV
journald_cursor:
s=facd15e04f384ea0b6e611e9078e70c2;i=92231f2d;b=34ca2973d2434e6f973add5fae86b10f;m=75f14af9;t=6347a7e580b45;x=3b76384ca1e0b033
executable: /usr/libexec/ibus-x11
cmdline: /usr/libexec/ibus-x11 --kill-daemon
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.14.5-300.fc42.x86_64
package: ibus-1.5.32-1.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: __strcmp_evex
Truncated backtrace:
Thread no. 1 (18 frames)
#0 __strcmp_evex at ../sysdeps/x86_64/multiarch/strcmp-evex.S:316
#1 g_str_equal at ../glib/ghash.c:2444
#2 g_hash_table_lookup_node at ../glib/ghash.c:442
#3 g_hash_table_lookup at ../glib/ghash.c:1488
#4 g_dbus_proxy_get_cached_property at ../gio/gdbusproxy.c:712
#5 ibus_input_context_post_process_key_event at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusinputcontext.c:1534
#6 _process_key_event_sync at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:638
#7 xim_forward_event at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:765
#8 ims_protocol_handler at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:1020
#9 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224
#10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1898
#11 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524
#12 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337
#13 gdk_display_get_event at ../gdk/gdkdisplay.c:442
#14 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
#16 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249
#17 g_main_context_iterate_unlocked at ../glib/gmain.c:4314
#19 ibus_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusshare.c:336
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2364700
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=2362429
Bug ID: 2362429
Summary: [abrt] ibus: g_hash_table_remove_all_nodes(): ibus-x11
killed by SIGABRT
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:6ef4db86fa264ddee0fbb467ca28f667a1602325;VAR
IANT_ID=workstation;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: wangxuke.china(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
input chinese in Intellij IDEA
Version-Release number of selected component:
ibus-1.5.32-1.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-x11 killed by SIGABRT
journald_cursor:
s=3c0dd3d416e941f6a30daef456f5e069;i=314c71;b=df414e19ee6c4d1f94962765166ef677;m=fd1cc199;t=633a404f8f053;x=14c6bfd5955da7ef
executable: /usr/libexec/ibus-x11
cmdline: /usr/libexec/ibus-x11 --kill-daemon
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.14.3-300.fc42.x86_64
package: ibus-1.5.32-1.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: g_hash_table_remove_all_nodes
comment: input chinese in Intellij IDEA
Truncated backtrace:
Thread no. 1 (12 frames)
#10 g_hash_table_remove_all_nodes at ../glib/ghash.c:656
#12 g_hash_table_unref at ../glib/ghash.c:1438
#14 g_dbus_message_finalize at ../gio/gdbusmessage.c:521
#16 message_to_write_data_free at ../gio/gdbusprivate.c:902
#17 write_message_cb at ../gio/gdbusprivate.c:1370
#18 g_task_return_now at ../gio/gtask.c:1363
#19 complete_in_idle_cb at ../gio/gtask.c:1377
#22 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249
#23 g_main_context_iterate_unlocked at ../glib/gmain.c:4314
#25 gdbus_shared_thread_func at ../gio/gdbusprivate.c:284
#26 g_thread_proxy at ../glib/gthread.c:893
#28 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2362429
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…