Bug 1368593

Created attachment 1192314 [details]
File: backtrace

Created attachment 1192315 [details]
File: cgroup

Created attachment 1192316 [details]
File: core_backtrace

Created attachment 1192317 [details]
File: dso_list

Created attachment 1192318 [details]
File: environ

Created attachment 1192319 [details]
File: exploitable

Created attachment 1192320 [details]
File: limits

Created attachment 1192321 [details]
File: maps

Created attachment 1192322 [details]
File: mountinfo

Created attachment 1192323 [details]
File: namespaces

Created attachment 1192324 [details]
File: open_fds

Created attachment 1192325 [details]
File: proc_pid_status

Created attachment 1192326 [details]
File: var_log_messages

I cannot reproduce your problem.
Are you able to reproduce your backtrace?

Seems your desktop does not enable XKB. If you log into GNOME, ibus-ui-gtk3 should not be run since gnome-shell shows the ibus icon instead.


(In reply to laolux from comment #1)
> Created attachment 1192314 [details]
> File: backtrace

#0  XkbFreeClientMap (xkb=xkb@entry=0x5, what=what@entry=7, freeMap=freeMap@entry=1) at XKBMAlloc.c:903
903	    if ((xkb == NULL) || (xkb->map == NULL))
#1  0x00007f0e38624973 in XkbFreeKeyboard (xkb=0x5, which=<optimized out>, which@entry=127, freeAll=freeAll@entry=1) at XKBAlloc.c:322
#2  0x00007f0e3860e9f1 in _XkbReloadDpy (dpy=0x5620308fb020) at XKBBind.c:558
#3  0x00007f0e3860efdf in XKeysymToKeycode (dpy=0x5620308fb020, ks=ks@entry=32) at XKBBind.c:159
#4  0x000056202fe58f58 in keybinding_manager_bind (self=self@entry=0x562030a11930, keysym=keysym@entry=32, modifiers=GDK_CONTROL_MASK, handler=handler@entry=0x56202fe5dcc0 <___lambda38__keybinding_manager_keybinding_handler_func>, handler_target=handler_target@entry=0x562030ad6160) at keybindingmanager.c:210
#5  0x000056202fe5c1e8 in panel_keybinding_manager_bind (accelerator=0x562030a23e70 "<Control>space", keybinding_manager=0x562030a11930, self=0x562030ad6160) at panel.c:1334
#6  panel_bind_switch_shortcut (self=self@entry=0x562030ad6160) at panel.c:1398
#7  0x000056202fe5ee3a in panel_construct (object_type=<optimized out>, bus=<optimized out>) at panel.c:714
#8  0x000056202fe505d5 in application_bus_name_acquired_cb (parameters=<optimized out>, signal_name=<optimized out>, interface_name=<optimized out>, object_path=<optimized out>, sender_name=<optimized out>, connection=<optimized out>, self=0x5620308eaa10) at application.c:220
#9  _application_bus_name_acquired_cb_gd_bus_signal_callback (connection=<optimized out>, sender_name=<optimized out>, object_path=<optimized out>, interface_name=<optimized out>, signal_name=<optimized out>, parameters=<optimized out>, self=0x5620308eaa10) at application.c:166
#10 0x00007f0e37a2a277 in emit_signal_instance_in_idle_cb (data=0x7f0e20005850) at gdbusconnection.c:3701
#11 0x00007f0e37444703 in g_main_dispatch (context=0x562030900a10) at gmain.c:3154

Sorry, not been able to reproduce, just as the other one I experience (https://bugzilla.redhat.com/show_bug.cgi?id=1368592).
Could have been with Gnome on Wayland, if that helps any. Haven't been using that lately, will try (use) more.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

I decided to run ibus-ui-gtk3 with x11 backend only at the moment.
Fixed in f25 or later.

ibus-1.5.14-6.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c75f9d414a

ibus-1.5.16-6.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e743d58478

ibus-1.5.14-6.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c75f9d414a

ibus-1.5.16-6.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e743d58478

ibus-1.5.16-6.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

ibus-1.5.14-6.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.