Bazzite update broken - Shows a black screen after log in (KDE)
I updated some days ago, but upon logging in, I was greeted with a seemingly useless black screen. (KDE, Wayland, Framework 13, AMD CPU).
TTY is available, so if everything breaks, I know I can use
bazzite-rollback-helper or other commands if needed.
As such, I selected the previous rpm-ostree version on boot (GRUB), and as expected, I am able to use my computer.
I found this thread that seems identical to my issue: #After updating bazzite, I am hit with a black screen on desktop mode
However, the solution was to reinstall Bazzite, and it doesn't seem to be a good idea.
Attachment is the output of rpm-ostree status. I have no idea what the red line means.
@Sean.exe suggested to pin the previous version (the one I am on right now), but I am unsure of how to do that.
So, I have three questions:
1. How do I pin the previous version (the one that I am using right now)?
2. After doing that, I can safely update without "removing" the working version, right?
3. What does the SecAdvisories: 1 unknown severity, 7 moderate, 5 important mean?
Thanks in advance!
Solution:Jump to solution
@DD (ping when you reply) run
rpm-ostree status -v. You'll an index next to each version, in parenthesis. See which number your current version is. I expect it will be two based on the order they show up here. (The count starts at zero.) Run that command to double check me on that, and then run sudo ostree admin pin 2. Run rpm-ostree status -v and under your current version it should say "Pinned: yes". That means it will continue to show up in your bootloader until you unpin it.8 Replies
Solution
@DD (ping when you reply) run
rpm-ostree status -v. You'll an index next to each version, in parenthesis. See which number your current version is. I expect it will be two based on the order they show up here. (The count starts at zero.) Run that command to double check me on that, and then run sudo ostree admin pin 2. Run rpm-ostree status -v and under your current version it should say "Pinned: yes". That means it will continue to show up in your bootloader until you unpin it.wow there's so much info, so cool
here's the output of the command
(you're awesome btw, thanks for the help)
I believe I need to run this command
but I will wait for your confirmation
@DD (ping when you reply) Sorry to keep you waiting - I'm at work now. Yes, your current version is index one from February 11th. Index 0 is the new one from yesterday. After you've pinned it, it will continue to show up in your GRUB menu. As the oldest version, it should be the one with the highest index.
Do you also have multi monitors? I have a similar issue and it seems like an issue on KDE Plasma that was very recently fixed
https://bugs.kde.org/show_bug.cgi?id=500819
this current issue is on a laptop (framework 13) with AMD CPU/GPU, so no multi monitor lol
I did not have this issue on my desktop (intel CPU, nvidia GPU), which has two monitors; if it was recently fixed, one less thing to worry :)
no worries for the wait, this is really not urgent
sorry for asking for your help when you're busy, you don't need to reply immediately at all
I have successfully pinned deployment 1
should I just
ujust update now?
in the SecAdvisories section of rpm-ostree status -v, there's wireshark (which I do not need anymore), should I uninstall it? or should I not care?@δDD The update is already installed and ready. You just need to reboot and let it boot into index zero. The "SecAdvisories" section is just a list of security upgrades between your current version and the new version. Wireshark showing up means that it's had a security update fixing the vulnerability listed. This isn't a good way to find out about unfixed vulnerabilities on your system. You can uninstall wireshark if you don't need it anymore, or keep it around. Either way should be fine.
ujust update might be a good idea to just update the other packages on your system while you're at it, but isn't required.finally updated after ages, and I have a working laptop with the latest version of KDE! thanks again for your help
