Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62937 - [lib32-mesa] Segfault on start after upgrading lib32-mesa to 19.1.0-1

Attached to Project: Community Packages
Opened by Martin Roth (Captain_Rage) - Wednesday, 19 June 2019, 08:42 GMT
Last edited by Laurent Carlier (lordheavy) - Wednesday, 19 June 2019, 18:31 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Laurent Carlier (lordheavy)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading lib32-mesa (19.0.6-1 -> 19.1.0-1) Steam segfaults immediately during startup (both using runtime and native; the below is for starting Steam native):

[hello@Computername Sikuli]$ steam-native
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is disabled by the user
Installing breakpad exception handler for appid(steam)/version(0)
crash_20190619103024_1.dmp[6624]: Uploading dump (out-of-process)
/tmp/dumps/crash_20190619103024_1.dmp
crash_20190619103024_1.dmp[6624]: Finished uploading minidump (out-of-process): success = yes
crash_20190619103024_1.dmp[6624]: response: CrashID=bp-b979f3d8-f537-4899-ae5e-067202190619
crash_20190619103024_1.dmp[6624]: file ''/tmp/dumps/crash_20190619103024_1.dmp'', upload yes: ''CrashID=bp-b979f3d8-f537-4899-ae5e-067202190619''
/home/hello/.local/share/Steam/steam.sh: line 906: 6621 Illegal instruction (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"



Additional info:
* downgrading lib32-mesa (19.0.6-1 <- 19.1.0-1) makes Steam start without crashing again
* pertains steam 1.0.0.61-1

Steps to reproduce:
Start Steam with lib32-mesa version 19.1.0-1
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Wednesday, 19 June 2019, 18:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  lib32-mesa-19.1.0-2
Comment by Levente Polyak (anthraxx) - Wednesday, 19 June 2019, 09:08 GMT
to me this sounds like a bug in lib32-mesa instead. Illegal instruction normally means there are instructions to be executed that your CPU doesn't support. maybe libswrAVX2.so is wrongly taken into account for execution on your system?
In either way i dont think this is steam specific, you just use steam to trigger it

can you try running with exporting DEBUGGER=gdb and post some stack-traces and instructions around RIP?
Comment by Martin Roth (Captain_Rage) - Wednesday, 19 June 2019, 09:32 GMT
I see. Thank you very much for your input. The CPU in question is an 'AMD C-70 APU with Radeon HD Graphics'. It's some APU from around 2012.
Running steam-native after having exported DEBUGGER=gdb:

Running Steam on arch rolling 64-bit
STEAM_RUNTIME is disabled by the user
GNU gdb (GDB) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/hello/.local/share/Steam/ubuntu12_32/steam...
(No debugging symbols found in /home/hello/.local/share/Steam/ubuntu12_32/steam)
(gdb)


And after that nothing happens. The terminal stays like that and no Steam window appears. Worth adding, I'm not sure how to debug stuff, but if I understand you correctly this issue might be better suited for reporting in upstream lib32-mesa.
Comment by Levente Polyak (anthraxx) - Wednesday, 19 June 2019, 09:57 GMT
you need to enter 'continue' so it actually does something.
once it crashes you should have all info display, in doubt use 'bt' for the backtrace and 'x/10i $pc' to print current and next instructions and maybe also an 'info sharedlibrary' so we see what libs are loaded as well
Comment by Martin Roth (Captain_Rage) - Wednesday, 19 June 2019, 14:52 GMT
Your patience and guidance is appreciated. Thanks again. Alas, nothing useful seems to be showing up:

/.../
(No debugging symbols found in /home/hello/.local/share/Steam/ubuntu12_32/steam)
(gdb) continue
The program is not being run.
(gdb) bt
No stack.
(gdb) info sharedlibrary
No shared libraries loaded at this time.
(gdb)

Not sure where to take it from here. I might file a bug report for lib32-mesa upstream and use the previous version of the package for the time being.
Comment by kinodont (kinodont) - Wednesday, 19 June 2019, 17:29 GMT
This looks like  FS#58697  - SWR driver was enabled again for lib32-mesa.
I can reproduce this on a CPU without AVX support as described in the above bug report.
Additionally, I can also reproduce on 64-bit Mesa:

$ LIBGL_ALWAYS_SOFTWARE=1 GALLIUM_DRIVER=swr glxinfo
name of display: :0
Illegal instruction (core dumped)

The apparent upstream bug report is here: https://bugs.freedesktop.org/show_bug.cgi?id=108135#c5



Comment by Laurent Carlier (lordheavy) - Wednesday, 19 June 2019, 17:56 GMT
Please test with lib32-mesa-19.1.0-2 (without swr driver - again)
Comment by kinodont (kinodont) - Wednesday, 19 June 2019, 18:08 GMT
No crashes with lib32-mesa-19.1.0-2.

Loading...