Thanks for reporting this.
gamescope has been updated to 3.14.22 in Factory, so should be resolved now.

After updating to KDE 6.1.1 and incidently updating libdisplay-info I realized this bug was not fixed with gamescope 3.14.22.

There is an easy fix proposed by a github user (link bellow), but as long as Valve does not validate the pull request gamescope will remain unusable on any up-to-date Tumbleweed.

Considering that Valve might take lots of time to validate the pull request and draft a new release, maybe it would be better to push a custom version including the fix ?


Link to the actual fix : https://github.com/ValveSoftware/gamescope/pull/1409

Hi.

After looking into this more closely, I realized it was likely never an issue.

The gamescope package in Tumbleweed has always been built with the libdisplay-info provided by gamescope itself as a git submodule in the subprojects dir, not with the system's libdisplay-info.

You can check that for yourself by running `ldd /usr/bin/gamescope` and seeing that it has no dependency on the system's libdisplay-info.

Furthermore, I can't reproduce the bug. It works fine for me on an up to date Tumbleweed system running latest KDE Plasma.

That means whatever your problem is, it's likely unrelated to libdisplay-info entirely.

Can you post more information? Are you running on Plasma X11 or Wayland? Are you using an Nvidia GPU? What exactly happens, does gamescope just crash on startup? No terminal output? Are you sure it's not the app launched by gamescope that's crashing? Maybe try `gamescope glxgears` or `gamescope vkcube` to test.

Hi, my bad then sorry for that, libdisplay-info was my only lead as it's a known issue with gamescope, at least it was updated in the process haha

Here are the requested informations (I should have started by that) :
Operating System: openSUSE Tumbleweed-Slowroll 20240702
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-default (64-bit)
Graphics Platform: X11 (not running off of Wayland because of touchegg)
Processors: 16 × AMD Ryzen 7 7840HS with Radeon 780M Graphics
Memory: 27.1 Gio of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: LENOVO
Product Name: 82Y8
System Version: Yoga Pro 7 14APH8

The symptoms are the following :
KDE taskbar and window decorations start flashing every seconds or so (compositing issue ?). The gamescope's window slightly moving downward on each flash. This eventually ends up with a crash. Terminal outputs seem normal, the only things out of the ordinary are these messages :
wlserver: [xwayland/sockets.c:64] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server

Update : deactivating "Allow applications to block compositing" kind of fixes the issue.

After that, on the first run of gamescope the whole desktop flashes, then comes back to normal and gamescope never block compositing again, even when reactivating "Allow applications to block compositing" (which isn't normal).
A restart is required after reactivating "Allow applications to block compositing" for the issue to come back (I'm unsure if the issue arises with other windows as I'm unaware of other programs that deactivate compositing automatically.

Update 2 : It seems that compositing keeps reactivating even when disabled manually. Which explains the issue with gamescope as it keeps trying to disable compositing but KDE just turns it back on.

So the issue has nothing to do with gamescope, and seems related to KDE itself.
Can you reproduce this issue ? Should I open a new ticket ?

(In reply to Guillaume Pinchon from comment #6)
> Should I open a new ticket ?

Yes please open a new ticket so that it gets assigned to the KDE maintainers.

This issue is in fact not related to gamescope but to KWin compositing on X11 turning itself back on. Opening a new ticket linking to this one.