https://bugzilla.redhat.com/show_bug.cgi?id=2392358
Bug ID: 2392358
Summary: [abrt] ibus-panel: ibus_service_constructed():
ibus-ui-gtk3 killed by SIGSEGV
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:8569166ab34b7d5c81aed4fc2482ddb5958024eb;VAR
IANT_ID=kde;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: woonj(a)woontech.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:
I was trying to switch to the "IBus wayland" virtual keyboard while I started
Ibus-setup from the terminal (I don't think I was suppoed to do thas)
Version-Release number of selected component:
ibus-panel-1.5.32-1.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-ui-gtk3 killed by SIGSEGV
journald_cursor:
s=cfaf3b94f783442db6a9c7ccae8d11f2;i=17eede33d;b=3dd1b3858f674bd3b185712ae38b4d63;m=1560d57241;t=63dbaf249fc5a;x=f3e04a06f4b37a9
executable: /usr/libexec/ibus-ui-gtk3
cmdline: /usr/libexec/ibus-ui-gtk3
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole@d2bb77a94b2d4197a7cf860130e85f82.service
rootdir: /
uid: 1000
kernel: 6.16.3-200.fc42.x86_64
package: ibus-panel-1.5.32-1.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: ibus_service_constructed
comment: I was trying to switch to the "IBus wayland" virtual keyboard
while I started Ibus-setup from the terminal (I don't think I was suppoed to do
thas)
Truncated backtrace:
Thread no. 1 (14 frames)
#0 ibus_service_constructed at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusservice.c:289
#1 g_object_new_with_custom_constructor at ../gobject/gobject.c:2603
#2 g_object_new_internal at ../gobject/gobject.c:2627
#3 g_object_new_valist at ../gobject/gobject.c:2968
#5 panel_construct at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/panel.vala:112
#6 panel_new at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/panel.vala:108
#7 application_bus_name_acquired_cb at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:100
#8 _application_bus_name_acquired_cb_gd_bus_signal_callback at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:68
#9 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:4207
#12 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249
#13 g_main_context_iterate_unlocked at ../glib/gmain.c:4314
#15 gtk_main at ../gtk/gtkmain.c:1329
#16 application_run at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:89
#17 application_main at
/usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:379
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2392358
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=2326692
Bug ID: 2326692
Summary: [abrt] ibus-typing-booster: endElement():
langtable.py:334:endElement:AttributeError: 'dict'
object has no attribute '_names'
Product: Fedora
Version: 41
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:32b157848ec9b889f0697dbb2cbc8e8b8ed9f268;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: computer_nerd3(a)hotmail.com
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:
I was adjusting the preferences of the Terminal. Although, ibus-typing-booster
seems to crash regardless of what I'm doing.
Version-Release number of selected component:
ibus-typing-booster-2.26.8-1.fc41
Additional info:
reporter: libreport-2.17.15
kernel: 6.11.7-300.fc41.x86_64
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
cgroup:
0::/user.slice/user-1001.slice/user@1001.service/session.slice/org.freedesktop.IBus.session.GNOME.service
uid: 1001
reason: langtable.py:334:endElement:AttributeError: 'dict' object has
no attribute '_names'
executable: /usr/share/ibus-typing-booster/engine/main.py
type: Python3
package: ibus-typing-booster-2.26.8-1.fc41
runlevel: N 5
exception_type: AttributeError
crash_function: endElement
interpreter: python3-3.13.0-1.fc41.x86_64
comment: I was adjusting the preferences of the Terminal. Although,
ibus-typing-booster seems to crash regardless of what I'm doing.
Truncated backtrace:
langtable.py:334:endElement:AttributeError: 'dict' object has no attribute
'_names'
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/engine/main.py", line 132, in <module>
import factory
File "/usr/share/ibus-typing-booster/engine/factory.py", line 37, in <module>
import hunspell_table
File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 52, in
<module>
import itb_util
File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 97, in
<module>
import langtable # type: ignore
^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/langtable/__init__.py", line 1, in
<module>
from .langtable import *
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 2719,
in <module>
__module_init = __ModuleInitializer()
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 2714,
in __init__
_init()
~~~~~^^
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 2704,
in _init
_read_file('territories.xml', TerritoriesContentHandler())
~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 954, in
_read_file
_expat_parse(file, sax_handler)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 934, in
_expat_parse
parser.ParseFile(file)
~~~~~~~~~~~~~~~~^^^^^^
File
"/builddir/build/BUILD/python3.13-3.13.0-build/Python-3.13.0/Modules/pyexpat.c",
line 473, in EndElement
File "/usr/lib/python3.13/site-packages/langtable/langtable.py", line 334, in
endElement
self._names[str(self._item_id)] = self._item_name
^^^^^^^^^^^
AttributeError: 'dict' object has no attribute '_names'
Local variables in innermost frame:
self: <langtable.langtable.TerritoriesContentHandler object at 0x7f2a140f0440>
name: 'name'
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2326692
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=2248636
Bug ID: 2248636
Summary: [abrt] ibus-libpinyin: std::__glibcxx_assert_fail():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 39
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:90b337510822b74ec1264b8ed94bb02bf5d3006e;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: jacknlliu(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
Description of problem:
upgrade to fedora 39
Version-Release number of selected component:
ibus-libpinyin-1.15.4-1.fc39
Additional info:
reporter: libreport-2.17.11
journald_cursor:
s=efe1502c004e4d8fb9e372c089ce0297;i=3204d5;b=3f4d4311a5ea437cb5394fb51d9e764d;m=3258aaa;t=6099aa3bced6f;x=7855a2569304aad2
crash_function: std::__glibcxx_assert_fail
rootdir: /
reason: ibus-engine-libpinyin killed by SIGABRT
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
kernel: 6.5.9-300.fc39.x86_64
backtrace_rating: 4
runlevel: N 5
comment: upgrade to fedora 39
type: CCpp
cgroup: 0::/user.slice/user-42.slice/session-c1.scope
uid: 42
executable: /usr/libexec/ibus-engine-libpinyin
package: ibus-libpinyin-1.15.4-1.fc39
Truncated backtrace:
Thread no. 1 (27 frames)
#4 std::__glibcxx_assert_fail at
../../../../../libstdc++-v3/src/c++11/debug.cc:61
#5 std::unique_ptr<PY::LibPinyinBackEnd,
std::default_delete<PY::LibPinyinBackEnd> >::operator* at
/usr/include/c++/13/bits/unique_ptr.h:451
#7 PY::LibPinyinBackEnd::instance at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYLibPinyin.h:61
#8 PY::SuggestionEditor::~SuggestionEditor at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYPSuggestionEditor.cc:48
#10 std::_Sp_counted_ptr<PY::SuggestionEditor*,
(__gnu_cxx::_Lock_policy)2>::_M_dispose at
/usr/include/c++/13/bits/shared_ptr_base.h:428
#11 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release at
/usr/include/c++/13/bits/shared_ptr_base.h:346
#13 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count at
/usr/include/c++/13/bits/shared_ptr_base.h:1071
#14 std::__shared_ptr<PY::Editor, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr
at /usr/include/c++/13/bits/shared_ptr_base.h:1524
#15 std::shared_ptr<PY::Editor>::~shared_ptr at
/usr/include/c++/13/bits/shared_ptr.h:175
#16 PY::PinyinEngine::~PinyinEngine at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYPPinyinEngine.cc:123
#18 PY::ibus_pinyin_engine_destroy at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYEngine.cc:185
#20 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:4020
#21 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#24 ibus_object_dispose at /usr/src/debug/ibus-1.5.29
#27 g_list_foreach at ../glib/glist.c:1092
#28 g_list_free_full at ../glib/glist.c:246
#29 ibus_factory_destroy at /usr/src/debug/ibus-1.5.29
#31 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:4020
#32 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#35 ibus_object_dispose at /usr/src/debug/ibus-1.5.29
#39 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3980
#40 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#43 emit_closed_in_idle at ../gio/gdbusconnection.c:1375
#46 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
#47 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
#49 ibus_main at /usr/src/debug/ibus-1.5.29
#50 start_component at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYMain.cc:155
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2248636
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=2372527
Bug ID: 2372527
Summary: [abrt] ibus-typing-booster: g_malloc(): python3.13
killed by SIGABRT
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:6c984bdb56b78cfbac329c0377577688b0630e54;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: lorenzus.ian8(a)gmail.com
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:
It seems like it is crashing in background
Version-Release number of selected component:
ibus-typing-booster-2.27.63-1.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.13 killed by SIGABRT
journald_cursor:
s=a2ea7dfa38344f98a729281a13197d1b;i=3fdcd;b=83f546ce93f94b6f9ecd8c4b15107071;m=16be28d2b;t=637601c2edf7a;x=6bac89d61c6c35c
executable: /usr/bin/python3.13
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.14.9-300.fc42.x86_64
package: ibus-typing-booster-2.27.63-1.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: g_malloc
comment: It seems like it is crashing in background
Truncated backtrace:
Thread no. 1 (34 frames)
#10 g_malloc at ../glib/gmem.c:100
#11 g_slice_alloc at ../glib/gslice.c:193
#12 g_source_new at ../glib/gmain.c:934
#13 timeout_source_new at ../glib/gmain.c:5127
#14 g_timeout_source_new at ../glib/gmain.c:5157
#15 connection_setup_add_timeout at ../atspi/atspi-gmain.c:349
#17 add_timeout at ../atspi/atspi-gmain.c:445
#18 _dbus_timeout_list_add_timeout at ../dbus/dbus-timeout.c:324
#19 protected_change_timeout at ../dbus/dbus-connection.c:841
#20 _dbus_connection_add_timeout_unlocked at ../dbus/dbus-connection.c:874
#21 _dbus_connection_attach_pending_call_unlocked at
../dbus/dbus-connection.c:936
#22 dbus_connection_send_with_reply at ../dbus/dbus-connection.c:3480
#23 check_for_hang at ../atspi/atspi-misc.c:1207
#25 _atspi_dbus_call_partial_va at ../atspi/atspi-misc.c:1325
#26 _atspi_dbus_call_partial at ../atspi/atspi-misc.c:1365
#27 atspi_accessible_get_state_set at ../atspi/atspi-accessible.c:731
#29 ffi_call_unix64 at ../src/x86/unix64.S:104
#30 ffi_call_int at ../src/x86/ffi64.c:673
#31 ffi_call at ../src/x86/ffi64.c:710
#32 pygi_invoke_c_callable at ../gi/pygi-invoke.c:731
#33 pygi_function_cache_invoke at ../gi/pygi-cache.c:941
#34 pygi_callable_info_invoke at ../gi/pygi-invoke.c:774
#35 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:811
#36 _callable_info_call at ../gi/pygi-info.c:548
#38 _PyObject_MakeTpCall at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Objects/call.c:242
#39 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/generated_cases.c.h:1843
#40 _PyEval_EvalFrame at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Include/internal/pycore_ceval.h:119
#41 _PyEval_Vector at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/ceval.c:1816
#42 _PyFunction_Vectorcall at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Objects/call.c:413
#43 _PyObject_VectorcallTstate at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Include/internal/pycore_call.h:168
#44 method_vectorcall at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Objects/classobject.c:70
#45 thread_run at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/_threadmodule.c:337
#46 pythread_wrapper at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/thread_pthread.h:243
#48 __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=2372527
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=2374979
Bug ID: 2374979
Summary: [abrt] ibus-typing-booster:
g_settings_schema_get_value(): python3.13 killed by
SIGTRAP
Product: Fedora
Version: 42
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:f87e8213a5627c1152f3ed76d505f164606a1b6e;VAR
IANT_ID=kde;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: dwlegg(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-typing-booster-2.27.65-1.fc42
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.13 killed by SIGTRAP
journald_cursor:
s=ba5e9344dfc94054963f95303db481f2;i=110adc;b=2659a8eb57ed495d8a1149dffaf2c6e8;m=456bda70;t=6386231bccf16;x=365aa2e1d55fe93f
executable: /usr/bin/python3.13
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--xml
cgroup: 0::/user.slice/user-0.slice/session-c1.scope
rootdir: /
uid: 0
kernel: 6.14.11-300.fc42.x86_64
package: ibus-typing-booster-2.27.65-1.fc42
runlevel: N 5
backtrace_rating: 4
crash_function: g_settings_schema_get_value
Truncated backtrace:
Thread no. 1 (27 frames)
#4 g_settings_schema_get_value at ../gio/gsettingsschema.c:1005
#6 g_settings_schema_key_init at ../gio/gsettingsschema.c:1294
#7 g_settings_get_user_value at ../gio/gsettings.c:1350
#8 ffi_call_unix64 at ../src/x86/unix64.S:104
#9 ffi_call_int at ../src/x86/ffi64.c:673
#10 ffi_call at ../src/x86/ffi64.c:710
#11 pygi_invoke_c_callable at ../gi/pygi-invoke.c:731
#12 pygi_function_cache_invoke at ../gi/pygi-cache.c:941
#13 pygi_callable_info_invoke at ../gi/pygi-invoke.c:774
#14 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:811
#15 _callable_info_call at ../gi/pygi-info.c:548
#17 _PyObject_MakeTpCall at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Objects/call.c:242
#18 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/generated_cases.c.h:813
#19 PyEval_EvalCode at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/ceval.c:604
#20 run_eval_code_obj at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/pythonrun.c:1381
#21 run_mod at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/pythonrun.c:1466
#22 pyrun_file at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/pythonrun.c:1295
#23 _PyRun_SimpleFileObject at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/pythonrun.c:517
#24 _PyRun_AnyFileObject at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Python/pythonrun.c:77
#25 pymain_run_file_obj at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/main.c:410
#26 pymain_run_file at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/main.c:429
#27 pymain_run_python at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/main.c:696
#28 Py_RunMain at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/main.c:775
#29 Py_BytesMain at
/usr/src/debug/python3.13-3.13.3-2.fc42.x86_64/Modules/main.c:829
#30 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58
#31 __libc_start_main_impl at ../csu/libc-start.c:360
#32 _start
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2374979
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=2323789
Bug ID: 2323789
Summary: The word "Favorites" appears as a candidate in emojier
when pressed!
Product: Fedora
Version: 41
OS: Linux
Status: NEW
Component: ibus
Keywords: Regression
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Manish and I discovered this bug in emojier last week while testing.
Reproducible: Always
Steps to Reproduce:
0. Open gnome-text-editor
1. Start emojier by pressing Super+Period Space
2. Click on Favorites category
Actual Results:
The word "Favorites" is listed as an emoji candidate in the grid!
Expected Results:
"Favorites" should not be listed as a favorite emoji.
Does not seem to happen in current F40.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2323789
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=2397633
Bug ID: 2397633
Summary: Deadkey latch function seems to be broken
Product: Fedora
Version: 43
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: bkelly(a)coastsystems.net
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rstrode(a)redhat.com
Target Milestone: ---
Classification: Fedora
Example Cameroon International keyboard uses latch deadkey function. Pressing
;, then releasing, and pressing an additional will will insert partiular
character.
Normally pressing and releasing ; followed by e, will insert ;e instead of ə.
Reproducible: Always
Steps to Reproduce:
Reproduce: Go to Settings Keyboard, Add Input Source. Select Cameroon
Multilingual Qwerty.
Press and release ; folowed by e.
Actual Results:
Actual results: Press and release ; followed by e inserts ;e
Press and hold ; while pressing e inserts ;ə
Expected Results:
Expected results: Press and release ; folowed by e inserts ə.
Additional Information:
(At least pressing and holding can produce the desired character, but requires
additional finger acrobatics and is not the normal functionality. The latch key
character ';' is also inserted. However the level 1 ;(latch key) normally
should insert nothing and wait for the next keypress.
Strangely running under both Sway and Hyperland also under wayland, this works
fine. So is this a Gnome specific issue? Since it also works with Sway I was
concluding that it is not an xkeyboard-config issue itself.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2397633
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…