Hi. Some time ago I discovered that I couldn't create a new workspace dragging a window in the GNOME desktop manager. Whenever I wanted to move an app window the cursor turned into an "X" and after the click was released, a BadCursor Signal was sent to the X server killing gnome-shell and restarting it. Today I was trying to figure out why it was happening and discovered that if I run gnome-shell --replace as root, the session changed with root's configuration and I was capable of creating new workspaces by dragging windows into them. The problem begins when I set gentoo-blue as default cursor on any user. If you need some extra report or can't reproduce the failure please let me know.
I know nothing about this. Sorry.
I can add, this also happens to me. Using default Adwaita cursor is fine, however as soon as any of the gentoo-xcursors are used the exact same symptom happens. Output from journalctl below: Oct 29 19:08:29 pig gnome-shell[17149]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadCursor (invalid Cursor parameter)'. (Details: serial 408115 error_code 6 request_code 95 (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 GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Oct 29 19:08:29 pig kernel: traps: gnome-shell[17149] trap int3 ip:7f99155bd371 sp:7ffe146799f0 error:0 in libglib-2.0.so.0.5000.3[7f991555f000+128000] Oct 29 19:08:29 pig systemd[1]: Created slice system-systemd\x2dcoredump.slice. -- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit system-systemd\x2dcoredump.slice has finished starting up. -- -- The start-up result is done. Oct 29 19:08:29 pig systemd[1]: Started Process Core Dump (PID 4964/UID 0). -- Subject: Unit systemd-coredump@0-4964-0.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@0-4964-0.service has finished starting up. -- -- The start-up result is done. Oct 29 19:08:37 pig gnome-keyring-daemon[17013]: asked to register item /org/freedesktop/secrets/collection/login/420, but it's already registered Oct 29 19:08:50 pig gnome-keyring-daemon[17013]: asked to register item /org/freedesktop/secrets/collection/login/420, but it's already registered Oct 29 19:08:51 pig polkitd[573]: Unregistered Authentication Agent for unix-session:c3 (system bus name :1.84, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, Oct 29 19:09:02 pig gnome-keyring-daemon[17013]: asked to register item /org/freedesktop/secrets/collection/login/420, but it's already registered Oct 29 19:09:06 pig systemd-coredump[4965]: Process 17149 (gnome-shell) of user 1000 dumped core. -- Subject: Process 17149 (gnome-shell) dumped core -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: man:core(5) -- -- Process 17149 (gnome-shell) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug.
I think this was a bug in Mutter that was fixed in 3.30. See https://gitlab.gnome.org/GNOME/mutter/issues/254 Please reopen if you can still reproduce with an up to date system.
