https://bugzilla.redhat.com/show_bug.cgi?id=2252227
Bug ID: 2252227 Summary: [abrt] ibus-panel: wl_proxy_get_version(): ibus-ui-gtk3 killed by SIGSEGV Product: Fedora Version: 39 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:c75ecfa14c60b64aa5a0248ea5b67ce73f59fb4e;VAR IANT_ID=kde; Component: ibus Assignee: tfujiwar@redhat.com Reporter: RainSlide@outlook.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, shawn.p.huang@gmail.com, tfujiwar@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: Use iBus with telegram-desktop
Version-Release number of selected component: ibus-panel-1.5.29~rc2-3.fc39
Additional info: reporter: libreport-2.17.11 comment: Use iBus with telegram-desktop reason: ibus-ui-gtk3 killed by SIGSEGV backtrace_rating: 4 runlevel: N 5 type: CCpp kernel: 6.6.2-201.fc39.x86_64 executable: /usr/libexec/ibus-ui-gtk3 package: ibus-panel-1.5.29~rc2-3.fc39 uid: 1000 rootdir: / journald_cursor: s=465db592572c420f9b5043ae39b1812b;i=4f46;b=58bff58fc0044277ae9c3c28cee3ae3c;m=20bbc031c;t=60b5a88942da0;x=7185e6f9d1bff6f4 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' crash_function: wl_proxy_get_version cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
Truncated backtrace: Thread no. 1 (15 frames) #0 wl_proxy_get_version at ../src/wayland-client.c:2248 #1 zwp_input_method_context_v1_preedit_string at ../../client/wayland/input-method-unstable-v1-client-protocol.h:389 #2 _context_hide_preedit_text_cb at ../../client/wayland/ibuswaylandim.c:496 #5 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3980 #6 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612 #9 ibus_input_context_g_signal at /usr/src/debug/ibus-1.5.29 #11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:4020 #12 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612 #15 on_signal_received at ../gio/gdbusproxy.c:890 #16 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:3802 #19 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #20 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #22 gtk_main at ../gtk/gtkmain.c:1329 #23 application_run at /usr/src/debug/ibus-1.5.29 #24 application_main at /usr/src/debug/ibus-1.5.29
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Doc Type|--- |If docs needed, set a value
--- Comment #14 from fujiwara tfujiwar@redhat.com --- Are you still able to reproduce your backtrace? I cannot reproduce your issue. I don't know why the problem can happen because the IBusInputContext should be NULL before the Wayland input context is NULL.
(In reply to RainSlide from comment #10)
Created attachment 2002107 [details] File: backtrace
#1 0x000055772a9ae4e1 in zwp_input_method_context_v1_preedit_string (commit=0x55772a9b9bc7 "", text=0x55772a9b9bc7 "", serial=781, zwp_input_method_context_v1=0x0) at ../../client/wayland/input-method-unstable-v1-client-protocol.h:389 No locals. #2 _context_hide_preedit_text_cb (context=<optimized out>, wlim=<optimized out>) at ../../client/wayland/ibuswaylandim.c:496
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #15 from lehoangan02school@gmail.com --- sudo dnf install ibus-unikey ibus-setup in the terminal add ibus-unikey go to settings > input > virtual keyboard > ibus wayland > apply restart computer ibus-unikey keyboard shortcut for switching input method doesn't work for most apps unless it is the default apps on kde (not libreoffice) and firefox constantly restarting itself due to it crashing
reporter: libreport-2.17.11 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV journald_cursor: s=9deffa3a92ff47a5bba127b2c25f79b3;i=eca2;b=04df519e46f246ccac434b39b61f21a2;m=40828567;t=60dc8dc8c2267;x=623e13b348a691eb executable: /usr/libexec/ibus-ui-gtk3 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.6.8-200.fc39.x86_64 package: ibus-panel-1.5.29~rc2-6.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: wl_proxy_get_version
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #16 from Junyi the.junyi@gmail.com --- Trying to type Chinese in Gmail in Chrome.
reporter: libreport-2.17.11 kernel: 6.6.14-200.fc39.x86_64 comment: Trying to type Chinese in Gmail in Chrome. cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' backtrace_rating: 4 reason: ibus-ui-gtk3 killed by SIGSEGV uid: 1000 rootdir: / executable: /usr/libexec/ibus-ui-gtk3 crash_function: wl_proxy_get_version package: ibus-panel-1.5.29~rc2-6.fc39 runlevel: N 5 type: CCpp cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service journald_cursor: s=e2736061454c41f1859ca7011871a461;i=32dd5;b=3e46a7629a1d4c29bf84f10da0905e54;m=1422c73bb;t=61085b6b044fa;x=9a1d01a293d6584e
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #17 from Adrien deeewens@gmail.com --- I enabled IBus Wayland in the Virtual Keyboard section of Plasma settings. Which ended up not doing what I expected, so I deactivated it again. After I stopped my computer and started it again the next day, I got an error message telling me IBus crashed. I am not sure why or what it means.
reporter: libreport-2.17.11 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV journald_cursor: s=e4c95dcec2604e4b8df36652aa613dd6;i=381c4;b=c50814666b184e528ec6ebc3941a430b;m=9ec3097d;t=6110b12c4140f;x=414459434ee2b815 executable: /usr/libexec/ibus-ui-gtk3 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.7.4-200.fc39.x86_64 package: ibus-panel-1.5.29~rc2-6.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: wl_proxy_get_version comment: I enabled IBus Wayland in the Virtual Keyboard section of Plasma settings. Which ended up not doing what I expected, so I deactivated it again. After I stopped my computer and started it again the next day, I got an error message telling me IBus crashed. I am not sure why or what it means.
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #18 from Junyi the.junyi@gmail.com --- I switched to a tab with Gmail (on google Chrome (flatpak))
reporter: libreport-2.17.11 kernel: 6.7.4-200.fc39.x86_64 comment: I switched to a tab with Gmail (on google Chrome (flatpak)) cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' backtrace_rating: 4 reason: ibus-ui-gtk3 killed by SIGSEGV uid: 1000 rootdir: / executable: /usr/libexec/ibus-ui-gtk3 crash_function: wl_proxy_get_version package: ibus-panel-1.5.29~rc2-6.fc39 runlevel: N 5 type: CCpp cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service journald_cursor: s=5a1258bff6634a9cb1adc0468886a28f;i=3f252;b=3cb3b527e4254b0a84411e18c49af1a3;m=3fd8b4af;t=61188f308d837;x=626e37fc54abc92c
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #19 from Aragubas vaiogames18@gmail.com --- I was just switching windows and it seems like ibus crashed the windows in specific was Telegram, KDE Plasma Desktop and KDE Plasma default startup menu
reporter: libreport-2.17.11 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV journald_cursor: s=b573990ce5284b018c0506ef2d361fc7;i=4a113;b=cb8edaf39dcf4667aafb13eb708389d5;m=33a5c1b8e;t=61527d41dc12a;x=ecf09024d6d0da17 executable: /usr/libexec/ibus-ui-gtk3 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.7.10-200.fc39.x86_64 package: ibus-panel-1.5.29-1.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: wl_proxy_get_version
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |michael_wzq@icloud.com
--- Comment #20 from fujiwara tfujiwar@redhat.com --- *** Bug 2262336 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rudikarius@gmx.de
--- Comment #21 from fujiwara tfujiwar@redhat.com --- *** Bug 2266187 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED
--- Comment #22 from Fedora Update System updates@fedoraproject.org --- FEDORA-2024-afdec1e5e5 (ibus-1.5.30-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-afdec1e5e5
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #23 from Fedora Update System updates@fedoraproject.org --- FEDORA-2024-afdec1e5e5 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-afdec1e5e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-afdec1e5e5
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #24 from fujiwara tfujiwar@redhat.com --- I don't reproduce the issue yet but I found some memory issues in ibus-panel and fixed them. Let's see if this issue is resolved.
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #25 from Fedora Update System updates@fedoraproject.org --- FEDORA-2024-afdec1e5e5 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-afdec1e5e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-afdec1e5e5
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
--- Comment #26 from Fedora Update System updates@fedoraproject.org --- FEDORA-2024-afdec1e5e5 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-afdec1e5e5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-afdec1e5e5
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=2252227
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version| |ibus-1.5.30-5.fc40 Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed| |2024-06-25 02:26:10
--- Comment #27 from Fedora Update System updates@fedoraproject.org --- FEDORA-2024-afdec1e5e5 (ibus-1.5.30-5.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
i18n-bugs@lists.fedoraproject.org