[Bug 988273] New: Steam segmentation fault
http://bugzilla.opensuse.org/show_bug.cgi?id=988273 Bug ID: 988273 Summary: Steam segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: quarckster@gmail.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: Steam crashes immediately after starting due this bug https://github.com/ValveSoftware/steam-for-linux/issues/4504 Reproducible: Always Steps to Reproduce: 1. Install steam 1.0.0.52 2. Run it Actual Results: Steam crashes with segmentation fault. Expected Results: Steam works fine. There is fix/workaround for this http://www.gearsongallium.com/?p=3276#utm_source=feedly&utm_medium=rss&utm_campaign=fix-for-segmentation-fault-in-libcrypto-steam-beta mesa must be compiled with libnettle: --with-sha1=libnettle -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Dmitry Misharov
http://bugzilla.opensuse.org/show_bug.cgi?id=988273 http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c1 Egbert Eichchanged: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias@mailaender.name, | |opensuse@dstoecker.de, | |xorg-maintainer-bugs@forge. | |provo.novell.com Assignee|xorg-maintainer-bugs@forge. |vcizek@suse.com |provo.novell.com | --- Comment #1 from Egbert Eich --- >From looking at the discussion on Github, I don't understand why building Mesa with libnettle would help when steam running with the system provided libcryto - ie without the steam provided runtime librypto - doesn't work. This seems to be a libcrypto issue: Before we do any changes in the built of Mesa, the libcrypto & steam maintainers should have a look at this. Reassigning to the maintainer of openssl. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c2
Ondřej Súkup
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c4
--- Comment #4 from Egbert Eich
@Egbert, SR#407423 for TW and SR#407424 for Leap:42.1 is workaround with libnettle + update to 12.0.1 / 11.0.9
comment by Marek Olsak is clear : BTW, this is libcrypto developers' fault, because they had changed their public interface, which is the cause of this incompatibility.
WHich incompatibility? When the run time libs shipped by steam are not used /lib/libcrypto.so.1.0.0 is used by both Mesa and steam. Where do you see an ABI breakage? I would like the maintainer of openssl (where libcryto comes from) to look into this issue before we change anything in Mesa.
and because steam isn't in our control ..
Of course not. But is this a valid reason to do kludge around this by adapting other packages? I've declined the SRs for Mesa for now due to the change of crypto libs for now. I'd like to understand the issue better. I'm fine with the other updates. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Robert Munteanu
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c5
--- Comment #5 from Ondřej Súkup
(In reply to Ondřej Súkup from comment #2)
@Egbert, SR#407423 for TW and SR#407424 for Leap:42.1 is workaround with libnettle + update to 12.0.1 / 11.0.9
comment by Marek Olsak is clear : BTW, this is libcrypto developers' fault, because they had changed their public interface, which is the cause of this incompatibility.
WHich incompatibility? When the run time libs shipped by steam are not used /lib/libcrypto.so.1.0.0 is used by both Mesa and steam. Where do you see an ABI breakage?
i think steam binary uses steamclient.so and steamservice.so with integrated libcrypto into this two libraries ... and here might be incompactibility between steam and Mesa used libs
I would like the maintainer of openssl (where libcryto comes from) to look into this issue before we change anything in Mesa.
and because steam isn't in our control ..
Of course not. But is this a valid reason to do kludge around this by adapting other packages?
I've declined the SRs for Mesa for now due to the change of crypto libs for now. I'd like to understand the issue better. I'm fine with the other updates.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c6
--- Comment #6 from Egbert Eich
i think steam binary uses steamclient.so and steamservice.so with integrated libcrypto into this two libraries ... and here might be incompactibility between steam and Mesa used libs
What do you mean? Statically linked? I very much doubt this. It could well be that we are seeing different versions of the same lib loaded and functions from different versions being called for the same sha1 calculation. What I still don't understand is that this also happens when nut using the steam provided runtime. Unless the openssl maintainer is aware of any issue with a recent version of libcrypto, this needs to be investigated more thoroughly - by the steam package maintainers: presently, I don't have the time for this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c7
Vítězslav Čížek
What do you mean? Statically linked? I very much doubt this. They statically link openssl in ~/.local/share/Steam/ubuntu12_32/steamclient.so (https://github.com/ValveSoftware/steam-for-linux/issues/3803)
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c8
Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Ju_Ping Chan
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Bernhard Breinbauer
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Jon Brightwell
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c17
Pedro Rosado
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c19
--- Comment #19 from Matthias Mailänder
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c20
--- Comment #20 from Matthias Mailänder
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c21
--- Comment #21 from Jon Brightwell
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c22
--- Comment #22 from Marcus Meissner
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
Ludwig Nussel
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c24
Matthias Mailänder
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c28
kolA flash
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c29
--- Comment #29 from Dmitry Misharov
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c30
Alex Petrini
http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c31
--- Comment #31 from kolA flash
For me this seems to be still broken on openSUSE 42.2. Anyone else tested this on 42.2?
So either please: - please reopen this bug until it's fixed for 42.2 OR - bug 996928 isn't a duplicate, because it was specifically for 42.2
Sorry for my previous comment. I didn't installed Steam from the openSUSE-42.2-NonOSS repo, so my Steam didn't used the Steam fixing stuff. https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2:NonFree:Upda... (line 43 - 60) http://download.opensuse.org/distribution/leap/42.2/repo/oss/suse/x86_64/lib... http://download.opensuse.org/distribution/leap/42.2/repo/oss/suse/x86_64/lib... I manually linked those libraries into a non-YaST Steam installation and now that Steam is working fine on 42.2! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com