I’ve just installed Fedora Asahi Remix (39) on an M1 Air. It works really great, except for this inconvenience: if I close the lid and open it a bit later, then GNOME crashes with one or more reports. See some of the details below.
reason: gnome-shell killed by SIGSEGV
os_release: Fedora Asahi Remix release 39 (Thirty Nine)
reason: python3.12 killed by SIGSEGV
cmdline: /usr/bin/python3 /usr/bin/gnome-tweaks
I’ve tried to send in the crash report, but pressing Report results in another error:
Element 'os' is invalid: Element 'name' is invalid: Only the following values are allowed: centos, fedora
For some reason, running
systemctl suspend and waking up using the power button works fine, just not closing/opening the lid.
Edit: I see now that the first bug has already been reported. Not sure how to report the issue with the Report feature itself, however.
I am seeing the same problem after upgrading to Fedora 39.
The link you have posted on RH bugzilla does not appear to be the same issue, though.
Interesting to hear that the problem wasn’t present in Fedora 38. So what is the right place to report these two bugs (1: GNOME crashing; 2 the broken crash report feature)?
I am experiencing a very similar issue that materialized after I upgraded Mesa. I reported it to upstream here: gnome-shell crash on lock screen (#7199) · Issues · GNOME / gnome-shell · GitLab
Thanks Yussef! Yes, I tried downgrading MESA twice, as you described and it made the issue disappear. It also made the GNOME x11 crashes disappear.
Excellent news! So is this a bug in apple_dri? Some display driver portion for Apple GPU?
apple_dri is just “all of mesa”. The libraries are hardlinked, the filename is just an artifact of how the drivers are loaded. You need to look at the stack trace to figure out if this has anything to do with our actual driver or not.
Thanks @marcan. I didn’t realise that’s how it worked I think that report on the gnome tracker has a stack trace, I’ll double check
@albsod Moving back from the other thread, I just pushed a Mesa update with some misc fixes. Can you confirm whether the suspend/resume issue is still there?
You probably still want to remove
/usr/lib64/dri/zink_dri.so after the update until the glibc issue is solved and the updates for that are available (even on Wayland, just in case the underlying issue is still there somehow and causing other trouble).
@marcan After applying your latest updates I’ve closed and opened the lid a dozen times and not experienced any crashes so it looks promising! For reference, I left
/usr/lib64/dri/zink_dri.so in place.
@ydalton and @scidoner, could you try this as well?
I installed the latest Mesa a few hours ago, and I have not experienced any crashes (yet), although I think it is too early to tell. I will let you know if something comes up.