DecentM
UBUniversal Blue
•Created by DecentM on 12/31/2024 in #🛟bazzite-help
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!6 replies