Gnome Wayland crashing on login.
I normally build from a more customized bluebuild image but this is now occurring on bazzite-gnome:stable as well, rebased to remove variables. In short, when logging in via Wayland GNOME I get what appears to be a core dump according to the output of the log this session ujust. It started happening a couple days ago. Attached is the full text of the "log this boot." I'm at a loss on this one.
EDIT with more data: on a framework 16.
Ok, more info, back on my personal image and everything looks good if I go back to May 7th image.
(At this point I'm trying to narrow down the introduction of the problem) May 14th's image was fine, gonna try May 21st next.
16 Replies
Have you tried disabling secure boot and seeing if the newer image boots?
Not happening for me, just checked my framework 16 on the absolute latest image
I should clarify as it might not have been clear, it'll boot just fine, and I can login to both Gnome Xorg and when on my custom image, the Cosmic session I have as well, but when attempting to login to Wayland specifically it'll crash out
Maybe make a new user and see if you can log into Wayland without it crashing, then you can eliminate if it's something in local user settings or some issue in the system settings somewhere.
This did it so it appears. Test user was fine
Well that’s incredibly frustrating
So this isn't a bazzite issue, but if anyone has any suggestions on how to deal with this nonsense I'd really appreciate it.
Try rename your .cache folder in your home folder (that fixes a bunch of stuff like broken icons for me) perhaps there is something there breaking the login. It's a long shot but it's the least annoying approach. If that doesn't help then you might have a bad setting somewhere in your .config or .local folder, look specifically around the gnome settings in those folders
Its something I'm pretty sure to do with my dconf settings somewhere
so I exported them, wiped them, and sometime later today I'll get a chance to just cherry pick the important bits and re-import them
Ok, I think I've got it working? I deleted all dconf settings I didn't instantly recognize as my own. Gimme a minute and I can post the ones I deleted for anyone seeing this in the future
Anyone running into similar situations, here are the dconf settings I deleted (Note a few are for extensions baked into Bazzite I have turned off. So YMMV)
I also found a dconf referencing a font I don't think I have?
Annnddd its doing it again >.>
https://extensions.gnome.org/extension/5724/battery-health-charging/
This is the culprit, I'm 99.999% sure. Without it enabled, laptop is fine, can boot, reboot, do all the things
I re-enable it, laptop is fine, on reboot, it goes into a bad state
I have to delete my .config and .cache folders (probably not all of them, but at this point it was eaiser to just back them both up entirely and restore)
and we're back to normal after doing that.
So glad I know now, can go make an issue on the github
(Ok, one more test... I think it might be a specific branch that the author wrote for me that's the problem?)
Glad you found the culprit.
at least I'm pretty sure I was.