SDDM dumps core on boot on a chromebook
I started playing with installing Bazzite today, and I ran into an issue that I haven't found a solution for from others. On boot, before logging in, SDDM crashes with a trace pointing to libopenjph.
I tried adding
noapic to cmdline via rpm-ostree kargs but either I did it wrong or this Reddit post is outdated because on reboot, the system dropped into emergency mode, complaining that it cannot find a partition by its uuid. Reverting that override fixed that ofc.
I also tried installing libopenjph-devel as an override to maybe make the trace more useful, but on next boot, we don't even get to the networking stack - the system gets stuck on a blank screen with a non-blinking cursor :/
Some info about my setup, and what I found so far:
- Model: HP Chromebook 14a (Blooglet), coreboot flashed with fwscript
- ujust device-info: https://paste.centos.org/view/a7ea5492
- Full dmesg: https://paste.centos.org/view/d8341369
- Trace from journalctl: https://paste.centos.org/view/639d44ca
- I installed using the iso from bazzite.gg (the desktop version, after going through the selection menu), then rebased onto my image, which layers my ssh key on top of the system. This issue happened both straight after install and after rebasing (the images are nearly identical).
- Googling reveals this thread on the FreeBSD bugzilla, not sure if relevant but it was the only related result besides the release that introduces libopenjph from around mid-november
I'd be happy to put some elbow grease in to help debug, appreciate the help!5 Replies
Little update, rolling back to 41.20241112.1 does fix this, and sddm shows up, with no issues logging in afterwards. I plan on manually bisecting between stable releases to see where the issue is introduced, but this is a great start!
is it a chromebook with intel graphics? sounds like this issue
https://github.com/ublue-os/aurora/issues/8
GitHub
No graphical session after update to 41.20241117.3 on Aurora. · Iss...
Describe the bug The system updated from 41.20241112.1 to 41.20241117.3 and on the next boot it showed the arrow cursor for a little while and then a blank screen. It didn't even show the login...
GitHub
libheif and heif-pixbuf-loader from negativo causes sddm/plasma/qt ...
Context: ublue-os/aurora#8 ublue-os/aurora#8 (comment) Responsible commit? negativo17/libheif@4a4cbd9 affected hardware: possibly everything that uses i915? Pentium B940 SandyBridge = Gen6 Graphics...
Interesting, I don't think it's the first one because they had a cursor. The diff from the second one looks very similar to the one I saw when rolling back tho
they are the same issue, the second one is just the root cause and without the progress report essentially