Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
There is a hack to fix it. Yes, it's ugly solution but works for now.
For about a week now I could still download and run games from the client but not access the Store, Community or Profile from it.
I went into Linux Steam Integration and, for the "Use native runtime" option, flipped the switch from right to left to disable it.
Still not working.
It's irritating. I can still do everything from my browser, but... I shouldn't have to.
Like I said, I disabled it via Linux Steam Integration, yet the problems persisted.
On the plus side, I found something of a solution: I launched Steam via LSI and now I can access the sections that previously didn't work.
I installed a bunch of compatibility tools about a week ago, one of them may have messed up the default settings...
Ideally I'd figure out why all those features are broken, but for now I can just start Steam via LSI to bypass the problem. Annoying, but not overly so.
I never needed it until a week ago, but currently it's the only way I know to make the client able to connect with the Store, Community and Profiles.
I recommend getting the Flatpak version from FlatHub for any Non-Ubuntu, Non-Debian distro. This provides the best compatability, short of the Snap, which few non-Ubuntu distros have Snap installed by default making it pointless for this use.
I didn't even suspect the possibility that I'd broken anything until just now. Someone posted getting the exact same problem as me at the exact same time it happened to me, so I just thought some update (either on Steam's part or the OS' part) had broken something.
After reading the thread, I disabled the "Use native runtime" option and things still didn't work, which is when I made my initial post in this thread.
Having exhausted all natural avenues of investigation, I considered other possibilities and remembered downloading a few compatibility tools that I didn't know had anything at all to do with Steam, it was just a bunch of Wine stuff. I'm actually not certain I broke anything, it's just the most likely possibility at the moment.
Maybe I'll play around with all that later. Right now it's just not important, everything works fine.
Regarding the present problem, there totally was something making Steam open using the native runtime. I simply removed native-runtime from my computer so that whatever was doing that now can't do it anymore. I can open my Steam client directly and gain access to pages normally.
I wonder why the native runtime thing even exists if it's so completely borked and isn't ever going to be fixed...
Almost all the Steam games I care about work on Linux without even having to use SteamPlay, so that's good, but I'll keep the Flatpak in mind if I encounter some difficulties in the future. It's always good to have options.
It's one of the reasons I picked it... pretty much everything works right out of the box. I'm too old to waste my time on technical issues.
I find that works much better when loading programs compiled for other distros.
It has a few annoyances, such as the need to periodically run "flatpak update" as root if the permissions get f---ed up by something (which happened to me once or twice). However, it seems pretty reliable on the whole.