What does the different OS channels do on the game mode settings? I'm guessing 38 and 39 is Fedora v
What does the different OS channels do on the game mode settings? I'm guessing 38 and 39 is Fedora versions but what's stable?
ZIs 39 perhaps my modified image done through rpm-ostree?
ZAlright I did an update through the steam deck UI, I usually do it in terminal and it shows Stable Beta and 39
RAssuming they didn't break anything, yeah, why not?
RYeah, I'm not sure myself. Stable should be latest and main unstable (IIRC), but for me the updater in Game Mode just fails to install os updates, so I might be wrong.
RAnd each time I set something manually the os selection always show unstable.
RSo I'm not sure 
T@__aru the rollback was successfully completed . Is this the same version you have?
KRegarding those pipewire issues, are you guys seeing it on KDE too or only GNOME?
RKDE too
Kty
RSame exact issue on my install.
K@rodoma92 if you still have the issue, can you get a log from pipewire for me?
RI'll try later today, if I can get it to boot again.
RI just achieved one single boot after the update after 10 tries.
RBut then I forgot to unplug the monitor and the deck decided to fail train on the external monitor + not returning on the internal one.
RFun /s
RWait, I'm dumb.
RI should be able to SSH in.
RAssuming enough of the OS is up.
RFor people on deck with boot issues and no way to use an external keyboard, just spam select on boot.
RThis is the same as pressing escape on a keyboard.
R(The three lines button)
RSSH is up, so I should be able to.
R(As soon as I copy my identity to the Deck, I forgot to do that since I've upgraded)
DJust updated my bazzite deck install which also updated the bios and my install is now broken, at first it booted to the system but without audio/audio control, after a restart the system doesn't boot into desktop or gamescope, it just opens a terminal screen
KIf you can get a log from pipewire that would be helpful
Kin the meantime, you can rebase back to the last release with:
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:39-20231121Kwe're looking into it
DHow can I do that?
Ksystemctl status pipewire | fpasteKjournalctl - u pipewire | fpasteDAfter rebasing back to the previous ver?
Kbefore, if you could
DOkay
RIt just dies with 254
RThat's it, @KyleGospo
KNo logs before it dies?
REnter and exit immediately with 254
RChecking dmesg but nothing of relevance pops out for me
KAlright, gonna pull out steamdeck-dsp on :testing and go from there
TUniversal Blue
How do updates work? Bazzite updates all of the changes made specifically in Bazzite itself, updates from Fedora’s base packages, and user applications installed. The next reboot will contain the newest changes. No need for worrying about manually updating your system. How do I update? Desktop images (bazzite, bazzite-nvidia, bazzite-gnome,...
RNow my logs are gone? I'm confused.
Rjournalctl --user -xeu pipewire.servic
Ktry no u
RIs this the correct param to see the pipewire status?
RThanks
RArgument not valid
Knvm u is valid, it's a user service
RBtw, now that I'm logged in via SSH.
RIt boots to desktop fine
