LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-24-2018, 08:08 AM   #1
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
Segfault on Steam in Latest Current


Greetings
I'm still running 14.2 multilib as my main but I wanted to try out the latest Current (12/18) and it's really sweet. However with the exact same kernel and exact same steamclient version (literally copy 'n pasted the build directory from 14.2 and rebuilt for Current) does the oddest thing. First off it asks for "libnghttp2" complaining it can't be found when that file doesn't exist on 14.2 either and I've never seen a complaint error message there. What can possibly be the difference?

Edit - Well I did forget one difference that could possibly be a factor. On 14.2 originally it did have pulseaudio installed and I removed it later after trying for many months to work with it. With Current, I never installed it in the first place. As AlienBob states Steam doesn't require Pulse to work but at one time, with one version of his Steam client, it had to be there, just turned off. I have no idea if this is still an issue.

Note: I'm also having trouble with wine running old World of Warcraft 3.3.5 but I know wine works so that's an issue for WoW and another thread. The only reason I mention it is that it, too is the exact same (software) game (not merely a duplicate) and the only difference I know of is Current vs/ 14.2. Any ideas are most welcome.

Last edited by enorbet; 12-24-2018 at 08:21 AM.
 
Old 12-24-2018, 11:08 AM   #2
akimmet
LQ Newbie
 
Registered: Jul 2018
Posts: 27

Rep: Reputation: Disabled
Quote:
Originally Posted by enorbet View Post
Greetings
I'm still running 14.2 multilib as my main but I wanted to try out the latest Current (12/18) and it's really sweet. However with the exact same kernel and exact same steamclient version (literally copy 'n pasted the build directory from 14.2 and rebuilt for Current) does the oddest thing. First off it asks for "libnghttp2" complaining it can't be found when that file doesn't exist on 14.2 either and I've never seen a complaint error message there. What can possibly be the difference?

Edit - Well I did forget one difference that could possibly be a factor. On 14.2 originally it did have pulseaudio installed and I removed it later after trying for many months to work with it. With Current, I never installed it in the first place. As AlienBob states Steam doesn't require Pulse to work but at one time, with one version of his Steam client, it had to be there, just turned off. I have no idea if this is still an issue.

Note: I'm also having trouble with wine running old World of Warcraft 3.3.5 but I know wine works so that's an issue for WoW and another thread. The only reason I mention it is that it, too is the exact same (software) game (not merely a duplicate) and the only difference I know of is Current vs/ 14.2. Any ideas are most welcome.
I'm not currently having any problems with Steam at all.
When I have a problem with a missing library like this, it is almost always because I neglected to install any new packages that were added to -current.

Since you are trying to run Steam, this means installing the compat32 versions of these packages as well. Slackpkg or slackpkg+ won't install new compat32 packages automatically with slackpkg install-new.
If you have slackpkg+ installed and configured you can use slackpkg install multilib to update and install the new compat32 packages. You will need to run this again whenever there is a new package added to -current.
 
Old 12-24-2018, 12:10 PM   #3
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
Thank you akimmet, but this was a fresh install of Current not an upgrade and I immediately built multilib. I don't use slackpkg but I'm well schooled in setting up multilib. I used AlienBob's instructions for a complete list and setup all of the required compat-32 packages consistent with this release. I also followed the instructions for the extras required for Steam. The only one of any confusion is pulseaudio ad I'm unsure of why that needs to have ever been installed since Steam works fine on a pure ALSA 14.2 system. Additionally I checked and it isn't that 14.2 Multilib's Steam is working because libnghttp2 is satisfied. That library isn't anywhere on that system. I checked for it in $HOME, /lib, and /usr and it doesn't exist in either 14.2 or Current yet Steam in 14.2 works and has never complained about that library missing. That's actually what has me creating this thread. I can't even imagine why the same app calls for different libraries really on any system, but especially on 2 so similar as 14.2 and Current.

That noted, I will heed your suggestion and check yet again to make sure my package list has left out nothing, even though I am quite certain that Steam does work without libnghttp2. I just don't know why on Current it even calls for it, let alone segfaults from it's absence. I may try rebuilding Steam and adding a line to "--disable-libnghttp2" as a workaround but I'd still love to understand why that would be needed on one and not the other.
 
Old 12-24-2018, 03:25 PM   #4
akimmet
LQ Newbie
 
Registered: Jul 2018
Posts: 27

Rep: Reputation: Disabled
My -current install has a libnghttp2, it is from the nghttp2 package. However, I don't have a compat32 version installed. It looks like a pre-made compat32 version dose not exist yet. Steam will complain about this seemingly unrelated library if any of your installed 32-bit system libraries have been built with nghttp2.
I recently found this out because of Steam asking about needing libgraphite2, and Steam had worked earlier in the day without complaining about it. To add to my confusion it was the exact same Steam build version I was running earlier. Only when I went digging into the Slackware -current change-log did I notice it was a new library added a month before. I had just finished updating my multilib libraries. I put 2 and 2 together and I figured out that I need to manually check for new compat32 packages when I update.

Another thing to look into, is launching steam with it's built-in run-time disabled. I have found the old steam version included in AlienBob's package won't launch for the first time in -current with it enabled. Once Steam is updated, it will only run with it's run-time libraries enabled. This can be temporarily accomplished by running: STEAM_RUNTIME=off steam

Last edited by akimmet; 12-24-2018 at 03:40 PM. Reason: More information
 
Old 12-24-2018, 09:35 PM   #5
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
First of all thank you for taking the time to respond during such a busy time of year, akimmet. Could you tell me why you have nghttp2 installed at all? It's not part of a regular Slackware install so I'm wondering what you needed it for and how and when this became a possibly hard dependency for Steam. Eric is usually right on top of Steam changes and I haven't been seeing others complaining about nghttp2 requirements. It might be the source of my segfault or it may not but I intend to rule it out by building my own 32 bit version and then convertpkg-compat32. The fact isthis is one of the problems with non OSS. I just am really sketchy at even how to go about tracing where exactly the segfault occurs. I am reminded of old DOS days where one could opt to load config.sys line by line to discover the entire flow and where any problems existed. Maybe I'll find some time later tonight to build compat32 nghttp2 and keep trying to satisfy errors.
 
Old 12-25-2018, 03:20 PM   #6
akimmet
LQ Newbie
 
Registered: Jul 2018
Posts: 27

Rep: Reputation: Disabled
nghttp2 is an official Slackware -current package. If I'm not mistaken it was added recently. Check your local mirror and/or iso, you may have missed it. It is likely other system libraries now depend on it.
ftp://ftp.osuosl.org/pub/slackware/s...1-x86_64-1.txt

I agree commercial software on Linux can be an enormous source of frustration.

Last edited by akimmet; 12-25-2018 at 03:23 PM. Reason: Typos again.
 
Old 12-25-2018, 11:34 PM   #7
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,632

Rep: Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389Reputation: 3389
Quote:
Originally Posted by akimmet View Post
nghttp2 is an official Slackware -current package. If I'm not mistaken it was added recently.
It was added to -current back in March.
 
1 members found this post helpful.
Old 12-26-2018, 06:50 PM   #8
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
I have nghttp2 installed since I'm using the latest Current, so that isn't the problem or the question. The problem is that Steam now asks for it (only on Current, apparently) even if I copy over all Steam directories and files from my Steam install on 14.2, and fails to find it, as I expect it seeks the 32 bit version which I haven't built yet. I don't know yet if that's the cause of an actual segfault, but it does seem to be an "issue" that I must resolve. Since an official compat32 doesn't yet exist I do wonder what other Steam users are doing or if they are running into issues. The larger problem is just me, that because of the way Steam loads from steam.sh which alters the somewhat fluid executable I'm unsure how to run something like "ldd" to trace what it actually requires or precisely what is a hard dependency and what can "workaround".
 
Old 12-27-2018, 02:27 PM   #9
akimmet
LQ Newbie
 
Registered: Jul 2018
Posts: 27

Rep: Reputation: Disabled
Quote:
Originally Posted by enorbet View Post
I have nghttp2 installed since I'm using the latest Current, so that isn't the problem or the question. The problem is that Steam now asks for it (only on Current, apparently) even if I copy over all Steam directories and files from my Steam install on 14.2, and fails to find it, as I expect it seeks the 32 bit version which I haven't built yet. I don't know yet if that's the cause of an actual segfault, but it does seem to be an "issue" that I must resolve. Since an official compat32 doesn't yet exist I do wonder what other Steam users are doing or if they are running into issues. The larger problem is just me, that because of the way Steam loads from steam.sh which alters the somewhat fluid executable I'm unsure how to run something like "ldd" to trace what it actually requires or precisely what is a hard dependency and what can "workaround".
Did you download AlienBob's pre-made compat32 packages or did you generate them yourself? If you generated them yourself, they may be slightly newer than the ones AlienBob generated. These newer packages may have been built with nghttp2 as a dependency.
 
Old 12-27-2018, 09:26 PM   #10
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
Good point, akimmet! I downloaded all available but had to build 2 or 3 so far. So now I need to check my records as to which 3 they were and see if it is those that are calling nghttp2 when Steam is launched. Thanks. I hadn't thought of that.
 
Old 12-30-2018, 03:09 PM   #11
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
UPDATE - I checked all the compat32 packages (they're all correct), added a few more recommended for Steam, found a 32bit nghttp2 package for Slackware Current and converted it compat32, and tried to wade through separating what used to be required (and the workarounds) and what is now actually required, and I am at stalemate for awhile. I no longer get an error regarding libnghttp2, but it still segfaults on the tail end (line 768 or so) of steam.sh.

I'm not on Current at the moment but later I'll switch and post the exact error but I'm pretty discouraged today. It's not that I expect Current to be like a full release. I think it's the complications of compatibility that will likely exist until everything is 64 bit as well as the basic problems of software having to provide for hard coded expectations of where to find things.
 
Old 01-04-2019, 06:23 PM   #12
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
I can't mark this as solved since it isn't but unless mods want to close it, I'll just update in a month when I try a new Current release. Maybe then I can even trace why this ever occurred.
 
Old 01-05-2019, 01:18 PM   #13
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 924

Rep: Reputation: 353Reputation: 353Reputation: 353Reputation: 353
I am not having issues with Steam using Slackware64-current. Perhaps describing my setup would be of help or spark an idea.

This is my setup. Slackware64-current (Fri Jan 4 21:44:44 UTC 2019) with the latest multilib (Tue Dec 11 21:52:18 UTC 2018). I also have installed Alien Bob's ktown (Thu Jan 3 15:13:29 UTC 2019). The package installed is steamclient-1.0.0.54-i386-1alien.tgz. Steam has been installed a while, at least since September 5, 2016 (oldest directory in ~/.local/share/Steam). I am fairly certain it's been a lot longer.

At the time I remember of at least two requirements, flashplayer-plugin and OpenAL. I am fairly certain OpenAL is no longer needed for Steam. I say this based on two things. 1) there are OpenAL libraries are located under ~/.local/share/Steam 2) At some point I removed the compat32 packages I created for OpenAL. Steam is working fine without a compat32 package of OpenAL. As for flashplayer-plugin, I also create and install a compat32 package in addition to the x86_64 package. I'm not sure that even flashplay-plugin is needed any more, I removed flashplayer-plugin and all the games I have installed in Steam all work. I don't have a lot of games though, seven of them.

My video card is an NVIDIA Corporation GF108 [GeForce GT 730], recently declared a legacy card, so I am stuck with the NVIDIA Driver Version 390.87 which needs a patch applied to work with the latest kernels in -current. I was running Steam with the stock xf86-video-nouveau driver included with Slackware for a long time, after an upgrade to xorg-server made that possible. I went back to the NVIDIA drive two reasons, the first was I was trying to start Steam for another user (my son) on this computer and it was a no go. The second reason escapes me right now. Since installing the NVIDIA driver I added my son as a user on this computer then started Steam from the menu, it placed a Steam icon on the desktop, did a couple of updates (took a few minutes to complete) and Steam is now working with the new user account.
 
Old 01-07-2019, 12:35 PM   #14
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
Although I can't seem to utilize the error messages with steam since it quickly hands off to steam.sh so AFAIK things like LDD can't help, I figure there are lots of people who know way more than me so I'm going to post what I get so far, now that the nghttp2 error is solved.

Code:
 bash-4.4$ steam
Slackware 32-bit: Check the 'deps/<slackwareversion>' directory where you downloaded this package and install/upgrade the packages you find there.
Slackware 64-bit multilib: Install/upgrade the packages in the 'deps/<slackwareversion>/multilib' subdirectory instead.

Running Steam on slackware 14.2 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0)
crash_20190107122525_1.dmp[8109]: Uploading dump (out-of-process)
/tmp/dumps/crash_20190107122525_1.dmp
~/.local/share/Steam/steam.sh: line 756:  7986 Segmentation fault      $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
crash_20190107122525_1.dmp[8109]: Finished uploading minidump (out-of-process): success = yes
crash_20190107122525_1.dmp[8109]: response: CrashID=bp-aa83cec3-361b-4e00-b02e-2dd3c2190107
crash_20190107122525_1.dmp[8109]: file ''/tmp/dumps/crash_20190107122525_1.dmp'', upload yes: ''CrashID=bp-aa83cec3-361b-4e00-b02e-2dd3c2190107''
and this is from steam.sh

Code:
###lines 754-757 steam.sh
else
	$STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
fi
STATUS=$?
So if anyone knows how to proceed to troubleshoot this I'd be quite grateful for any suggestions. Otherwise I'm just stopped cold and intend to wait for a month for an updated Current (mine is Dec 2018) and start fresh.
 
Old 01-07-2019, 04:21 PM   #15
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,076

Original Poster
Rep: Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994Reputation: 1994
Well at long last and with.... hmmm not quite blind luck but certainly one-eyed, it's all working, both Steam and Wine. I build a KDEv3 set in /opt to rune one old program I just can't do without, the original KPackage. I like it because it displays all my installed packages in one panel and in the opposite panel there are two tabs, one for what the package does and is for, and the other with a list with complete path to all the files installed as part of that package. I use it several times a week on average. Anyway this helped me solve my segfault problems.

Here's the one-eyed part. I can't be certain what fixed it or if it was just one thing or a combo but I decided to go over all my compat32 installs and simply look for anything that seemed "hinky". I found I had several packages where the compat32 version was newer than the 64bit version, most just a version apart but a few were more than just one off. So I installed all the ones where I found the exact version in 64bit to match the installed compat32. Some were involved in resources that were likely candidates for any sort of gaming software so I upgraded those. Those that seemed unlikely and just one version apart I left as is. I upgraded 16 64bit packages from runlevel 3 just to be safe.

During the KPackage search process I noticed I had two versions of vulkan_sdk and even though I hadn't even one successful launch of Steam to select Beta enrollment, I uninstalled the offender just to be sure.

After dropping to runlevel3 and upgrading the 16 packages, I did the usual and launched KDM from the root login. KDE would not start and dropped me back to the Chooser/Login so I went into Fluxbox and tried dolphin from xterm. It wouldn't run and the error told me libicu4c was at fault and since that was one a more than two versions apart that I had been unsure of but did anyway because it was so far apart, I downgraded back to the original version and KDE started and everything runs fine.

I'm figuring that I must've gotten those conflicting versions from not knowing where to get exact matches for Coimpat32 packages and inadvertently got ones from a newer release of Current so it's all on "the nut behind the wheel". Current, as usual, is remarkably good. Multilib is just a bit of a PITA... presently necessary, but a pita nonetheless.

Thanks to all who tried to help and akimmet, you were right all along. It was just a mess to trace.
 
  


Reply

Tags
current, slackware, steam


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Valve Adds Bluetooth LE Support to Steam Controller in Latest Steam Client Beta LXer Syndicated Linux News 0 05-15-2018 08:31 AM
LXer: Steam Controller Works Again with Older Udev Rules in Latest Steam Client Beta LXer Syndicated Linux News 0 12-09-2016 11:33 PM
Steam crashing with segfault JZL240I-U Linux - Games 5 12-17-2013 02:28 AM
[SOLVED] Xorg segfault after latest upgrade -current yenn Slackware 14 05-14-2012 06:41 PM
Steam on Wine, cannot login,"Steam is having trouble connecting to the Steam servers" cantab Linux - Games 1 06-19-2010 07:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration