just for the hell of it, im gonna run system update
just for the hell of it, im gonna run system update
Asee if that does anything
ZThough, would be funny we were somewhat able to run steam at build time so we can kind of offer somewhat a snapshot of it's binaries, so if breaks, we can revert to a working version
Aid try removing steam and reinstalling it, but immutable filesystems :D
Gtheoretically you could reinstall steam I don't see why not
GGaming mode will stay iirc
Gand we got a spammer infection
AI suspected it might have been because I was using decky + css-loader for the "adwaita for steam" stuff, so I uninstalled brew and whatnot earlier, didn't help
Gyeah could pick back up that way, idk if you suspect that try to install it back?
AI did, still happening lmao
Gah I see yeye
AAlso this didn't do anything to help lol
Gusually it does it usually doesn't it's 50/50
Gyou rebooted is that correct? Unless everything was ok
ZWait
AI can't quite boot into gaming mode to like, check and make sure decky is working, reenable css-loader, etc because I'm not on a deck image (I had to rebase into a deck image a while back just to install & enable & configure css-loader, since afaik decky plugin store only exists in gaming mode)
Ghm?
ZWasn't there a workaround to make steam redownload all binaries in a clean folder
ANo clue
AI have no idea how on bazzite, since steam isn't a layer on the ostree afaik
AAnd I'm not on a deck image, so I don't have gaming mode
Gah yeah
Ghmm even if you elevate administrator privileges you can't reinstall steam right?
ABazzite has an immutable file system, usr is read-only
Gthough you can sudo your way though to say install dnf packages
GWhich as intended from sudo is to privilege admin so you can debug it
ANo way to even remove steam from bazzite though
Ahmm.. could
steam-runtime-sniper have been fucked somehow?ZYou can't
Gwell search yes but use dnf I see that you can, that is to install than search
ZWell, you can install packages, but removing them eh
Gyeah
ZI don't even know if we even use rpm-ostree to install steam at build time
GI bet KDE Discover wouldn't do much
GI noticed rpm-ostree being utilized a few times ye
AHere's the relevant steamwebhelper logs (i think)
ASteam is entirely non-functional, btw. Like, I can't even open my library or anything. When I launch it, it does nothing for a bit (not even an "updating steam" popup), and then pops up with this error
Atrying any of the options does nothing, same error comes up
Aeither that or steam just doesn't relaunch when clicking "ok"
ZOk found it, basically is
cp -Tr --reflink=always ~/.local/share/Steam ~/.local/share/Steam_old. That will make sort of a backup but force steam to redownload its binariesAill give it a try
Athere's this in the
console-linux.txt log, as well, before it starts to upload the error dump
Aiirc you just move .local/share/Steam to another folder and steam will recreate that
A@ruv0119 you could try that
ZYeah basically
Goh btw I tried some solution, there are intermittent times it appeared (especially connected to a display?) anyways I typed the journalctl command you instructed right after
https://paste.centos.org/view/97824086
https://paste.centos.org/view/97824086
Agiving it a try now
Adeleting also work but backing up is better
Zyeah, also with --reflink will use almost no space, btrfs benefits
Ais it automatic? i know btrfs have that but never messed with it
Ahow do i "undo" this command?
