Game doesn't start on linux

[Profile Name]

When trying to run RogueLegacy on my linux notebook, all I get is a black window with title "MonoGame-SDL2 Window", and it hangs there. It doesn't respond to any input, I have to kill -9 it. It's not a steam related problem as the standalone version (from humble store) does the same thing.

Video card: NVidia GT320M, with propertiary drivers 331.20
OS: Gentoo Linux, amd64

[flibitijibibo]

I got a couple reports saying it was fixed when run in terminal outside of Steam, does this work for you?

I haven't been able to get a GDB trace of the hang yet, but I'm guessing it's something going on at SDL2->X11's level. It may be resolved by updating my libSDL2 sofile to SDL2 2.0.1 (we're still on 2.0.0), but I'll need to check that out as well.

[Profile Name]

I've tried running it from a terminal, with no luck.

About SDL: i quickly tried to replace libSDL2-2.0.so.0 in lib64 with my system libsdl, but in that case it doesn't draw anything to the window (whatever was in place of the window remains).

[Profile Name]

Interesting. I've realized that gdb is broken again (doesn't stop on breakpoints, ctrl-c is ignored). I have no idea what causes this, but probably has something to do with hibernation, as it only happened a few times after a long uptime, and the only solution I've found so far is to reboot the whole system. And it also fixed Rogue Legacy.

And I thought reboot system to fix problems is a windows only thing... :)

[Tom]

I'm also having this problem. Any updates on this front?

[flibitijibibo]

I got another possible fix from someone this morning, see if this works:

1. Exit Steam
2. Start Steam via terminal
3. Run Rogue (may pass or fail), exit (or kill) game
4. Exit Steam
5. Run Rogue (if it complains about Steamworks, start Steam with terminal again)

I'm starting to wonder if all the problems lie in user permission problems with the Rogue files. This does make a bit of sense, as it would explain why it randomly affects all of my MG-SDL2 titles. Would explain why rebooting works, too.

If we can find a reproducible way to resolve the problem, I'll look into fixing it, or filing it with the right people if I can't do it myself.

[Nubby101]

i seem to be having the same problem but i'm running windows 8 :(

[Cellar Door Games]

@Nubby101

If you're having problems on a Windows machine, then your errors are probably entirely different. Here's a list of suggested fixes:

- Update video card drivers.

- Verify game files (Steam only).

- Reinstall the .NET and XNA framework files (please restart your system after re-install). The file locations are listed below:

Steam location:

Program Files (x86)\Steam\steamapps\common\Rogue Legacy\_CommonRedist\XNA
Program Files (x86)\Steam\steamapps\common\Rogue Legacy\_CommonRedist\DotNet

Standalone location:

The install directory of the game.
(xnafx40_redist.msi)
(dotNetFx40_Client_x86_x64.exe)

Also, please check to see if you have any crash logs appear when you run the game. Instructions on how to find your crash logs can be found here:

http://steamcommunity.com/app/241600/discussions/1/846957366713233279/

[Dust]

This may be an issue with a recent nvidia-libgl release on arch that appears to be affecting a number of applications, especially mono-based ones (i became aware of it due to keepass stopping working). Here are some links to relevant info.

https://bbs.archlinux.org/viewtopic.php?pid=1351879

https://devtalk.nvidia.com/default/topic/633706/linux/recent-drivers-cause-applications-to-hang-not-start-at-all-or-compilation-failures

Until the driver is fixed the only solution appears to be either running running the applications manually from a command-line (with mixed success :<) or to replace nvidia-libgl with an alternative such as mesa-libgl

[rabozacherl]

Same problem here. Current proprietary NVIDIA Driver. Replaced SDL by 2.0.1 does not help.
Running in gdb and breaking at the point of freeze points out a threading problem:

Program received signal SIGINT, Interrupt.
0x00007ffff6f6eff0 in sem_wait () from /usr/lib/libpthread.so.0
(gdb) bt
#0  0x00007ffff6f6eff0 in sem_wait () from /usr/lib/libpthread.so.0
#1  0x00007ffff7aa991a in pthread_stop_world () at pthread_stop_world.c:450
#2  0x00007ffff7aa99c3 in GC_stop_world () at pthread_stop_world.c:603
#3  0x00007ffff7a95246 in GC_stopped_mark (stop_func=0x7ffff7a9483f <GC_never_stop_func>) at alloc.c:503
#4  0x00007ffff7a94f59 in GC_try_to_collect_inner (stop_func=0x7ffff7a9483f <GC_never_stop_func>) at alloc.c:382
#5  0x00007ffff7a961ff in GC_collect_or_expand (needed_blocks=2, ignore_off_page=0) at alloc.c:1045
#6  0x00007ffff7a9b826 in GC_alloc_large (lw=1024, k=1, flags=0) at malloc.c:60
#7  0x00007ffff7a9bc66 in GC_generic_malloc (lb=8192, k=1) at malloc.c:204
#8  0x00007ffff7a9bf91 in GC_malloc (lb=8192) at malloc.c:311
#9  0x00007ffff7aa786c in GC_local_malloc (bytes=8192) at pthread_support.c:332
#10 0x00007ffff79d10eb in ves_icall_Type_GetMethodsByName (type=<optimized out>, name=0x0, bflags=40, ignore_case=<optimized out>, 
    reftype=<optimized out>) at icall.c:3577
#11 0x00000000400c61bf in ?? ()
#12 0x0000000000605b00 in ?? ()
#13 0x00007ffff7fb6750 in ?? ()
#14 0x0000000000000000 in ?? ()

Do you have a bug tracker, or is this the official way of dealing with problems?

[rabozacherl]

I can confirm that the problem is the NVIDIA driver. The game runs fine with nouveau.
I also use GNOME. This may be releated:

https://bugzilla.gnome.org/show_bug.cgi?id=719891

Also SDL 2.0.1 seems to improve the drawing performance. I symlinked the so file from the sdl2 ArchLinux package to the game lib64 directory to make this work.

[flibitijibibo]

Hm, not sure about the 2.0.1 perf thing, but the NVIDIA/GNOME thing is definitely new. I wonder where GNOME fits into all of this, as I've gotten a similar report from AMD users. Of course, I've also gotten this from users on XFCE... this bug is certainly a doozy.

Thanks a bunch for the gdb trace though. If we're stuck on that thread, then we can blame the C# garbage collector for picking up something that it's not supposed to. This is similar to the OSX hang on exit too... such a mess, garbage collection.

[rabozacherl]

Running the game with the NVIDIA driver also works if you impersonate your own user with sudo.

sudo -u <my_username> ./RogueCastle.bin.x86_64

[CrazyMammut]

It stopped working on my fedora 20 box after updating to mesa 10. I don't know if it's relevant but I also tried with STEAM_RUNTIME=0 (I have SDL 2.0.2 installed) and it does not start either.

[CrazyMammut]

Now it works with the last mesa 10.0 version, sorry for the noise.