this one occurred after rebasing, tried going back to previous ostree but its still happening
this one occurred after rebasing, tried going back to previous ostree but its still happening
Alike, i just can't use steam
Aat all
Phave you tried logging in as a different user
Pmayhaps
Aid have to add a user
Pyou would, wouldn't you
ZRebase won't help. Steam updates its own binaries all by itself
ZYou will always be stuck with the latest version
Pthis is also a fair point
Psteam is just being a fuck
ZThough, I'm sure there is a workaround for that, but I'm not sure
Aoh, it's broken for y'all too?
Pbut if you want to try anything after a rebase i suggest it'd be a new user
Pno
Pwhat GPU do you have?
ZHonestly didn't touch my computer since yesterday so can't tell
Poh shit
Phang on
Ayeh but going back to the previous ostree, it's still happening. This wasn't happening before rebasing into bazzite
P2 secs i want u to try something
Aamd lmao
Pjust let me consult the genius bar
Pin go settings > desktop session and make sure session restore is disabled
AI'm back on gnome - like I said, I rolled back
Pit defaulted to on for me at some point and steam decided to be a wacky loser about it, maybe it has for you too
Pthen maybe it's a gnoment
Pof the same variety?
Ai dont have restore session on, no
Aagain, this wasn't happening just before rebasing into bazzite:stable
Aand a rollback didn't fix it
Pare there any steam processes left behind you can sigkill
ZWait as in, you switched to KDE plasma or something?
Por does this literally happen even after a clean boot etc.
Ahappens after a clean boot
Pthis is weird af
AYes. Backed up .local and .config, restored them post-rollback as well
P:wat:
ZYou tried clearing .cache?
Ahm
Ano, i havent
ZSome leftovers might be causing that
Agood idea
ASame problem still after emptying .cache
ZOw
ZGonna give it a try to see if broke for me
Alog is a bunch of this now lol
Pyou can ignore 90% of that
Apressure-vessel-wrap[8407]: E: None of the supported CPU architectures are common to the graphics provider and the container (tried: x86_64-linux-gnu, i386-linux-gnu) probably wahtever this isZLD_PRELOAD lines can be ignored
Ai figured
