Version-Release number of selected component:
cmdline: gkbd-keyboard-display -l us
runlevel: N 5
Thread no. 1 (4 frames)
#0 xkl_engine_constructor at /lib64/libxklavier.so.16
#1 g_object_new_internal at /lib64/libgobject-2.0.so.0
#2 g_object_new_valist at /lib64/libgobject-2.0.so.0
#4 xkl_engine_get_instance at /lib64/libxklavier.so.16
Created attachment 1066464 [details]
Created attachment 1066465 [details]
Created attachment 1066466 [details]
Created attachment 1066467 [details]
Created attachment 1066468 [details]
Created attachment 1066469 [details]
Created attachment 1066470 [details]
Created attachment 1066471 [details]
Created attachment 1066472 [details]
Created attachment 1066473 [details]
Created attachment 1066474 [details]
Created attachment 1066475 [details]
Created attachment 1066476 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
I got this backtrace when trying to display the keyboard layout on a gnome+wayland session. This always immediately results in a SEGV. When specifying GDK_BACKEND=x11, it crashes at a later point in execution or runs fine.
In theory, it should be possible to make gkbd-keyboard-display work under wayland, since we're using xkb there too. If that is too hard, we should at least disable the button in the region panel under wayland.
(In reply to Matthias Clasen from comment #16)
> In theory, it should be possible to make gkbd-keyboard-display work under
> wayland, since we're using xkb there too. If that is too hard, we should at
> least disable the button in the region panel under wayland.
And also in the gnome-shell keyboard-switcher dropdown menu, which is only visible in case you have multiple keyboard layouts configured.
Having it ported would be preferred, of course.
*** Bug 1262553 has been marked as a duplicate of this bug. ***
the keyboard layout window is now using X11 (enforced). The crasher is gone for me now.
Can somebody please close this bug, it is fixed upstream on Fedora 25 for quite some time.