Gnome-shell segfault: mesa 24.3.2-1, vbox guest, VMSVGA, fedora 41 workstation

Ask Fedora
1

It looks like if I update mesa to the 24.3.2-1 via dnf update, gnome-shell crashes with a segfault.

[   11.666015] gnome-shell[1289]: segfault at 8 ip 00007f592922904f sp 00007ffda61fb9d0 error 4 in libgallium-24.3.2.so[2904f,7f5929201000+1a4a000] likely on CPU 3 (core 3, socket 0)
[   11.666040] Code: 48 89 e5 41 56 41 55 41 54 41 89 f4 53 4c 8b 6f 58 48 89 fb 0f b6 05 81 b9 a3 02 84 c0 0f 84 98 00 00 00 0f b6 05 71 b9 a3 02 <41> 83 7d 08 03 4c 8d 35 25 01 91 02 88 83 68 01 00 00 7e 0e 49 83

This seem to only affect a virtualbox fedora 41 workstation guest that I use for testing. I did update on a couple other physical hosts with amdgpu and they seem fine.

If I revert to a previous snapshot that is on the previous mesa 24.2.8-1 all is fine.

I wonder if anyone else has seen this behavior?

2

Hi and welcome to :fedora: !

It seems you’re not alone:

3

Thank you for the information, I didn’t think to search for “black screen” on the forums. I’ll poke around in the mesa issues tracker and see if something as been reported.

1 Like
4

Just an FYI, I have created an issue with mesa #12447, with the backtrace from the gnome-shell core. There are a few similar issues that are still open, so this may be a duplicate of one of those.

5

Looks like we crossed the streams. I just created a Mesa bug report as well Mesa 24.4.2 causing gnome-shell to crash in VMware virtual machine (#12448) · Issues · Mesa / mesa · GitLab - I suspect that this issue impacts both x86_64 and aarch64 architecture VMware virtual machines (I’m running on VMware Fusion with F41 aarch64 and seeing the same thing).

I think this is impacting Rawhide as well as F41. I’m seeing the same gnome-shell crash there.

1 Like
6

For anyone that views this thread, on Fedora Workstation 41, mesa package version 24.3.4-3.fc41 has the fix for the segmentation fault with gnome-shell ( aka black screen ).

7

Those packages are also being distributed with rawhide, so it’s fixed there as well.