[SOLVED] Slackware -current and Unity based games on steam not working?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware -current and Unity based games on steam not working?
Since the past week or so, i've noticed that any game using the Unity engine on steam, refuses to load.
Can anyone with any steam games that run under Unity confirm if they are having the same problem? As two games which have had no updates in months are suddenly not launching.
2 games i've tested:
* Dungeons II
* 7 Days to Die
When trying to launch them, you just get a black screen, and have to kill the process manually.
It seems like some other system package may be causing this? I've tried downgrading my nvidia driver to a previous version which worked fine with the games, however it still shows the black screen.
Would anyone be able to explain why this lets the game run?
Edit: This seems to cause problems with the steam client itself, mostly with the built in web browser when navigating the store / forums. Although, it still works to let Unity games run.
It has to do with the upgrade to glibc to version 2.25 and a change to malloc. The LD_PRELOAD allows you to use a different malloc implementation that works with Unity.
Thanks. I had no idea that jemalloc was included in slackware. I had tried to fix this problem with unity games the other day using jemalloc. I looked on slackbuilds.org and it wasn't there so I downloaded it from github and built it and used it which got me a bit further but the games crashed after a few secs. Using the system installed one everything seems ok.
I was thinking about downgrading glibc if it didn't get fixed soon, but it seems the solution was already installed. I'm glad someone else posted the problem before I went and messed up my glibc
I ran across this bug the other day. Glad someone had already found a fix. Of course, the developer has to point me to this thread.
One thing I discovered, this only affected x86_64 games. x86 binaries ran fine.
Using jemalloc has been working for me for a while now, but I noticed that whenever I start steam this way then the steam store/activity/profiles (all the web stuff) doesn't work. Anyone else have that problem?
I can just start steam normally and then just launch the game from the command line using jemalloc, but some games don't like that.
Using jemalloc has been working for me for a while now, but I noticed that whenever I start steam this way then the steam store/activity/profiles (all the web stuff) doesn't work. Anyone else have that problem?
I can just start steam normally and then just launch the game from the command line using jemalloc, but some games don't like that.
Yes i noticed that almost immediately, but as dugan suggested, modifying the launch options per each game effected is a nice workaround, i just tried it now with the Unity games (7DaysToDie and Dungeons II), setting this works fine, whilst allowing the store/browser to function normally.
Oh thanks. I thought the launch options only allowed you to pass args to be appended to the command. Didn't know you could add stuff before the command too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.