neovim dd and xsel -i kills the gnome-shell with X Window System error_code 5 request_code 17 (core protocol) minor_code 0)
Affected version
NAME="openSUSE MicroOS"
VERSION="20230326"
ID="opensuse-microos"
gnome-shell 44.0 (gnome-shell-44.0+28-1.1.x86_64
), using Wayland compositor, disabling extensions haven't helped
Bug summary
Each time I press dd
in neovim (neovim-0.8.3-2.1.x86_64
) under gnome-shell, the gnome shell session is restarted. This happens 100% times as much weird it sounds. The same operation in vim
works fine.
Steps to reproduce
- Open gnome-terminal
- Launch nvim foo
- Type anything in insert mode (everything is fine including dd)
- Press Esc
- Type dd to remove a line (haven't tested more commands as loosing the gnome shell is really annoying)
What happened
gnome-shell is immediately restarted
What did you expect to happen
Keep working :-)
Relevant logs, screenshots, screencasts etc.
I think this is a relevant part of a journald logs
Mar 28 11:22:02 localhost.localdomain systemd[1311]: Reached target GNOME session X11 services.
Mar 28 11:22:02 localhost.localdomain gnome-shell[21578]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Mar 28 11:22:02 localhost.localdomain gnome-shell[21578]: > Warning: Unsupported maximum keycode 708, clipping.
Mar 28 11:22:02 localhost.localdomain gnome-shell[21578]: > X11 cannot support keycodes above 255.
Mar 28 11:22:02 localhost.localdomain gnome-shell[21578]: Errors from xkbcomp are not fatal to the X server
Mar 28 11:22:02 localhost.localdomain gnome-shell[17996]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
Mar 28 11:22:02 localhost.localdomain systemd[1311]: Starting GNOME XSettings service...
Mar 28 11:22:02 localhost.localdomain systemd[1311]: Started GNOME XSettings service.
Mar 28 11:22:02 localhost.localdomain systemd[1311]: Reached target GNOME session X11 services.
Mar 28 11:22:07 localhost.localdomain gnome-shell[17996]: Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 326 error_code 5 request_code 17 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the meta_x_error() function.)
Mar 28 11:22:07 localhost.localdomain gnome-shell[17996]: == Stack trace for context 0x55a2d77abd40 ==
Mar 28 11:22:08 localhost.localdomain gnome-shell[21567]: (EE) failed to read Wayland events: Broken pipe
Mar 28 11:22:08 localhost.localdomain fractal[20061]: Error reading events from display: Broken pipe
Mar 28 11:22:08 localhost.localdomain xdg-desktop-por[18627]: Error reading events from display: Broken pipe
Mar 28 11:22:08 localhost.localdomain evolution-alarm[18380]: Error reading events from display: Broken pipe
Mar 28 11:22:08 localhost.localdomain gsd-wacom[18428]: Error reading events from display: Broken pipe
I would love to debug it more, but frankly have no idea how to to it.