Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.

Steam for Linux Is a little messed up, here's the temporary fix!

By - | Views: 35,388
Something odd has happened to Steam for Linux and you might face some difficulties starting/restarting it at the moment. We don't know what causes this, but luckily we have a quick temporary fix for you!

If your Steam seems to hang during starting up with terminal output similar to this then you have to run a quick command to fix it until you start it up next time. This is the command (source: http://steamcommunity.com/app/221410/discussions/0/864978835653093697/):

rm -Rf ~/.steam/steam/appcache

Removing the appcache doesn't seem to affect Steam in any way and hopefully the permanent patch for this annoying bug will be released soon.

Edit by liamdawe: You will also need to kill any Steam processes running.
Edit: Removing the appcache actually might affect installing games on Steam, but we have mixed results about that. Article taken from GamingOnLinux.com.
Tags: Steam
0 Likes
About the author -
author picture
I'm a Linux gamer from Finland. I like reading, long walks on the beach, dying repeatedly in roguelikes and ripping and tearing in FPS games. I also sometimes write code and sometimes that includes hobbyist game development.
See more from me
The comments on this article are closed.
29 comments
Page: 1/3»
  Go to:

Bumadar Sep 13, 2013
no startup issues here (opensuse, pure /home install), but since this morning the internal browser seems to be broken, so store, community etc. etc. all give "error code -130, failed to load webpage" back.  Library works fine.

switching from beta back to normal solves the issue.  appcache has no effect on this.
Mike Frett Sep 13, 2013
I think it's a sever side issue or regional perhaps. I just opened and browsed around a while and didn't have any issues. I don't use the Beta though so perhaps it's a Beta issue.
Anonymous Sep 13, 2013
Thanks that actually helped me (Ubuntu 13.10).
Liam Dawe Sep 13, 2013
I am not using the beta and it affects me, looks like it's a general Steam issue.
mattyy1hp Sep 13, 2013
Oh my god it helped. Thank you very much! I was trying to solve this problem last 2 hours.
strg Sep 13, 2013
helped on Manjaro too
Thanks!
Guest Sep 13, 2013
Not had any issues using either the BETA or non-BETA, internal browser has also been fine (I use the BETA on my desktop and non-BETA on my Laptop) -- both running Arch x86_64.
Ivancillo Sep 13, 2013
This subject reminds me some things TheEnigmaticT said the other day here in GOL.

About breaking compatibility as the systems upgrades.
Seems that he was/is right at this point. (Why this issue appeared with just no modification of the program? : cause the modification of the host OS (upgrades) ).

But in the other hand ... Yes, it happened, but it's not so terrific like he explained to us.

People reacted inmediatly to support users just the problem appeared.

And the issue is solutionated. No casualities, no need to refund to anyone. Not so terrific.
We Linux users are used to manage program issues as a normal thing.
Liam Dawe Sep 13, 2013
It's nothing to do with a system update breaking Steam, Steam recently got an update and broke itself.
Samsai Sep 13, 2013
Quoting: IvancilloThis subject reminds me some things TheEnigmaticT said the other day here in GOL.

About breaking compatibility as the systems upgrades.
Seems that he was/is right at this point. (Why this issue appeared with just no modification of the program? : cause the modification of the host OS (upgrades) ).

But in the other hand ... Yes, it happened, but it's not so terrific like he explained to us.

People reacted inmediatly to support users just the problem appeared.

And the issue is solutionated. No casualities, no need to refund to anyone. Not so terrific.
We Linux users are used to manage program issues as a normal thing.
This can be compared to broken compatibility to some extent, though the issue itself is probably a programmer error somewhere, but it really shows how the Linux community works when problems arise: some people figure out a fix for the problem and tell about it to others, who in turn spread the word exponentially throughout the whole community.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.