how do I upgrade/rebase without uninstalling packages that can't be updated, that are third-party, b
how do I upgrade/rebase without uninstalling packages that can't be updated, that are third-party, basically?
M(if that's possible)
SI can't seem to get grub to show on boot.
SReason I am asking all of this. I made sure my deck was set to lastest with the os-tree command and now I am getting a login screen.
SI will make a help page.
Eujust unhide-grub
EA normal update won't remove them. If you rebase or reset the tree, you'll have to reinstall them
Mso by normal update does that include the version upgrade (e.g. fedora 38 -> 39)?
Mbecause I couldn't get f39 with just a normal update and had to rebase
M
RIs there a way to get Bazzite to a sort of "factory" state with like, configs and packages without losing my personal files and flatpaks? Games, ROMs, etc?
EThe :latest tag receives the latest Fedora version we support over updates. No need for a rebase when you use it
SOn the cli? I cant login nor use sudo since I forgot my password. I have tried all possivle passwords with no luck.
EA reinstall. Keep your existing home directory in tact
SSorry @EyeCantCU I dont mean to sound rude. I thabk you for your help.
EIn that case, you should be able to press the escape key after the UEFI splash
SOk
Eplug for Elite Dangerous Odyssey being on sale (you can see Agricultural Stations on foot now 
)
)If anyone's a fan of Freelancer, then you really need to check out Elite Dangerous Odyssey: https://store.steampowered.com/app/1336350/Elite_Dangerous_Odyssey/
Msorry, not sure what you mean. I tried to get fedora 39 and I couldn't because I got an error. that's why I did a rebase in the first place
HMI didn't, because by this point I'd already upgraded to f39 with a rebase
MI was thinking of seeing if I can avoid uninstalling it in the future - when upgrading to f40, for example
Kerror: Updating rpm-md repo 'expressvpn-repo': cannot update repo 'expressvpn-repo': repomd.xml GPG signature verification error: Bad GPG signature
Kthis is your issue, you absolutely can layer packages and update without issue
Kbut you cannot update a package from a repo who's signature you don't have/can't test
Kyou can either fix that, or edit the repo to not do gpg checking in /etc/yum.repos.d/
RDo I have to click any special options to do so? Basically is there a way to mess up and lose everything?
RI'm on Steam Deck
Myeah, that's what I figured - but the "software" app that I figured was supposed to update everything, but I got an error, I wouldn't have even tried the rebase if I thought the update would've worked, and I don't know how to fix the refspec issue
Dbut doesn't reinstalling wipe everything?
MHey, bazzite-gnome hasn't had an update for a week. Is this as intended?
Also the version marked
Also the version marked
39.20231121labels.org.opencontainers.image.version39.20231120.0rpm-ostree statusGitHub
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
BIf the developers are us-based last week was a holiday
BIt may have to do with that
EYou'd have to use manual partitioning when installing without selecting the home partition for formatting
ROkay! That's fine then.
KWe are, issue however is upstream in nature
KBuilds happen automatically 2x a week without our input
KWhen the upstream issue is resolved they'll resume
Dbut I didn't manually partitioned by system and made /var/home a seperate directory. I just let anaconda do it for me.
Dwill the upstream issue even resolve?
EI forgot people that didn't manually paritition their drive don't have a separate home partition
EWhy wouldn't it?
EWith that said you may be able to retain the BTTFS subvolume but I am not sure
Dbecause there is some unfixable bug involved
EWell it's certainly not unfixable and I wouldn't consider absent builds a bug
MSo trying out VRR with the new update. Worked first try when connected directly to my TV. Then plugged the deck into my VRR compatible receiver which is plugged into my TV. Was unable to enable VRR on the deck now. Ok. Switched back to direct connect to the TV. Now I can’t turn on VRR anymore 
MI don’t know how to fix it yet, but figured I’d just share
MAnd I’ve tried rebooting, changing resolutions, verifying that the TV is setup right, and unplugging the power from the dock and plugging it back in. Still can’t get it back
Dtry booting into your previous deployment
MI mean it was working. All I did was switch what it was plugged into
ETo my understanding, the patchset needs to be updated for 45.1
