Arch Linux

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#80318 - [gamescope] segfaults

Attached to Project: Arch Linux
Opened by f (bakgwailo) - Tuesday, 21 November 2023, 20:04 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 November 2023, 06:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Version 3.13.7-1 segfaults whenever I try to launch anything with gamescope including Proton and even just glxgears. Rolling back to 3.12.7-1 and everything works fine again.

Additional info:

Operating System: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.6.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Graphics Processor: AMD Radeon RX 6900 XT

Steps to reproduce:

Install gamescope 3.13.7-1 and attempt to launch any games in it. It then segfaults immediately.


   glxGearsGameScope.txt (4.5 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 23 November 2023, 06:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  gamescope-3.13.8-1
Comment by Toolybird (Toolybird) - Tuesday, 21 November 2023, 20:41 GMT
> It then segfaults immediately

Please provide a backtrace that includes debugging information. Ensure gdb is installed then:

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

More reading at [1][2]

[1] https://blogs.gnome.org/mcatanzaro/2021/09/18/creating-quality-backtraces-for-crash-reports/
[2] https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by f (bakgwailo) - Wednesday, 22 November 2023, 05:11 GMT
Ok, here is what I generated. I do get a warning "warning: Section `.reg-xstate/24340' in core file too small" so not sure how useful it is.
   gdb.txt (0.8 KiB)
Comment by f (bakgwailo) - Wednesday, 22 November 2023, 05:13 GMT
Also attaching the run from steam/proton, pretty much the same (probably useless) trace.
   gdb.txt (0.8 KiB)
Comment by Toolybird (Toolybird) - Wednesday, 22 November 2023, 06:04 GMT
> probably useless

Unfortunately, yes. FWIW, it crashes for me too (Nvidia GPU/drivers). My backtrace (attached) is a little better but still inconclusive. Would be interested to know if it works for anyone.
   gdb.txt (10 KiB)
Comment by Joshua Ashton (JoshuaAshton) - Wednesday, 22 November 2023, 07:41 GMT
Should be fixed with 3.13.8
Comment by f (bakgwailo) - Thursday, 23 November 2023, 05:47 GMT
Yeah, works for me on 3.13.8-1, thank you!

Loading...