On 05.02.2017 03:45, Bryon Adams wrote:

On Sun, 2017-02-05 at 00:07 +0100, Aaron Digulla wrote:

...

On 31.01.2017 01:10, Bryon Adams wrote:

...

Having trouble launching Steam after an update the other day.

I just started steam 1.0.0.54-3.1 on my Leap 42.2 system and it worked fine.

You can look into /tmp/dumps/ and try to check the dumps and logs. Also check your 3D drivers, especially when you use a proprietary one. I'm assuming it's something system specific for me to be honest. Journalctl provides the below error from the kernel. I don't believe I'm using any proprietary drivers, I haven't consciously installed any at any rate. I don't know what I'll need to read the dmp file Steam generates, though if I just use ViM there's a line about something being inaccessible. What would I need to read it?

To identify file types, use file(1). file /tmp/dumps/* says: /tmp/dumps/crash_20160716173943_54.dmp: MDMP crash report data which leads to this page: https://www.chromium.org/developers/decoding-crash-dumps

From journalctl: Feb 04 21:21:48 coffee-to-go.bryonadams.com kernel: steam[19177]: segfault at f52aa193 ip 00000000f62c1ce5 sp 00000000ff8667cc error 7 in libcrypto.so.1.0.0[f627b000+1c3000]

libcrypto seems innocent enough. If it was broken, your web browser probably wouldn't work, either. Next stop: Did you install steam with zypper? That is, are you using the official openSUSE package or something else? steam comes with a bunch of libraries which sometimes to play well with the official ones; the zypper steam package fixes that. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11.02.2017 17:56, Bryon Adams wrote:

On 2/9/2017 15:51, Aaron Digulla wrote:

...

On 05.02.2017 03:45, Bryon Adams wrote:

...

On Sun, 2017-02-05 at 00:07 +0100, Aaron Digulla wrote:

...

On 31.01.2017 01:10, Bryon Adams wrote:

...

Having trouble launching Steam after an update the other day.

I just started steam 1.0.0.54-3.1 on my Leap 42.2 system and it worked fine.

You can look into /tmp/dumps/ and try to check the dumps and logs. Also check your 3D drivers, especially when you use a proprietary one. I'm assuming it's something system specific for me to be honest. Journalctl provides the below error from the kernel. I don't believe I'm using any proprietary drivers, I haven't consciously installed any at any rate. I don't know what I'll need to read the dmp file Steam generates, though if I just use ViM there's a line about something being inaccessible. What would I need to read it?

To identify file types, use file(1). file /tmp/dumps/* says:

/tmp/dumps/crash_20160716173943_54.dmp: MDMP crash report data

which leads to this page: https://www.chromium.org/developers/decoding-crash-dumps

...

From journalctl: Feb 04 21:21:48 coffee-to-go.bryonadams.com kernel: steam[19177]: segfault at f52aa193 ip 00000000f62c1ce5 sp 00000000ff8667cc error 7 in libcrypto.so.1.0.0[f627b000+1c3000]

libcrypto seems innocent enough. If it was broken, your web browser probably wouldn't work, either.

Next stop: Did you install steam with zypper? That is, are you using the official openSUSE package or something else? steam comes with a bunch of libraries which sometimes to play well with the official ones; the zypper steam package fixes that.

Regards,

Aaron, I'll have to spend a bit of time figuring out reading the crash dumps. I agree that libcrypto isn't necessarily at fault here. I did install Steam from packman.

There looks to be some upstream patch in Tumbleweed that may resolve this but I guess Valve has had some trouble with libcrypto. According to someone on this Github issue (https://github.com/ValveSoftware/steam-for-linux/issues/4504) the libcrypto developers changed their public interface and caused some incompatibilty. Workaround that worked for a few people is to do the following:

1. Install nettle-dev:i386, a replacement for libcrypto. 2. Build 32-bit Mesa (from source). Mesa should detect libnettle and Mesa's autogen.sh/configure should print libnettle in the summary at the end. If not, you don't have the development package. To be sure, configure Mesa with "--with-sha1=libnettle".

Although I don't see where I updated libcrypto in what I had in my original post (I'll have to double check this when I get home from work).

I think your version of steam and libcrypto don't match. My version of steam is from openSUSE-Leap-42.2-Update-Non-Oss (http://download.opensuse.org/update/leap/42.2/non-oss/), not packman. Try that one, it should just work. Here are my versions:

rpm -qi steam Name : steam Version : 1.0.0.54 Release : 3.1 Architecture: x86_64 Install Date: Fr 03 Feb 2017 23:52:04 CET Group : Amusements/Games/Other Size : 2761521 License : SUSE-Freeware Signature : RSA/SHA256, Fr 27 Jan 2017 08:05:01 CET, Key ID b88b2fd43dbdc284 Source RPM : steam-1.0.0.54-3.1.src.rpm Build Date : Fr 27 Jan 2017 08:04:52 CET Build Host : lamb21 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.steampowered.com/ Summary : Installer for Valve's digital software distribution service

/lib/libcrypto.so.1.0.0 comes from this package:

rpm -qi libopenssl1_0_0-32bit-1.0.2j-2.2.x86_64 Name : libopenssl1_0_0-32bit Version : 1.0.2j Release : 2.2 Architecture: x86_64 Install Date: So 20 Nov 2016 10:52:44 CET Group : Productivity/Networking/Security Size : 2456756 License : OpenSSL Signature : RSA/SHA256, Di 18 Okt 2016 12:53:43 CEST, Key ID b88b2fd43dbdc284 Source RPM : openssl-1.0.2j-2.2.src.rpm Build Date : Di 18 Okt 2016 12:53:34 CEST Build Host : build79

which is interesting: A 32bit library inside of a 64bit RPM... Shouldn't hurt, though. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 14.02.2017 00:06, Bryon Adams wrote:

On Sun, 2017-02-12 at 23:38 +0100, Aaron Digulla wrote:

...

I think your version of steam and libcrypto don't match. My version of steam is from openSUSE-Leap-42.2-Update-Non-Oss (http://download.opensuse.org/update/leap/42.2/non-oss/), not packman. Try that one, it should just work.

Here are my versions:

...

rpm -qi steam Name : steam Version : 1.0.0.54 Release : 3.1 Architecture: x86_64 Install Date: Fr 03 Feb 2017 23:52:04 CET Group : Amusements/Games/Other Size : 2761521 License : SUSE-Freeware Signature : RSA/SHA256, Fr 27 Jan 2017 08:05:01 CET, Key ID b88b2fd43dbdc284 Source RPM : steam-1.0.0.54-3.1.src.rpm Build Date : Fr 27 Jan 2017 08:04:52 CET Build Host : lamb21 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.steampowered.com/ Summary : Installer for Valve's digital software distribution service

/lib/libcrypto.so.1.0.0 comes from this package:

...

rpm -qi libopenssl1_0_0-32bit-1.0.2j-2.2.x86_64 Name : libopenssl1_0_0-32bit Version : 1.0.2j Release : 2.2 Architecture: x86_64 Install Date: So 20 Nov 2016 10:52:44 CET Group : Productivity/Networking/Security Size : 2456756 License : OpenSSL Signature : RSA/SHA256, Di 18 Okt 2016 12:53:43 CEST, Key ID b88b2fd43dbdc284 Source RPM : openssl-1.0.2j-2.2.src.rpm Build Date : Di 18 Okt 2016 12:53:34 CEST Build Host : build79

which is interesting: A 32bit library inside of a 64bit RPM... Shouldn't hurt, though.

Regards,

-- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/

Sorry for the delay, hectic weekend at work (we started mandating 10 digit dialing at the telco, yay overtime)

Hmm, well I did make an error. Looks like my Steam is actually from the non-OSS repo. I believe mine are the same versions as yours.

Yes, I checked. Next step: Check the files. Run rpm --verify -v on both packages. That should look like this:

rpm --verify -v libopenssl1_0_0-32bit ......... /lib/engines ......... /lib/engines/libgost.so ......... /lib/engines/libpadlock.so ......... /lib/libcrypto.so.1.0.0 ......... /lib/libssl.so.1.0.0

(i.e. only dots in the first column). If you see any letters instead of dots, then a file is damaged. If that looks OK, rename $HOME/.steam to $HOME/.steam.bak and try to start steam again. The SuSE package is just a small wrapper which installs the real steam package from Valve. Steam should check its own files and fix them when they are broken, though. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-02-16 21:13, Bryon Adams wrote:

On February 16, 2017 5:18:30 PM EST, Aaron Digulla wrote:

...

Yes, I checked.

Next step: Check the files. Run rpm --verify -v on both packages. That should look like this:

...

rpm --verify -v libopenssl1_0_0-32bit ......... /lib/engines ......... /lib/engines/libgost.so ......... /lib/engines/libpadlock.so ......... /lib/libcrypto.so.1.0.0 ......... /lib/libssl.so.1.0.0

(i.e. only dots in the first column). If you see any letters instead of dots, then a file is damaged.

If that looks OK, rename $HOME/.steam to $HOME/.steam.bak and try to start steam again. The SuSE package is just a small wrapper which installs the real steam package from Valve. Steam should check its own files and fix them when they are broken, though.

Regards,

I ended up reinstalling openSUSE on my laptop and installed steam first. Ran great until after I started reinstalling some other packages I wanted. Unfortunately I couldn't restore it back trying to use snapper, though I've never used it before and it didn't work that time it looks really cool.

Currently wiping it again so I can leave the laptop vanilla openSUSE with Steam for a bit before installing things one at a time.

I did try wiping the ~/.steam and ~/.local/share/steam directories and running steam --refresh to reload it but still got that segfault.

Well, Steam is running right now. I'll keep an eye on things and follow up with what breaks it if I can figure it out. I created a snapshot using snapper so hopefully if I break it I can just roll back and try again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 19/02/2017 03:16, Bryon Adams wrote:

On Thu, 2017-02-16 at 22:07 -0500, Bryon Adams wrote:

...

On 2017-02-16 21:13, Bryon Adams wrote:

...

On February 16, 2017 5:18:30 PM EST, Aaron Digulla wrote:

...

Yes, I checked.

Next step: Check the files. Run rpm --verify -v on both packages. That should look like this:

...

rpm --verify -v libopenssl1_0_0-32bit ......... /lib/engines ......... /lib/engines/libgost.so ......... /lib/engines/libpadlock.so ......... /lib/libcrypto.so.1.0.0 ......... /lib/libssl.so.1.0.0

(i.e. only dots in the first column). If you see any letters instead of dots, then a file is damaged.

If that looks OK, rename $HOME/.steam to $HOME/.steam.bak and try to start steam again. The SuSE package is just a small wrapper which installs the real steam package from Valve. Steam should check its own files and fix them when they are broken, though.

Regards,

I ended up reinstalling openSUSE on my laptop and installed steam first. Ran great until after I started reinstalling some other packages I wanted. Unfortunately I couldn't restore it back trying to use snapper, though I've never used it before and it didn't work that time it looks really cool.

Currently wiping it again so I can leave the laptop vanilla openSUSE with Steam for a bit before installing things one at a time.

I did try wiping the ~/.steam and ~/.local/share/steam directories and running steam --refresh to reload it but still got that segfault. Well, Steam is running right now. I'll keep an eye on things and follow up with what breaks it if I can figure it out.

I created a snapshot using snapper so hopefully if I break it I can just roll back and try again.

So, I got Steam to fail again but was able to recover it. Tested a bit and it seems to be consistent.

I changed my $PATH variable in .bashrc to:

export PATH="/home/bryon/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/ga mes:/sbin:/usr/sbin"

and it causes Steam to fail after I log out/in. I removed the line and sourced it again to no avail, so I logged out/in and Steam now launches again. For funsies, I added the line back to my .bashrc and it resumed failing.

I wonder if Valve has something in the Steam bash script that launches it that gets messed with if that's my $PATH.

At a glance, is there something bad with my $PATH I'm trying to use? It's the default $PATH from openSUSE, unless I copied it wrong, with /sbin and /usr/sbin added for traceroute/reboot/etc without needing the full path.

Regards, Bryon

Hi Had this problem since last year and solved it by installing steam from this repo by boonbatower http://download.opensuse.org/repositories/home:/boombatower:/steamtricks/ope... Was the only way i could get it to work on opensuse 42.1 and now 42.2 Hope it helps Jide -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 19.02.2017 03:16, Bryon Adams wrote:

On Thu, 2017-02-16 at 22:07 -0500, Bryon Adams wrote:

...

On 2017-02-16 21:13, Bryon Adams wrote:

...

On February 16, 2017 5:18:30 PM EST, Aaron Digulla wrote:

...

Yes, I checked.

Next step: Check the files. Run rpm --verify -v on both packages. That should look like this:

...

rpm --verify -v libopenssl1_0_0-32bit ......... /lib/engines ......... /lib/engines/libgost.so ......... /lib/engines/libpadlock.so ......... /lib/libcrypto.so.1.0.0 ......... /lib/libssl.so.1.0.0

(i.e. only dots in the first column). If you see any letters instead of dots, then a file is damaged.

If that looks OK, rename $HOME/.steam to $HOME/.steam.bak and try to start steam again. The SuSE package is just a small wrapper which installs the real steam package from Valve. Steam should check its own files and fix them when they are broken, though.

Regards,

I ended up reinstalling openSUSE on my laptop and installed steam first. Ran great until after I started reinstalling some other packages I wanted. Unfortunately I couldn't restore it back trying to use snapper, though I've never used it before and it didn't work that time it looks really cool.

Currently wiping it again so I can leave the laptop vanilla openSUSE with Steam for a bit before installing things one at a time.

I did try wiping the ~/.steam and ~/.local/share/steam directories and running steam --refresh to reload it but still got that segfault. Well, Steam is running right now. I'll keep an eye on things and follow up with what breaks it if I can figure it out.

I created a snapshot using snapper so hopefully if I break it I can just roll back and try again.

So, I got Steam to fail again but was able to recover it. Tested a bit and it seems to be consistent.

I changed my $PATH variable in .bashrc to:

export PATH="/home/bryon/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/ga mes:/sbin:/usr/sbin"

/sbin and /usr/sbin are very unusual for user accounts since those folders contain stuff for root. I'd suggest to create links in $HOME/bin for the few tools that you need. Try this command to launch steam: PATH="/usr/bin:/bin:/usr/bin/X11" steam That will pass a special PATH to just this process, nothing else will be affected. You can try to add more folders from your PATH to see when it breaks. To see what the script does, try: PATH="/usr/bin:/bin:/usr/bin/X11" bash -x steam Also check whether the command executes the steam script that you expect: type steam which steam Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org