LinuxQuestions.org - [SOLVED] Can't run steam on multilib slackware current

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Can't run steam on multilib slackware current (https://www.linuxquestions.org/questions/slackware-14/cant-run-steam-on-multilib-slackware-current-4175580624/)

Can't run steam on multilib slackware current

I have a working multilib setup and I'm running on slack current. I have installed alienbob's multilib packages and I have run massconvert32.sh and upgradepkg --install-new on all of them. Steam complains with this every time

Code:

Couldn't find dpkg, please update steamdeps for your distribution.

Running Steam on slackware 14.2 64-bit

STEAM_RUNTIME is enabled automatically

Error: You are missing the following 32-bit libraries, and Steam may not run:

libc.so.6

Installing breakpad exception handler for appid(steam)/version(1461972496)

Installing breakpad exception handler for appid(steam)/version(1461972496)

Installing breakpad exception handler for appid(steam)/version(1461972496)

Fontconfig error: "/home/todd/.config/fontconfig/fonts.conf", line 1: not well-formed (invalid token)

../vgui_surfacelib/FontManager.cpp (276) : Assertion Failed: descs.Count() >= 1

Assert( Assertion Failed: descs.Count() >= 1 ):../vgui_surfacelib/FontManager.cpp:276



Installing breakpad exception handler for appid(steam)/version(1461972496)

/home/todd/.steam/ubuntu12_32/steamwebhelper: error while loading shared libraries: libgnutls.so.26: cannot open shared object file: No such file or directory

crash_20160524232619_5.dmp[22639]: Uploading dump (out-of-process)

/tmp/dumps/crash_20160524232619_5.dmp

../vgui_surfacelib/FontManager.cpp (276) : Assertion Failed: descs.Count() >= 1

../vgui_surfacelib/FontManager.cpp (276) : Assertion Failed: descs.Count() >= 1

../vgui_surfacelib/FontManager.cpp (276) : Assertion Failed: descs.Count() >= 1

../common/steam/client_api.cpp (326) : Assertion Failed: ClientAPI_InitGlobalInstance: InternalAPI_Init_Internal failed, most likely because you are missing a 32-bit dependency of steamclient.so (the Steam client is a 32-bit app).



SteamStartup.cpp (809) : Assertion Failed: ! "There was a problem with your Steam installation.\n" "Please reinstall steam.\n"

crash_20160524232619_5.dmp[22639]: Finished uploading minidump (out-of-process): success = yes

crash_20160524232619_5.dmp[22639]: response: CrashID=bp-1f69b7bb-9c43-4e47-952d-b54f72160524

crash_20160524232619_5.dmp[22639]: file ''/tmp/dumps/crash_20160524232619_5.dmp'', upload yes: ''CrashID=bp-1f69b7bb-9c43-4e47-952d-b54f72160524''

[2016-05-24 23:26:18] Startup - updater built Apr 29 2016 22:18:33

[2016-05-24 23:26:18] Verifying installation...

[2016-05-24 23:26:18] Verification complete

[2016-05-24 23:26:20] Shutdown

Quote:

Originally Posted by MarioMaster100 (Post 5550450)

Code:

Couldn't find dpkg, please update steamdeps for your distribution.

Running Steam on slackware 14.2 64-bit

STEAM_RUNTIME is enabled automatically

Error: You are missing the following 32-bit libraries, and Steam may not run:

libc.so.6

Seems you forgot to install package glibc-2.23_multilib-x86_64-1alien.txz. You should also check that packages below are installed :

Quote:

Originally Posted by MarioMaster100 (Post 5550450)

Code:

/home/todd/.steam/ubuntu12_32/steamwebhelper: error while loading shared libraries: libgnutls.so.26: cannot open shared object file: No such file or directory

You get this because one (or more) of the packages below is not installed :

--
SeB

Quote:

Originally Posted by phenixia2003 (Post 5550491)

Seems you forgot to install package glibc-2.23_multilib-x86_64-1alien.txz. You should also check that packages below are installed :

You get this because one (or more) of the packages below is not installed :

--
SeB

Well I have those packages

Code:

ls /var/log/packages|grep glibc

glibc-2.23_multilib-x86_64-1alien

glibc-i18n-2.23_multilib-x86_64-1alien

glibc-profile-2.23_multilib-x86_64-1alien

glibc-solibs-2.23_multilib-x86_64-1alien

glibc-zoneinfo-2016d-noarch-1

and

Code:

 ls /var/log/packages|grep gnutls

gnutls-3.4.11-x86_64-1

gnutls-compat32-3.4.11-x86_64-1compat32

I guess steam just can't figure that one out.

Strange I just downloaded Steam from with sbopkg from current and it worked fine. I even downloaded a game and it worked perfectly.

Had not got around to installing with current but I use it with 14.1.

Glad there is no problem with it.

As far as it not working for you can you run other 32bit programs without a problem ?

After I install multilib I always install Doom 3 to make sure it is working :)

I wonder if they will port the current Doom I like that one :D

Yeah I ran a music program that was only 32bit fine, steam apparently hates me :/

I ran into this exact same problem, but ONLY when running a game called Bound By Flame. You're not, by chance, trying to run that game are you?

I don't have that game and the problem is when simply running

Code:

steam

, the program itself.

Quote:

Originally Posted by TarFile (Post 5550994)

I wonder if they will port the current Doom I like that one :D

I was just discussing how much it sucks that we can't even count on native versions of id titles anymore.

Out of curiosity, should I stick with multilib with 14.2 to ensure my Steam games work? I am pretty sure I screwed some things up, but I haven't run into any problems yet. I was going to skip multilib next time since I don't think I need it.

Where'd you get steam?

And what is the output of:

Code:

locate libc.so.6

grep libc.so.6 /var/log/packages/*

Quote:

Originally Posted by MarioMaster100 (Post 5550450)

I have installed alienbob's multilib packages and I have run massconvert32.sh and upgradepkg --install-new on all of them.

I'm also curious about this line. If you got all of his multilib packages, there's no need to run massconvert32.sh. That is only if you have a 32bit tree of Slackware-current and want to create your own compat32 packages rather than using his. There is no need to run massconvert32.sh on 32bit pacakges that are already designed for installation on a 64bit Slackware install.

Quote:

Originally Posted by bassmadrigal (Post 5551562)

Where'd you get steam?

And what is the output of:

Code:

locate libc.so.6

grep libc.so.6 /var/log/packages/*

Note:
The grep will return nothing. libc.so.6 is a symlink (/lib/libc.so.6 -> libc-2.23.so) , created by doinst.sh from glibc-2.23_multilib (and glibc-solibs-2.23_multilib).

--
SeB

Quote:

Originally Posted by bassmadrigal (Post 5551562)

This needs a bit of clarification then.

The only official "multilib packages" that I carry in my repository are the multilib versions of glib and gcc, and the compat32-tools package was added so that you can create a set of compatibility packages and are able to run and compile software on Slackware.
The massconvert32.sh script is provided by the compat32-tools package and allows you to create a default set of packages which together create a 32bit compatibility layer on top of your 64bit installation of Slackware - hence the "-compat32" strings in their package names.

I do offer a directory "slackware64-compat32" in my multilib repository for every version of 64bit Slackware, which contains all the "-compat32" packages converted from the official 32bit Slackware using the massconvert32.sh script. That directory and its content was only added because a lot of people asked for ready-made compat32 packages instead of running the massconvert32.sh script themselves. Really, it saves you a few minutes at most when you do not have to run "massconvert32.sh"... but there you have it.

With the introduction of the "slackpkg+" extension to slackpkg it became a lot more convenient to have these re-packaged "-compat32" packages already available in the multilib repository because maintenance of your multilib layer becomes a lot easier using it. So I left the "slackware64-compat32" directory in, and keep updating it with the latest packages. However keep in mind that for me keeping the content of "slackware64-compat32" up to date is not a high priority.

Alright I figured out the problem if you run brew (linuxbrew.sh), don't add ~/.linuxbrew/ to your path and it doesn't do this nonsense to you.