Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Are you using the Steam package from the official Ubuntu repo? The Steam directory name that you have suggets you do. If so, perhaps there's something wrong with the package? I had some bad luck getting it to work with some games and reverted to the official Valve package.
Also, here is the relevant ldd line for me:
libSDL2-2.0.so.0 => /home/xxx/.local/share/Steam/ubuntu12_32/libSDL2-2.0.so.0
Not sure why that's not happening on your machine.
Regardless of the possible causes and culprits, a possible workaround should be running the game as
$ LD_LIBRARY_PATH=~/.steam/ubuntu12_32:. ./crimsonland
from its directory.
I switched to the official Ubuntu Steam app (version 1:1.0.0.48-1ubuntu1) few months ago, without any problem so far.
`ldd crimsonland` does return : "libSDL2-2.0.so.0 => not found", and :
Using `LD_LIBRARY_PATH=~/.steam/ubuntu12_32:. ./crimsonland` is a working workaround, but I'm pretty sure most users do not know how (or even want) to type this kind of commands to fix a game, so perhaps there is a more user-friendly way to fix this?
What I was getting at was that maybe, since the directory layout is different on your system with that Ubuntu Steam package of yours (note that the shared Steam libraries on your system are at ~/.steam/ubuntu12_32, while mine are at ~/.local/share/Steam/ubuntu12_32), your Steam version cannot pass the library paths to the game properly, or something along those lines. (which is a problem of course, but likely that of the Ubuntu Steam package, and not the game's).
I think you should try the official Valve package that I linked, I highly suspect that it will get rid of the problem.
That's not how that works. LD_LIBRARY_PATH specifies additional library paths for the program IN ADDITION to the standard paths, so it should normally be empty. (see http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html, paragraph 3.3.1) Somewhat surprised yours isn't. The standard way to add a library path to Ubuntu should be adding it to /etc/ld.so.conf.d/ or /etc/ld.so.conf, and then re-running ldconfig. Can't tell if that's part of the problem for you.
The Steam client does set LD_LIBRARY_PATH to point to additional library directories when running games (hence if you run ldd from within Steam, it is supposed to "find" that SDL library), but you'll be able to see the change only from within the client. Try changing the launch options to
Well, you could create a symlink to the library in the game directory.
Or Right click the game in the Steam client, pick "Properties", then "Set options", type
I already added that specific command line in order to be able to launch Crimsonland, but I was more thinking about a general fix (install -> play -> this works out of the box-style) :)
I'd prefer not changing (again) of Steam installation source, since when you switch from the ubuntu version to the valve one (and vice versa), you have to reconfigure quite a lot of stuff manually (ie. family sharing stuff, etc.) in order to keep your settings unchanged and not having to reinstall all your games.
Note : both steam installation auto-updates themselves with Valve so I'm surprised there are different paths to the config/game files.
What's your LD_LIBRARY_PATH when running Crimsonland from Steam? Can you set the launch options to those that I gave you earlier:
The result should be no different, except for the last two Braid-specific directories. What surprises me is that you've got the path where libSDL is at (/home/acid/.steam/ubuntu12_32), which means the library path SHOULD be passed to Crimsonland and detected without any problems.
Also, just to make sure, are you running Crimsonland from Steam directly? Running games from their directory while circumventing the Steam client is not the standard way to launch Steam games.
I can see no problem with the line, since the libSDL directory is already included in it at the game startup. Since you've already confirmed that passing LD_LIBRARY_PATH manually fixes the problem, the game should start fine if you remove all the command line arguments and click that "Play" button in the Steam client. If it doesn't start if you click "play", what exactly happens? I'm starting to sense some miscommunication problem with this whole thing.
Ok now, I removed `LD_LIBRARY_PATH=~/.steam/ubuntu12_32:. ` from the crimsonland steam command line properties, clicked play and....today, Crimsonland launches well!
Very, very weird that it did not yesterday!!
Yesterday, when I did the exact same thing, just saw a glitch on my screen where you could see the application was launching, but instead of showing the game logo, it showed a 'screenshot' of my whole screen (and this was offset a bit toward the upper side, by about the size of my window decoration), then had to kill the 'unresponsive app' with ctrl+alt+esc, then click.
Any idea why?
If that happens again, I'll be a bit confused about what broke/made it to work again...
... and yet you only did the debug run that I asked to perform. It was not supposed to launch the game itself, its only purpose was to show what directories are being searched for dynamic libraries at startup. You did not say the game was actually working until I explicitly requested to try and run it.
If the game fails to run due to a missing library (which was your original accusation in the topic), it doesn't do or show anything aside from a text message in the console that some library is missing. You did include such message in the original post, but overlooked the fact that LD_PRELOAD_PATH needed to be set up appropriately in order to launch the game from outside the client.
Beats me, might be because some graphical drivers on Linux are not very stable, and need a restart once in a while, especially when the user is screwing around with some kernel parameters. :s
Thanks for your help!