Bug ID 1184543
Summary wayand crashes when trying to display keyboard layout in GNOME live system
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.3
Hardware x86-64
OS Other
Status NEW
Severity Major
Priority P5 - None
Component X.Org
Assignee gfx-bugs@suse.de
Reporter Ulrich.Windl@rz.uni-regensburg.de
QA Contact gfx-bugs@suse.de
Found By ---
Blocker ---

Whenever I try to display the keyboard layout in the GNOME live system
(openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso), something odd happens:
Suddenly there are a few text characters in the upper left corner of the
screen, and the graphical background is all gone.  It looks as if the system
has crashed, while keys pressed are displayed.

As it turned out from journal, wayland had crashed:

pr 08 21:04:44 linux.fritz.box systemd[2492]: Started Application launched by
gnome-shell.
Apr 08 21:04:44 linux.fritz.box gnome-shell[4182]: syntax error: line 1 of
stdin
Apr 08 21:04:44 linux.fritz.box gnome-shell[4182]: Errors encountered in stdin;
not compiled.
Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: > Internal error:   Could
not resolve keysym XF86WWAN
Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: > Internal error:   Could
not resolve keysym XF86RFKill
Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: Errors from xkbcomp are not
fatal to the X server
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Modifiers specified, but DRI
is too old
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Modifiers specified, but DRI
is too old
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE)
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Backtrace:
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 0: /usr/bin/Xwayland
(xorg_backtrace+0x65) [0x55f1d24fd375]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 1: /usr/bin/Xwayland
(0x55f1d2361000+0x1a0049) [0x55f1d2501049]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 2:
/lib64/libpthread.so.0 (0x7f00e9e8e000+0x13f80) [0x7f00e9ea1f80]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 3: /usr/bin/Xwayland
(0x55f1d2361000+0x4faec) [0x55f1d23b0aec]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 4: /usr/bin/Xwayland
(0x55f1d2361000+0x46188) [0x55f1d23a7188]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 5: /usr/bin/Xwayland
(BlockHandler+0x3a) [0x55f1d24cf9ca]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 6: /usr/bin/Xwayland
(WaitForSomething+0xd7) [0x55f1d24faa97]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 7: /usr/bin/Xwayland
(0x55f1d2361000+0x169de3) [0x55f1d24cade3]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 8: /usr/bin/Xwayland
(0x55f1d2361000+0x16e03c) [0x55f1d24cf03c]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 9: /lib64/libc.so.6
(__libc_start_main+0xed) [0x7f00e9aef34d]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 10: /usr/bin/Xwayland
(_start+0x2a) [0x55f1d23a623a]
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE)
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Segmentation fault at
address 0x0
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE)
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Fatal server error:
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Caught signal 11
(Segmentation fault). Server aborting
Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE)
Apr 08 21:04:44 linux.fritz.box gkbd-keyboard-d[4179]: gkbd-keyboard-display:
Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Apr 08 21:04:44 linux.fritz.box gnome-shell[2593]: Connection to xwayland lost
Apr 08 21:04:44 linux.fritz.box gsd-xsettings[2828]: gsd-xsettings: Fatal IO
error 11 (Resource temporarily unavailable) on X server :0.
Apr 08 21:04:44 linux.fritz.box systemd[2492]:
gnome-launched-gkbd-keyboard-display-4179.scope: Succeeded.
...

When waiting long enough, the display manager is started again (by systemd, I
guess).
However it's not obvious to the user what had happened (I also had reset the
computer the first time).


You are receiving this mail because: