I’m using a custom image based on bazzite-dx-gnome-stable on my home PC. I’m not doing anything too crazy customization-wise. I’m installing a few GNOME extension packages and a driver for the fan in my System76 Thelio.
I went on vacation for a couple of weeks in July and when I got back and updated my machine it started hanging at boot. Looking at the logs from the failed boots I see two interesting things:
Aug 01 17:03:31 moya systemd[1]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Aug 01 17:03:31 moya udisksd[1377]: Mounted /dev/sdb4 (system) at / on behalf of uid 1000
Aug 01 17:03:31 moya systemd-udevd[966]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.
Aug 01 17:03:31 moya audit[966]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:udev_t:s0-s0:c0.c1023 pid=966 comm="systemd-udevd" exe="/usr/bin/udevadm" sig=6 res=1
Aug 01 17:03:31 moya audit[2160]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:init_t:s0 pid=2160 comm="systemd" exe="/usr/lib/systemd/systemd" sig=6 res=1
Aug 01 17:03:31 moya systemd[1]: Caught <ABRT>, from our own process.
This crash looks related to Bazzite Stuck on Splash Screen After Upgrading to Bazzite 42 from 41 · Issue #2565 · ublue-os/bazzite · GitHub but the fix from the linked issue didn’t do anything in my case.
The other interesting thing in the boot logs is lots of SELinux-related errors, e.g.
Aug 01 17:07:48 moya setroubleshoot[1786]: SELinux is preventing bootupctl from 'read, open' accesses on the file /usr/bin/ostree.
I see similar messages on a successful boot, so maybe it’s nothing. But there are a lot of them.
I’d really appreciate any advice on how to proceed here. I’ve pinned my last successful image which was based on ghcr.io/ublue-os/bazzite-dx-gnome:stable@sha256:0bd12da970ce28214838c46c3920f6d109188c778ac52c31cc4c00e39a2b2073 from July 12, so at least I should be able to boot, but no updates I’ve tried since then will boot on my machine.
) to be fixed? Might be the kernel bump.