protonscr

[SOLVED] CaveStory+ failing to run

steamclosed reviewed3rd party game
ValveSoftware/steam-for-linux#2266 · opened 2013-04-04 by GarlandKey · updated 2013-05-31 · 8 comments · github
GGarlandKey 2013-04-04 github

I recently was able to install and run CaveStory+ successfully. Now, it will not run and I get litany of errors.

Here is a dump of the errors: http://pastebin.com/8gjjNk9X

Here is my system info: http://pastebin.com/uCG6ShNV

Jjohndrinkwater 2013-04-04 github

The installscript.vdf error can be ignored, its just a steam client warning.

If you open a terminal, navigate to Steam/SteamApps/common/Cave Story+ where CaveStory+ is installed and run LD_LIBRARY_PATH=~/.steam/bin/ ./CaveStory+ does it load successfully?

GGarlandKey 2013-04-04 github

With Steam running, I get the following output:

# LD_LIBRARY_PATH=~/.steam/bin/ ./CaveStory+
Setting breakpad minidump AppID = 200900
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198006657008 [API loaded no]
Segmentation fault (core dumped)
Jjohndrinkwater 2013-04-04 github

ok, looks like it might not be a steam runtime issue.
Would you try this LD_LIBRARY_PATH=~/.steam/bin/ gdb ./CaveStory+ and when the prompt appears, type run, wait for it to crash, and then type bt and paste the output here.

GGarlandKey 2013-04-04 github

Here it is:

# 0  0x00000000 in ?? ()
# 1  0x080cc232 in ?? ()
# 2  0x080ccd35 in ?? ()
# 3  0x080ca6d2 in ?? ()
# 4  0x0804bb99 in ?? ()
# 5  0xf7b4b7c3 in __libc_start_main () from /usr/lib32/libc.so.6
# 6  0x0804be89 in ?? ()
Ggdrewb-valve maintainer 2013-04-04 github

You should mention this to the game developer also.

GGarlandKey 2013-04-04 github

I've sent the error information and this thread to Studio Pixel.

GGarlandKey 2013-05-24 github

I've spoken with a developer from Studio Pixel. This is a known bug that only happens with systems using multiple monitors. Temporary fix is to either disable all but one monitor when playing, or run the game in windowed mode.

Ggdrewb-valve maintainer 2013-05-31 github

Closing this since it's confirmed to be an app problem and not a Steam problem. This issue can still be found by people with similar problems even when closed.

Nothing extracted yet.