Arch Linux

doorknob60

Member

Registered: 2008-09-29

Posts: 404

[solved] Super Meat Boy segfault

EDIT: Fixed it! I deleted my ~/.local/share/SuperMeatBoy folder and it was fixed. Somehow my savefile got corrupt I guess. I didn't want to delete this because I didn't want to lose my progress, but my progress is still there so Steam Cloud must have downloaded a new copy. Either way, problem solved!

Whenever I try to launch Super Meat Boy from Steam, nothing shows up. I navigated to the directory in steamapps and ran the executable, and this is the output:

 ./SuperMeatBoy 
Super Meat Boy: Installed in '/home/[user]/Steam/SteamApps/common/Super Meat Boy'.
Super Meat Boy: Using amd64 version.
Segmentation fault (core dumped)

I'm using Kernel 3.13.5, with a GeForce 9800 GT with Nvidia drivers 331.49.

This game worked last time I played it (a few weeks ago), and my other Steam games work fine.

Last edited by doorknob60 (2014-02-28 21:13:09)

Rexilion

Member

Registered: 2013-12-23

Posts: 784

Re: [solved] Super Meat Boy segfault

Check /var/log/pacman.log for upgrades and look for suspicious entry's. Like the kernel, mesa and xorg.

---

fs/super.c : "Self-destruct in 5 seconds.  Have a nice day...\n",

blackout23

Member

Registered: 2011-11-16

Posts: 781

Re: [solved] Super Meat Boy segfault

Try running "GAME_DEBUGGER=gdb steam" and then starting Super Meat Boy and let it sefault. This should give you a backtrace.
Install gdb first if you have not already.

Last edited by blackout23 (2014-02-28 14:52:24)

doorknob60

Member

Registered: 2008-09-29

Posts: 404

Re: [solved] Super Meat Boy segfault

I ran that, and seemingly get nothing useful (it looks the same as when I ran Steam without GAME_DEBUGGER=gdb): http://pastebin.com/Rup8h8A6 I do find it weird that when launched through Steam, the segmentation fault doesn't even show up as an error (it was like this without gdb too). The segfault only shows up when I manually run the game.

I see a lot of errors regarding wrong ELF class for the steam overlay library, but I disabled to overlay and got the same problem, and starting SMB without Steam at all still crashes, so I don't think it's related to that. I think Steam might try to load both the 32 bit and 64 bit overlay library for each game, and then whichever one is the wrong one will just error out (which makes since since SMB is compiled for 64 bit; Rogue Legacy also produces these warnings but the game and the overlay still work) I just tried a bunch of other Steam games (Portal 1 and 2, Thomas Was Alone, VVVVVV, Rogue Legacy, as well as Minecraft as a non Steam game), and they all work fine, so I doubt it's related to improper graphics drivers or anything.

And to Rexilion: Last night, after I noticed Meat Boy not working, I did a full update, which updated the kernel and nvidia drivers, which didn't fix the problem. I could go back forever listing different updates I did in the past, but I have no clue when the last time Meat Boy worked was, and I don't plan on downgrading a bunch of packages. Considering all my other games still work, I don't think this is the problem.

EDIT: Fixed it! I deleted my ~/.local/share/SuperMeatBoy folder and it was fixed. Somehow my savefile got corrupt I guess. I didn't want to delete this because I didn't want to lose my progress, but my progress is still there so Steam Cloud must have downloaded a new copy. Either way, problem solved!

Last edited by doorknob60 (2014-02-28 21:12:43)