On fedora 23 64b, Intel HD3000 (SNB) I used to be able to run Steam on my self built i686 git Mesa driver, but not recently (few months). I tried to build the simplest Mesa with default options, copying those of official Fedora (copied from koji, is there a better way?), then about any mix of FLAGS and arguments. Steam runs on official Fedora Mesa builds but not on self built one anymore. Reinstalling distro drivers does permit to run Steam again. It's not a generic pb with my build config though, as any other i686 GL apps run just fine. What is the best way to compile an equivalent Mesa to the one available in repo? What changed in Fedora that self built drivers (with default options) used to work but not anymore? https://github.com/ValveSoftware/steam-for-linux/issues/4350 https://bugzilla.redhat.com/show_bug.cgi?id=1316505 --------------------------------------- [sheepdestroyer@sheepora ~] $ steam Running Steam on fedora 23 64-bit STEAM_RUNTIME is enabled automatically Installing breakpad exception handler for appid(steam)/version(1457571406) Installing breakpad exception handler for appid(steam)/version(1457571406) Installing breakpad exception handler for appid(steam)/version(1457571406) assert_20160310200202_1.dmp[22400]: Uploading dump (out-of-process) /tmp/dumps/assert_20160310200202_1.dmp /home/sheepdestroyer/.local/share/Steam/steam.sh: line 756: 22394 Segmentation fault (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@" assert_20160310200202_1.dmp[22400]: Finished uploading minidump (out-of-process): success = yes assert_20160310200202_1.dmp[22400]: response: CrashID=bp-9f7860f2-0a2f-4c4a-90e3-0ce112160310 assert_20160310200202_1.dmp[22400]: file ''/tmp/dumps/assert_20160310200202_1.dmp'', upload yes: ''CrashID=bp-9f7860f2-0a2f-4c4a-90e3-0ce112160310'' [sheepdestroyer@sheepora ~] $
I did try with both STEAM_RUNTIME=0 and STEAM_RUNTIME=1, to same results.
Analyze of the crash dump gave libcrypto.so.1.0.2g related error. Someone helpful guessed that "this is from the removal of ssl2 which happened in openssl 1.0.2f -> 1.0.2g" So I rebuilt mesa with --with-sha1=libnettle (instead of libcrypto) and that now works. Who is to blame?
Doesn't sound like us.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.