Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected

Bug #2062377 reported by vadim
72
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
mutter (Ubuntu)
In Progress
Medium
Daniel van Vugt

Bug Description

1)Go to xorg
2)Download Gnome Tweak Tool
3)Select DMZ-white
4)crash from the system

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024
 GCC version:
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 17:38:02 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524]
 Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
MachineType: Acer Aspire A715-42G
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2021
dmi.bios.release: 1.2
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Azalea_CAS
dmi.board.vendor: LN
dmi.board.version: V1.02
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.02
dmi.ec.firmware.release: 1.2
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku0000000000000000:
dmi.product.family: Aspire 7
dmi.product.name: Aspire A715-42G
dmi.product.sku: 0000000000000000
dmi.product.version: V1.02
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
vadim (vadim1337) wrote :
Jeremy Bícha (jbicha)
affects: xorg (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
importance: Undecided → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

affects: mutter (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Yves Bonneau (yvesb04) wrote :

Hello, i have the exact same issue. After crashing I switched to a Wayland Session and I noticed the cursor was also bugged (white square) when hovering over the dock

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Both that crash:

Apr 19 09:25:50 Legion5Pro gnome-shell[2799]: No cursor theme available, please install a cursor theme
Apr 19 09:25:50 Legion5Pro gnome-shell[2799]: Received an X Window System error.
                                              This probably reflects a bug in the program.
                                              The error was 'BadCursor (invalid Cursor parameter)'.
                                                (Details: serial 127343 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 MUTTER_SYNC environment
                                                 variable to change this behavior. You can then get a meaningful
                                                 backtrace from your debugger if you break on the mtk_x_error() function.)
Apr 19 09:25:50 Legion5Pro gnome-shell[2799]: GNOME Shell crashed with signal 5
Apr 19 09:25:50 Legion5Pro gnome-shell[2799]: == Stack trace for context 0x5bbb2d7c8930 ==
Apr 19 09:25:50 Legion5Pro gnome-shell[2799]: #0 5bbb2d890098 i resource:///org/gnome/shell/ui/init.js:21 (13ed08470bf0 @ 48)

and the white square:

https://gitlab.gnome.org/GNOME/mutter/-/issues/3184

seem to be due to mutter 46 not supporting legacy X11 cursor themes.

affects: ubuntu → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: Incomplete → Confirmed
importance: High → Medium
Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

FWIW, I am also affected in wayland, all packages up-to-date. Changing the cursor to adwaita fixes it for me was in DMZ-black).

Revision history for this message
Athos Ribeiro (athos-ribeiro) wrote :

Attaching a screenshot of what I am looking at when using DMZ-black

Revision history for this message
vadim (vadim1337) wrote (last edit ):

Well I found a solution when I downloaded the breeze theme I got breeze-cursor instead of a white square when I use dmz-white in wayland when I move the cursor to dash to panel. It is also the default cursor in xorg.

How it works? Like this:
There is a default folder in /usr/share/icons
There is index.theme inside

There is a line that indicates
Inherits=breeze_cursors

Basically you need to create a new cross cursor that would indicate that there is no cursor or supply the sudo apt-get install breeze package by default for Ubuntu
Or that it points somehow to the yaru cursor, only I do not know how to do it because breeze_cursors is a separate folder.
Well, the course of my idea you have understood

Revision history for this message
Jeremy Bícha (jbicha) wrote :

vadim, why couldn't you inherit Yaru or Adwaita which are already installed?

Revision history for this message
vadim (vadim1337) wrote :

I don't know how to write the path to the cursor file
breeze cursors is a separate folder
And the cursor in the yaru is in /Yaru/cursors
I tried to write the full path there and it didn’t work, I don’t know how to write the path to the cursor

summary: - Ubuntu 24.04. Xorg crash when dmz-white cursor is selected
+ Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme
+ is selected
Changed in mutter (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
milestone: none → noble-updates
status: Confirmed → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed:

#6 0x00007da91c9077fb in _XError () at /lib/x86_64-linux-gnu/libX11.so.6
#7 0x00007da91c90790f in ??? () at /lib/x86_64-linux-gnu/libX11.so.6
#8 0x00007da91c9079cd in ??? () at /lib/x86_64-linux-gnu/libX11.so.6
#9 0x00007da91c90971d in _XReply () at /lib/x86_64-linux-gnu/libX11.so.6
#10 0x00007da91c909aa5 in XSync () at /lib/x86_64-linux-gnu/libX11.so.6
#11 0x00007da91c909b3f in ??? () at /lib/x86_64-linux-gnu/libX11.so.6
#12 0x00007da91c8e0b2d in XFreeCursor () at /lib/x86_64-linux-gnu/libX11.so.6
#13 0x00007da91cf73c85 in meta_cursor_renderer_x11_update_cursor
    (renderer=0x5f58cdeed1a0, cursor_sprite=0x5f58cdc29790)
    at ../src/backends/x11/meta-cursor-renderer-x11.c:113
#14 0x00007da91cec592f in meta_cursor_renderer_update_cursor
    (renderer=0x5f58cdeed1a0, cursor_sprite=0x5f58cdc29790)
    at ../src/backends/meta-cursor-renderer.c:425
#15 0x00007da91cec5a3c in meta_cursor_renderer_force_update
    (renderer=0x5f58cdeed1a0) at ../src/backends/meta-cursor-renderer.c:460
#16 0x00007da91cf7121e in meta_backend_x11_reload_cursor (x11=0x5f58cdc05470)
    at ../src/backends/x11/meta-backend-x11.c:1121
#17 0x00007da91cfa0754 in update_cursor_theme (x11_display=0x5f58cdfd9b30)
    at ../src/x11/meta-x11-display.c:1757
#18 0x00007da91dbb86bd in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007da91dbb87c1 in g_signal_emit_valist ()
    at /lib/x86_64-linux-gnu/libgobject-2.0.so.0

Changed in mutter (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in mutter:
status: Unknown → New
Revision history for this message
danielb3 (danielb3) wrote :

I've also encountered this bug/crash since I always change the cursor to DMZ-White when I install Ubuntu and I reckon other ex-Windows users might also do. Before that I've noticed this weird "X" cursor when desktop was loading (see attachement).
I've replicated the bug using only the live USB (try without installing Ubuntu 24.04). Just apt install gnome-tweaks and then change cursor to DMZ-White leads to crashing. Re-tried by first installing Nvidia drivers with no difference.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please only use CSS cursor themes (like Yaru or Adwaita) until this bug is fixed.

Revision history for this message
Marko Hrastovec (marko-hrastovec) wrote :

Thanks for identifying the cause. I had to use wayland, and now I can go back to Xorg. For me it was impossible to find out why this was happening, because I was using DMZ-black, and upgraded from 22.04 much before if was stable. So I thought it will be resolved by the time of 24.04 launch. Unfortunately, that did not happen. Also had to find a substitute for a program I use, and it only works in X.

Revision history for this message
Anton Sudak (anton-sudak) wrote :

I got the same issue at the GDM. GDM uses X with nvidia driver and also uses Yaru cursor theme, which wasn't present in my system.

Revision history for this message
Jonathan Gilbert (logiclrd) wrote :

I upgraded from 22.04 to 24.04 and could no longer log in. Just immediately got the sad computer face screen. Can confirm that installing `breeze` fixed this. I don't really know what's going on but it seems to provide a functional fallback for when the selected cursor theme isn't working. Trying to explicitly change the cursor theme with dconf did not fix the problem, but installing breeze got me going again.

Revision history for this message
Jonathan Gilbert (logiclrd) wrote :

A further update -- a bit of a hack, but, I liked my "whiteglass" cursor, and I found that copying its left_ptr and right_ptr files from /usr/share/icons/whiteglass/cursors overtop of the corresponding ones in /usr/share/icons/Breeze_Snow/cursors gave me back my whiteglass cursor, at least for the pointer. :-P (I made backups of the originals before doing this.) Except in Firefox for some reason. Anyway, I don't see this as a long-term solution, but it at least helps somewhat with visibility for me.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.