Beta steamos side does the same, nothing, so most likely was the update indeed... guess I'll have to
Beta steamos side does the same, nothing, so most likely was the update indeed... guess I'll have to play on it for real xD
EThis is a new one
ECan you get
journalctl | grep steamos-session-select | fpaste
DHas anyone ever thought of having a factory reset script in the justfile that resets
rpm-ostree/etcOh, and just to add, if you want to get to desktop mode, run
systemctl disable bazzite-autologin.serviceSorry for not explaining that earlier
Vrpm-ostree reset
Bok... i'm going to try the bazzite again 
EThank you!
EOpe
EErr... That's off
ELet's try something
Dbut that doesn't reset
/etcAnd waaaay at the bottom you'll see this
Try removing those lines and then see if it works
E@saberj2x
EThe sentinel gets created so it reaches the end there
EThere's no reason for it not to work
Dthat isn't going to persist between reboots
EIt doesn't need to
Dhow come?
EWe just need a solution
EBecause if that's the problem then we can fix it
Doh yeah you can push the update out by editing the file on github
DI am talking about resetting
/etcrpm-ostree@KyleGospo Has Oversteer been moved to bazzite-arch yet?
VIf it has, do I need to remake the box?
NI encountered the unable-to switch-to-desktop-mode issue earlier today as well
UI forgot just how intense the X11 screentearing is on nvidia
DGitHub
add xwaylandvideobridge on bazzite portal for KDE desktop version
NI ran these commands, removed those lines, saved the file and switched back from the TTY. When trying to switch to Desktop mode I got a "verifying installation" splash-screen and then was returned to game mode.
EAll right... not handycon. Something more sinister. I'll take a closer look at changes we've made recently. Thank you so much for confirming that
NNo problem; I want to fix this too! 
NIt was kind of touched on already, but as some added context/a question. I keep getting prompted for Steam OS updates. Should I be trying to do those, and if not, is that what might be happening here, it's trying to apply the update and is blocking us from leaving gamemode somehow?
EIt's likely that there's just a lot of changes being made on our end. Most of those updates are from us. Every time the image rebuilds, there's an update
Nthat answers my other question; I wasn't sure if those update alerts were "false positives" because Valve was doing updates but didn't know I was running Bazzite. I had applied them in the past with no issue, but I was always a bit sus of them, and had been doing
just update-systemanything else you want me to try?
Thttps://github.com/Venomalia/UniversalDynamicInput the dolphin emulator community never ceases to amaze me
GitHub
a custom button pack for dolphin that supports over 150 games! - GitHub - Venomalia/UniversalDynamicInput: a custom button pack for dolphin that supports over 150 games!
EIf you edit that same file (steamos-session-select) and at the top remove the line setting BASE_IMAGE_NAME and replace it with
BASE_IMAGE_NAME=kinoite or silverblue depending on what image you have installed... does that fix it?EAnd more importantly, does that make sense?
Nyes it does, let me see what it says now, please hold!
NI'm NOT supposed to reboot, right?
Kit's installed in a fedora container
Kno need to remake
KColin WaltersColin Walters
While I often lump “dpkg/rpm” together since they’re very similar architecturally, their implementation of configuration file management is a small but nontrivial difference. This…
E@turbwroan don't reboot
NI'm in Desktop mode!
NThat worked.
ECrap
NI changed it to kinoite
EI didn't want that to be the problem lol
