Update not working from Game Mode
The update button always fails with
"Update Error
An error was encountered during the update process, please try again."
When manually writing ublue-update from a terminal in game mode I get
ERROR: | update check failed, system isn't managed by rpm-ostree container native.
78 Replies
something is very wrong, run
rpm-ostree update for meSymbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP-md2, version OPENSSL_3.0.0
oh you're using the decky terminal plugin
Yeah
that's fine for simple stuff, but it's not a complete terminal
Oh
switch to desktop and then try
rpm-ostree updateWill do from the desktop. I think it works there.
But updates still fail in Game Mode
once you've confirmed that works
restart, and then try
ublue-update on the desktop
that'll tell you why updates might be failing
or it'll be solved by the update👍
No system update available. System passed hardware checks. System passed all update checks.
ok, just run
ublue-update thenMay be that game mode spits an error when no updates are available?
actually, give me a
rpm-ostree status | fpaste
and no, that's handled gracefullyGive me a sec, connecting a real keyboard to my handheld
https://paste.centos.org/view/db3d6951
your build is current
so weird, let's have you run a
ublue-update then
curious what it doesIt tells that everything is up to date
If done in desktop mode
In gaming mode updating is a no go
No idea why
Installed the distro today, did nothing crazy with it, just testing and playing a bit
I'll see if I can reproduce this
should be trivial to fix once I do
👍
Also have this issue on a fresh install, ran the commands and have no issues in terminal but in game mode update error
Hrmm did another fresh install and still have the same issue is it possible to have perhaps journalctl open while attempting an update because it seems like updates get shown just that error popup still appears, or are there gamemode logs somewhere I can take a look at perhaps to see what could be triggering the popup (maybe a x sec timeout)
Very interested in this, there must be some way to identify the problem so it can be fixed.
journalctl -u ublue-update-force | fpaste
Preferably right after a failure👍
https://paste.centos.org/view/54387c7c
Problem is, updating works as a charm in desktop mode. The error only happens in gamescope session.
Yeah I don't see any failures in that log
If you can recreate it failing in game scope and then switch to desktop and run that command that would be very helpful
That's exactly what I did just now
The last run is successful
Maybe if decky terminal was actually a real terminal we would have better info about the error
Almost seems like this is a steam bug
You can run this in a normal terminal in desktop mode
The weirdest thing is that only a small percentage of users have the bug
Yeah, that's what I did, but that log doesn't show the error at all
Also, after spitting the error, Steam usually shows the actual update if there is one and actually lets me update.
But the updates never show automatically in game mode and I have to manually go through the error at least once to check for updates
Hmm ...
yep exactly that I too have noticed
couldn't you run terminal in nested desktop then?
assuming you setup nested desktop, and you're not on deck-gnome
Not in gnome, so I can try that. Don't think the results will be any different, though. I don't think updates actually fail from the Steam interface. My theory is that they don't even start when the error shows, then it finds them for some reason and the patched Bazzite update system fixes itself. I'll run the same command from nested desktop tomorrow anyway, just in case.
still not able to reproduce this on any hardware
but next update is gonna add ~/.steamos-update.log
matching how gamescope logs
might help figure this out
Thanks, Kyle
Just to note it’s happening to me too, Lenovo legion go
That file should be created now
Current workaround is to just update in desktop mode, right? I'll update some LGO documentation with a note
This happens to you too?
updating from desktop works, but I literally can't reproduce this on any hardware
I don't know, I've been rebasing to specific images for to test for different bugs, etc
So I haven't tested the steam update yet
I can try to replicate
I'd appreciate that greatly
it's just calling /usr/bin/steamos-update
fairly simple script
But I do vaguely remember trying an update once a while back, and afterwards steam still showed the
update available
Anyways, I'll try to replicate itTo add to this, fresh install on Ally ROG and getting the same error when attempting in Game Mode however in desktop there's no issues, all is well! Very odd
@Aru were you able to reproduce this/
sorry, was busy and haven't gotten around to it yet. i'll try to reproduce after wrapping up some hhd-related dev work
@Kyle Gospo if I see this in dmesg, does that mean the update was successful?
hrm, looks like it was successful, time to reboot and see if it updated properly
Yea that's fine
They're saying they're getting an error in the steam UI
So if that's not your experience you're already not affected
hrm, maybe it wasn't successful. did the reboot, still see kernel 6.7.4 on testing
New kernel hasn't built yet
Ping you when that's ready
oh i thought it was, my bad
sudo dmesg | grep rpm-ostree for a recent update on testing branchGitHub
chore: Remove tuned-utils-systemtap · ublue-os/bazzite@cc1da88
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...
just did another update on testing branch, worked flawlessly. Hrm 🙃
Yep, that's my issue too ..
On like four different pieces of hardware too
if you're queuing up a stable release soon, I'll try updating on my GPD win 4 too
and see if I can replicate the issue there
unfortunately, i was also not able to replicate on my GPD win 4
update ran flawlessly
I manually checked earlier and failed BUT 10 seconds later, it said I had an update to install - not sure if that helps! (within Steam)
Updates I think work it's just a popup msg appears before you can install it
This may be fixed via today's update
do let me know 🙂
Haha not for me, but has caused my decky to disappear :HideThePain:
That can happen even on SteamOS. Just reinstall Decky and everything will come back
Yep that fixed the issue, seems like hltb has a error but seems like a decky issue since reports others having same issue
Interesting to see if op still has the issue with updates showing error
Yeah, not fixed for me either
just putting it out there that I've pretty much had the "update error" prompt for months, but the update actually still works, so I never did anything about it
latest update fixed the error popup bug for me
after rebasing from that feb image (due to sleep bug) to the latest stable that fixes the sleep bug :invincible:
It's fixed on my end too, just by updating, no rebasing needed
Hello, over past few days i've been having issues updating ROG Ally. The update from game would seemingly succeed, but upon restart, i'd be presented with the same update again. Occasionally, update would get stuck on "Verifying installation" or "Update complete, launching system" messages, but nothing else would happen for hours.
Just now, i've tried updating it via desktop mode and it is now stuck in "Verifying" for like 15 minutes now.
I could force shut down the system and it would most likely roll back to previous version. Anyone kno why could this be happening?
On another note, updating ROG ally causes no issues - just did that as well. So it seems ROG Ally only issue..
Run
rpm-ostree update in the terminal on desktopshould i hard reboot the device now? its been in verifying state for a while now. It is connected to wired network and i am seeing some sort of activity. Should i wait or is it stuck?
@Kyle Gospo something is very wrong with my OS.. did the
rpm-ostree update, went successfully. Asked me to reboot, did that as well. Ally booted into game mode, i did check for updates and it presented me with the same update again. Went into desktop mode, did rpm-ostree update again and it seemingly again did the same update that went successfully just few minutes before.You have no way of knowing what is being updated in game mode. The changelog is hardcoded to pull Steam Deck client or OS logs
but the
rpm-ostree update is doing the same thing post reboot - the update seeming does not "stick"
tried again - same thing. The update is just being rolled back..rpm-ostree status | fpaste@Kyle Gospo https://paste.centos.org/view/9af7b06e
rpm-ostree --version tells me i am on 2024.2 version
so far, i have tried:
* update from game mode -> rolled back or stuck on "verifying...:
* update via OS provided tool -> roll back
* update via rps-ostree upgrade -> roll back
* rpm-ostree rebase to gnome version -> roll back
by roll back i mean i am still on KDE version 2024.2 after each reboot
occasionally i'd get a systeam read-only message in console - i assume thats due to upgrade not finished
journalctl tells nothing for me (or i am lookingat wrong data)
also, during reboot between different screens i saw some console messages (on one occasion), but did not manage to capture those.Roll back to what exactly? I see this on your deployed version:
Maybe run and provide the log before restarting
@termdisc (Deck+PC) @Kyle Gospo
I figured rollback would just go to previous version, i did not specify anything. What's wrong is that
rebase that i did to bazzite-ally-gnome, did not stick as well....
https://paste.centos.org/view/3930699b
it is not very informative though..
But just before uploading this paste, in terminal i got an error message syscore cleanup: pruning ..... read-only file system
rpm-ostree status now shows 3 deployments, and i am still on 39.20240311.0 post update
btw, rpm-ostree update and rpm-ostree upgrade are synonyms or different commands?
did a ostree fsch -a and it shows some checksum error
i guess something got corrupt at some point
some more tinkering but the updates still do not work. I also think my system, while working, is now corrupt. I ran sudo ostree fsch -a --delete and it marked a bunch of commits as partial (23 or so) and i have no idea how to delete them or roll them back or roll back to an older version. Everything i do seemingly ends up in a read-only system
i flashed bazzite-ally iso to try and boot to live env and do some recovery from it but:
1. it does not seem to have live env
2. system rescue option does not even see my linux partition
3. shell commands do nothingThis is normal
That command doesn't support OCI
booted again to usb rescue shell
did btrfs scan
shows errors, wil ltry to btrfs scrub later
maybe that will help
honestly, this is pretty much the last idea i can think of on how to recover
btw, i checked ostree's
state folder and it has all the .partialcommit files that fsck seems to find. Should i delete those?
welp, no go. tried scrubbing, it did not even start - says my filesystem is read-only... i reckon btrfs should not go to read only state for no reason, so i guess it is corrupted beyond recovery or there is a hardware failure... i did check my device in partition manager and it found no errors, so i assume its file system. @Kyle Gospo would you have any ideas on this?I'm afraid not, and some of this stuff you're messing with really shouldn't be touched. You might be best with a reinstall at this point
You can back up and keep the var partition
That way your home dir is kept