bazzite: upgrade success but reboot failed

Describe the bug

When i upgrade the system, then reboot it, it show this picture IMG_1535

The information is like this

[
OK
1 Finished plymouth-quit-wait.servichold until boot process finishes up.
OK
1 Finished plymouth-quit service - Terminate Plymouth Boot Screen.
[FAILEDI
Failed to start tailscaled.service - Tailscale node agent.
[FAILEDI
Failed to start cups.service - CUPS Scheduler.
[FAILEDI
Failed to start wireplumber-sysconf.service - Hardware Specific Wireplumber Configuration.
[FAILED!
Failed to start
tailscaled.service - Tailscale node agent.
[FAILED]
Failed to start
cups. service - CUPS Scheduler.
[FAILED!
Failed to start
systemd-uconsole-setup.service - Virtual Console Setup.
LPAILEDI
Failed to start
tailscaled.service - Tailscale node agent.

What did you expect to happen?

I expected reboot system.

Output of rpm-ostree status

No response

Hardware

GPD win4 7840U

Extra information or context

No response

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Comments: 20 (3 by maintainers)

Most upvoted comments

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

I only have the 20240415 option on grub … i will install a previous iso from scratch. Is there a way to install a previous image version build or should install the 2.4.0 20240314 and manage from there ?

Yeah you should install 2.4.0. afterwards you may manually update to a more recent version if you wish. But you have to do it through Terminal commands to get the correct update. When you update through Steam Gaming Mode it will always install the most recent stable one.

Did v3.0.0 fixed this bug?

yeap! At least for me the desktop bazzite stable 3.0.0 works fine, upgraded and boots correctly. 👍 tx!

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

Sure, here it is :

image

You can click esc once immediately, when you power on the computer. As this, you can see the boot menu. Select the ostree:1 to boot into previous version. But if you update to the newest version, problem is still here.