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). Then this bugzilla (https://bugzilla.opensuse.org/show_bug.cgi?id=1021095) was brought up by the person who is looking at the issue I raised on Github. where a patch was accepted into factory for Tumbleweed for a similar problem. Depending on how busy I am this weekend, I may just do a fresh install and see where it gets me if I can't figure out how to rebuild nettle and Mesa. Thanks, Bryon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org