Linux Beta client hanging on current update

[intok]

So I just installed the current update and the client hangs, pegging the CPU. It displays nothing on screen, but does show up in the system monitor and must be force quit to exit.

Terminal output

steam %U
Running Steam on linuxmint 13 32-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1379035603_client)
Installing breakpad exception handler for appid(steam)/version(1379035603_client)
Installing breakpad exception handler for appid(steam)/version(1379035603_client)
Installing breakpad exception handler for appid(steam)/version(1379035603_client)
unlinked 0 orphaned pipes
removing stale semaphore last operated on by process 30145 with name 0eBlobRegistryMutex_210CA16FEE060E8A96CC7ED140C792E8
removing stale semaphore last operated on by process 30145 with name 0eBlobRegistrySignal_210CA16FEE060E8A96CC7ED140C792E8
removing stale semaphore last operated on by process 30145 with name 0emSteamEngineInstance
removing stale semaphore last operated on by process 30145 with name 0eSteamEngineLock
Installing breakpad exception handler for appid(steam)/version(1379035603_client)
[0913/153654:WARNING:proxy_service.cc(958)] PAC support disabled because there is no system implementation

[Fugue]

I think I encountered this in the release version as well. Try:

Killing steam from system monitor or using killall
When no instances of steam are running,
go to ~/.local/share/Steam folder (or wherever you have Steam installed) and delete the appcache folder. You can do this through nautilus by getting to the location through CTRL+L or through the terminal with this command: rm -Rf ~/.steam/steam/appcache

Start it and it should work. Unfortunately, when you exit steam and want to restart... you will have to repeat this process. Hopefully they will fix it soon!

[scottlu]

Thank you for reporting this.

Here is how to fix it.

1. Fully exit Steam
2. Remove this file: ~/.local/share/Steam/appcache/appinfo.vdf
3. Restart Steam

We are working on a fix that won't require these steps. It will be available in the near future and will be available to users enrolled in the public beta.