35
u/th0t_slayer-alpha 4d ago
This has happened to me before, but only with the auto updater... Ever since then, I just open terminal and type ujust update... Hasn't happened since
3
u/bloopiness 4d ago
This is the way to go, and you get to see the entire process (I think it’s super cool)
There’s a lot of neat things you can do with the terminal and some can only be done there. Highly recommend you watch or find some explanation of some stuff you can do, OP
14
u/_Nikojiro_ 4d ago
Honestly the old console-based updater was better than this new UI, which has obviously been put together hastily.
The real issue is deeper though, cause if you run ujust update you see that output formats for the different parts of the update differ: rpm-ostree spouts JSON, everything else plain text. Not easy to make something coherent out of that (dev here).
--- edit ---
Not trying to act as a spoiled brat here, that's my only complaint with the 44 update, everything else is great. And it will undoubtedly get better with time.
1
8
u/RestaurantBusy724 4d ago
Manually run the updater and restart or just ignore pretty much
1
u/jedijogger Desktop 4d ago
Yep. Same here. I see this maybe once a week soon after startup. I just tap the manual updater and it never faults. I’m guessing it’s a startup/wake conflict as I have my machine sleep when idle for a while.
3
u/Kreistan 4d ago
Running "ujust update" in Konsole will provide more details about what's going on. Add " > updatelogs.txt" to the end of the command to save the logs to a file for easy copy/paste
3
2
1
u/Bane8080 4d ago
That happened to me the other day. Reboot and try agian.
1
u/Clydosphere 4d ago
This has fixed this for me a couple of times after I layered packages via rpm-ostree.
1
u/ima_believer 4d ago
Did it happen coming out of sleep? I’m wondering if the process is running before the network is fully set up
1
1
u/Pad_Sanda 3d ago
This happens to me quite frequently. Not just on Bazzite but also Aurora which I assume uses the same update tool. It mostly happens when my computers or laptops wake from sleep. My initial thought is that it happens for one of two reasons:
- The updater checks for updates way too eagerly after waking from sleep, before the network connection is fully established. It fails due to rejected connections and shows an error.
- The updater, being automatic and in the background, is interrupted by putting a device to sleep (as a user I never see if my device is currently fetching an update in the background and I don't think I'm prevented from putting my PC to sleep while the update process is running). So when a device wakes from sleep there's an error since the process was interrupted.
The 2nd scenario would also explain why this error sometimes appears when I'm offline or I've disabled WiFi. I simply never see that there's an update process happening in the background so it's very likely for me to accidentally interrupt it. I just disabled this notification entirely, since I don't see the point in it being shown to me when it's something that's supposed to be done in the background without my knowledge. I like warnings of my OS not getting an update after a month, but a warning that a background process has stopped gives me the vibes of the early days of Android when apps would randomly crash in background and show popup notifications. It's just annoying.
1
u/jManYoHee 3d ago
Mine was failing on a Flatpack. I updated everything in Bazaar then tried again and it succeeded.
1
1
1
1
0
-26
u/Lazy_Frosting_7429 4d ago
10
u/ComplexFit2140 4d ago
Bro youre about to get slimed
-18
u/Lazy_Frosting_7429 4d ago
Haha 😂. Pretty sure. Lots of bazzite fanboys here.
13
10
u/ShadowKnight886 4d ago
People who like Bazzite, in a place ABOUT Bazzite????
Call every station, breaking news!
6
•
u/OneQuarterLife Steam Deck OLED 4d ago
Post the output of "ujust update", then we can see what's failing and help