Bazzite Stuck on Splash Screen After Upgrading to Bazzite 42 from 41

[robarmstrong96]

Describe the bug

I've just recently attempted to upgrade to Bazzite 42 manually (ujust update and/or rpm-ostree rebase) and it appears after successfully updating to the new release + rebooting, Bazzite will hang during the splash screen. Choosing Bazzite 41 instead works fine during boot, it's just when booting into 42 where the hang occurs. I managed to grab some boot logs during the boot-up process from one of the failed boots and have included it here, hopefully this helps.

log.txt

What did you expect to happen?

Expected to boot into Bazzite 42. Instead, it hangs during the splash screen indefinitely.

Output of rpm-ostree status

State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:testing
                   Digest: sha256:55370fb2c1f83841c31f61051abd28d4eb9e70e506a6b24c684977a1e6229b32
                  Version: testing-42.20250429.1 (2025-04-30T02:41:07Z)
                     Diff: 2564 upgraded, 15 downgraded, 144 removed, 101 added

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:76b3f9e1dbb86bcfd1f18930a1af887533d3de600c1c21fd94c01174cf658bfc
                  Version: 41.20250409.1 (2025-04-09T19:14:25Z)
                   Pinned: yes

Hardware

• Ryzen 5600x
• Radeon 6800xt
• B550I AORUS PRO AX
• 32GB DDR4
• Multiple NVMe + 2.5" SSDs in RAID 0

Extra information or context

I'm currently on testing after having tried the stable branch; the results are the same between testing and stable for 42.

[wolfyreload]

Try following the instructions in https://docs.bazzite.gg/Advanced/Reset_Forgotten_User_Password/ until you are logged into the terminal of the machine then ignore the reset password stuff and try and run steamos-session-select desktop and see if you can at least get into desktop mode in Bazzite-42.

This is not a usual setup to have RAID 0 too so maybe that's part of the issue, not sure.

[robarmstrong96]

Okay, I should hopefully be able to try this out later today.

Also, just wanted to clarify that it is software raid that I had setup using the Bazzite installer during installation.

[robarmstrong96]

Alright, no luck. I'm sure there are some extra steps that I'm missing.

[wolfyreload]

That's a weird one, it's like the system is failing to mount your home partition all of a sudden when you do an upgrade. I've never seen that before.

[ThraaxSession]

Got the same issue. You can see the upgrade is pending.

First you need to apply with rpm-ostree upgrade. And then run ujust update after reboot. Then it should start normally.

[robarmstrong96]

That didn't appear to make a difference either. I did go ahead and hit 'ESC' during the splash screen after a few minutes and saw this:

I noticed the 'path_is_absolute(p)' failure in the logs as well, I believe. Could be related to the software raid that is configured. Weird that it works fine in 41 but not 42.

EDIT: Spelling

[douatigari02]

I'm stuck but in a more interesting issue, i have a big artifact on my screen when trying to boot into Bazzite-42, aswell, 41 works just fine lol

[PVermeer]

#2495

[Sanidin]

I am also getting a similar error on a AMD 5700U mini-pc. I've been pinned to a F41 version for some time now.
pcie_mp2_amd 0000:04:00.7: amd_sfh_hid_client_init failed err -95
systemd-journald[823]: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:648, function chase(). Aborting.

[robarmstrong96]

#2495

That did it for me! Thanks! Marking this as resolved.