[SOLVED] Steam segfaults (fresh install)

ctown.myth · 2013-02-09 19:21:36

Hello,

I did a fresh install of Arch on my laptop today, and after installing Steam, I couldn't start it. Here's the output from terminal, I can't find anything that stands out. Any help?

[mycookie@TheCookieBox ~]$ steam
Running Steam on arch  64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
unlinked 0 orphaned pipes
removing stale semaphore last operated on by process 4456 with name 0eBlobRegistryMutex_9C996DCA812DFD99E5CA72A9A86B8F99
removing stale semaphore last operated on by process 4456 with name 0eBlobRegistrySignal_9C996DCA812DFD99E5CA72A9A86B8F99
removing stale semaphore last operated on by process 4456 with name 0emSteamEngineInstance
removing stale semaphore last operated on by process 4456 with name 0eSteamEngineLock

(steam:4565): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
[0209/051316:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Uploading dump (in-process) [proxy '']
/tmp/dumps/crash_20130209051316_1.dmp
success = yes
response:  CrashID=bp-c29e0475-eea2-4f18-aab6-9ece02130209
/home/mycookie/.local/share/Steam/steam.sh: line 561:  4565 Segmentation fault      (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@"

Steam was working before on the same laptop, however it was from AUR, this is fresh from [community].

Last edited by ctown.myth (2013-02-09 22:23:17)

HalosGhost · 2013-02-09 19:39:21

This is a Steam-runtime issue. It has already been reported upstream, and a fix has already been proposed. The issue is slated to be fixed in the next release (no date given). Having said that, you can still run it without issue by passing STEAM_RUNTIME=0 first. That is to say:

$ STEAM_RUNTIME=0 steam

I am not sure if there are any negative ramifications to running it this way, but I have yet to have any problems.

All the best,

-HG

ctown.myth · 2013-02-09 20:02:30

HalosGhost wrote:

This is a Steam-runtime issue. It has already been reported upstream, and a fix has already been proposed. The issue is slated to be fixed in the next release (no date given). Having said that, you can still run it without issue by passing STEAM_RUNTIME=0 first. That is to say:
$ STEAM_RUNTIME=0 steam
I am not sure if there are any negative ramifications to running it this way, but I have yet to have any problems.
All the best,
-HG

Thanks! That worked, but now I have some other issues. After starting steam, it said that it needed more packages (lib32 of pango, gtk2, cairo, nss, libpng12, nspr, libcups and gcrypt). But after installing them I get an Assert fail:

[mycookie@TheCookieBox ~]$ STEAM_RUNTIME=0 steam
Running Steam on arch  64-bit
STEAM_RUNTIME is disabled by the user
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Looks like steam didn't shutdown cleanly, scheduling immediate update check
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
unlinked 0 orphaned pipes
removing stale semaphore last operated on by process 7725 with name 0eBlobRegistryMutex_9C996DCA812DFD99E5CA72A9A86B8F99
removing stale semaphore last operated on by process 7725 with name 0eBlobRegistrySignal_9C996DCA812DFD99E5CA72A9A86B8F99
removing stale semaphore last operated on by process 7725 with name 0emSteamEngineInstance
removing stale semaphore last operated on by process 7725 with name 0eSteamEngineLock
Main.cpp (1922) : Assertion Failed: !"Fatal Error: VGUI_Setup failed"
Assert( Assertion Failed: !"Fatal Error: VGUI_Setup failed" ):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamui/Main.cpp:1922
 
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
Uploading dump (in-process) [proxy '']
/tmp/dumps/assert_20130209055442_1.dmp
success = yes
response:  CrashID=bp-a75a6dea-e036-4fc5-a092-5376d2130209
Shutting down. . .
unlinked 2 orphaned pipes
Installing breakpad exception handler for appid(steam)/version(1360379549_client)
CAsyncIOManager: 0 threads terminating.  0 reads, 0 writes, 0 deferrals.
CAsyncIOManager: 159 single object sleeps, 0 multi object sleeps
CAsyncIOManager: 0 single object alertable sleeps, 1 multi object alertable sleeps

Also, I was under the impression that the dependencies for the packages I had to install were now shipped with Steam? Which is why they were removed from the dependency list when it was in the AUR.

gtmanfred: Steam was a lot more simple when it was in the AUR .

WorMzy · 2013-02-09 20:02:55

Try the fix provided in the first reply to this topic: http://steamcommunity.com/app/221410/di … 425424867/

ctown.myth · 2013-02-09 20:06:46

WorMzy wrote:

Try the fix provided in the first reply to this topic: http://steamcommunity.com/app/221410/di … 425424867/

Is that safe? I just did a fresh install last night, and certainly don't want to do it again .

ctown.myth · 2013-02-09 20:11:55

Well I tried it anyways, and it works! I didn't need to disable Steam runtime, either. Hopefully I don't have to come back here to complain that it broke my pluseaudio .

Thanks, everyone!

EDIT: I can't find where to add [SOLVED], can a mod add that to the topic?

Last edited by ctown.myth (2013-02-09 20:15:38)

WorMzy · 2013-02-09 20:12:25

I can't guarantee that it's safe, only that it worked for me.

HalosGhost · 2013-02-09 22:21:40

The proposed fix was merged upstream a couple of hours ago, you shouldn't need to disable steam-runtime anymore. You add [SOLVED] to your topic by editing your OP and putting it in the post title.

All the best,

-HG

Arch Linux

#1 2013-02-09 19:21:36

[SOLVED] Steam segfaults (fresh install)

#2 2013-02-09 19:39:21

Re: [SOLVED] Steam segfaults (fresh install)

#3 2013-02-09 20:02:30

Re: [SOLVED] Steam segfaults (fresh install)

#4 2013-02-09 20:02:55

Re: [SOLVED] Steam segfaults (fresh install)

#5 2013-02-09 20:06:46

Re: [SOLVED] Steam segfaults (fresh install)

#6 2013-02-09 20:11:55

Re: [SOLVED] Steam segfaults (fresh install)

#7 2013-02-09 20:12:25

Re: [SOLVED] Steam segfaults (fresh install)

#8 2013-02-09 22:21:40

Re: [SOLVED] Steam segfaults (fresh install)

Board footer