http://bugzilla.opensuse.org/show_bug.cgi?id=988273
http://bugzilla.opensuse.org/show_bug.cgi?id=988273#c1

Egbert Eich <eich@suse.com> changed:

           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 <eich@suse.com> ---
>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#c4 --- Comment #4 from Egbert Eich <eich@suse.com> --- (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 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 Robert Munteanu <robert.munteanu@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.munteanu@gmail.com -- 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 <eich@suse.com> --- (In reply to Ondřej Súkup from comment #5)

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#c8 Andreas Stieger <astieger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger@suse.com Flags|needinfo?(maintenance@opens | |use.org) | --- Comment #8 from Andreas Stieger <astieger@suse.com> --- Not seeing an action for maintenance just now (request review declined by maintainer). Removing needinfo flag. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=988273 Bernhard Breinbauer <infopipe@gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infopipe@gmx.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=988273 Jon Brightwell <jon@moozaad.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jon@moozaad.co.uk -- 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#c19 --- Comment #19 from Matthias Mailänder <matthias@mailaender.name> --- It should definitely be added to the 42.2 Release Notes so people who want to use Steam for gaming know that they can't upgrade yet. -- 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#c21 --- Comment #21 from Jon Brightwell <jon@moozaad.co.uk> --- I'm not 100% sure on how the conflict causes the seg fault with static vs dynamic so excuse any ignorance. openssl 1.1.0 is out now. Has anyone had the chance to check it is still an issue? What specifically changed with libcrypto to break it, I couldn't see anything in the changelog? Why is libnettle such a bad idea? It's already in the official repos and the only use of libnettle in mesa is for SHA1 which is AFAIK only used by shader code. Not exactly security centric and I couldn't find any openssl specific patches on mesa's obs. There's about 4 compiles of mesa with libnettle in obs and I've been using boomba's for several months now without any adverse affects. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=988273 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lnussel@suse.com -- 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#c28 kolA flash <kolAflash@kolAhilft.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kolAflash@kolAhilft.de --- Comment #28 from kolA flash <kolAflash@kolAhilft.de> --- 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 -- 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#c30 Alex Petrini <cyberalex4life@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyberalex4life@gmail.com --- Comment #30 from Alex Petrini <cyberalex4life@gmail.com> --- Take a look at https://bugzilla.opensuse.org/show_bug.cgi?id=1017891, I wasn't able to fix steam for Star Conflict or Strife. This bug is still present in 42.2. Steam works for Valve: Robocraft, Team Fortress and probably others, for War Thunder. This bug is not fixed yet. Please investigate! -- You are receiving this mail because: You are on the CC list for the bug.