spam and skipping/stuttering in games with "xwm: got the same buffer..." errors

Question

spam and skipping/stuttering in games with "xwm: got the same buffer..." errors

adlainewson opened this issue 2 months ago · comments

Please see videos for the issue:
Majesty 2:
https://github.com/ValveSoftware/gamescope/assets/10458698/9942fd2a-704b-436c-864f-b01ce6b065d8

Zero Protocol (free demo):
https://github.com/ValveSoftware/gamescope/assets/10458698/ef8f1ba4-df60-4079-a6a1-1c19b8b7d8e4

Problem description

Some games appear to skip / stutter at random intervals.
log is spammed with xwm: got the same buffer committed twice, ignoring. as the problem occurs
Problem occurs on both my nvidia eGPU (selected with MESA_VK_DEVICE_SELECT) and igpu (intel)

Debugging info

have tried with flags --rt, --force-composition --synchronous-x11 and various numbers for -r and --framerate-limit to no avail
problem does not occur in embedded mode launched from tty (or without gamescope)
I am X11 + arch + intel/nvidia (550, but problem also occurs in 555) gamescope 3.14.22

Following is an example log from gamescope -h 1440 -H 1440 -- steam then running Zero Protocol and loading into a saved game, where the problem occurs (log cut after at the relevant error spamming log)

console: gamescope version 3.14.22
No CAP_SYS_NICE, falling back to regular-priority compute and threads.
Performance will be affected.
vulkan: selecting physical device 'NVIDIA GeForce RTX 4060': queue family 2 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344241 (VkResult: 0)
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344258 (VkResult: 0)
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
wlserver: Using explicit sync when available
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: Successfully initialized libei for input emulation!
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b730678f0 (res 0x651b73062840)
wlserver: [xwayland/server.c:272] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 114
vblank: Using timerfd.
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
pipewire: renegotiating stream params (size: 2560x1440)
steam.sh[190170]: Running Steam on arch rolling 64-bit
steam.sh[190170]: STEAM_RUNTIME is enabled automatically
setup.sh[190245]: Steam runtime environment up-to-date!
steam.sh[190170]: Steam client's requirements are satisfied
[2024-06-24 21:42:39] Startup - updater built Jun 24 2024 19:20:24
[2024-06-24 21:42:39] Startup - Steam Client launched with: '/home/adlai/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened'
[2024-06-24 21:42:39] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
06/24 21:42:39 minidumps folder is set to /tmp/dumps
06/24 21:42:39 Init: Installing breakpad exception handler for appid(steam)/version(1719259903)/tid(190305)
[2024-06-24 21:42:39] Loading cached metrics from disk (/home/adlai/.local/share/Steam/package/steam_client_metrics.bin)
[2024-06-24 21:42:39] Using the following download hosts for Public, Realm steamglobal
[2024-06-24 21:42:39] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-06-24 21:42:39] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-06-24 21:42:39] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-06-24 21:42:39] Verifying installation...
[2024-06-24 21:42:39] Verification complete
UpdateUI: showing logowlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73035c00 (res 0x651b73068470)
xwm: got the same buffer committed twice, ignoring.
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

Steam logging initialized: directory: /home/adlai/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 1 real: 0xeb1e1dc0
XRRGetCrtcInfo Workaround: initialized with override: 1 real: 0xeb1e0500
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 190397
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
CAppInfoCacheReadFromDiskThread took 178 milliseconds to initialize
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
/usr/share/themes/Materia-light/gtk-2.0/main.rc:756: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Materia-light/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73028180 (res 0x651b730803c0)
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: got the same buffer committed twice, ignoring.
BRefreshApplicationsInLibrary 1: 1ms
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b72fbf9e0 (res 0x651b730875c0)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73021a10 (res 0x651b73087da0)
xwm: waylandres but no win
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
CDesktopCapturePipeWire: Opening DRM render node /dev/dri/renderD128
CDesktopCapturePipeWire: setting stream node path: gamescope
BuildCompleteAppOverviewChange: 1202 apps
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73026d10 (res 0x651b7308a2c0)
RegisterForAppOverview 1: 51ms
RegisterForAppOverview 2: 52ms
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: got the same buffer committed twice, ignoring.
chdir "/home/adlai/.local/share/Steam/steamapps/common/ZERO PROTOCOL Demo"
ERROR: ld.so: object '/home/adlai/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/adlai/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/adlai/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/adlai/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/adlai/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 191021 for gameID 2931820
Adding process 191022 for gameID 2931820
Adding process 191023 for gameID 2931820
Adding process 191113 for gameID 2931820
Adding process 191114 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
fsync: up and running.
Adding process 191115 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191116 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191119 for gameID 2931820
Adding process 191121 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191124 for gameID 2931820
Adding process 191133 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191224 for gameID 2931820
Adding process 191230 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191257 for gameID 2931820
Setting breakpad minidump AppID = 2931820
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198013970966 [API loaded no]
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191292 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191356 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191360 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191416 for gameID 2931820
Adding process 191431 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191434 for gameID 2931820
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73022ab0 (res 0x651b7307d1c0)
xwm: got the same buffer committed twice, ignoring.
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x651b73022e80 (res 0x651b7307be10)
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191577 for gameID 2931820
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191600 for gameID 2931820
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
wlserver: [types/wlr_pointer_constraints_v1.c:278] new confined_pointer 0x651b73026630 (res 0x651b73084620)
wlserver: [types/wlr_pointer_constraints_v1.c:378] constrained 0x651b73026630
wlserver: [types/wlr_pointer_constraints_v1.c:46] destroying constraint 0x651b73026630
wlserver: [types/wlr_pointer_constraints_v1.c:278] new locked_pointer 0x651b73026790 (res 0x651b73084740)
wlserver: [types/wlr_pointer_constraints_v1.c:378] constrained 0x651b73026790
wlserver: [types/wlr_pointer_constraints_v1.c:46] destroying constraint 0x651b73026790
wlserver: [types/wlr_pointer_constraints_v1.c:278] new confined_pointer 0x651b730268f0 (res 0x651b73084860)
wlserver: [types/wlr_pointer_constraints_v1.c:378] constrained 0x651b730268f0
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled NET_WM_STATE property change: _KDE_NET_WM_STATE_SKIP_SWITCHER
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
wlserver: [types/wlr_pointer_constraints_v1.c:46] destroying constraint 0x651b730268f0
wlserver: [types/wlr_pointer_constraints_v1.c:278] new locked_pointer 0x651b73023250 (res 0x651b73084ce0)
wlserver: [types/wlr_pointer_constraints_v1.c:378] constrained 0x651b73023250
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 191790 for gameID 2931820
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.
xwm: got the same buffer committed twice, ignoring.

following is some system info:

 % inxi -G
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: NVIDIA AD107 [GeForce RTX 4060] driver: nvidia v: 550.90.07
  Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB
  Device-4: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
  Display: unspecified server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915,nvidia,nvidia-nvswitch resolution: 1: 3840x2160~60Hz 2: N/A
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.90.07
    renderer: NVIDIA GeForce RTX 4060/PCIe/SSE2
  API: Vulkan v: 1.3.279 drivers: intel,nvidia surfaces: xcb,xlib

% uname -r
6.9.6-arch1-1

sharkautarch · Answer 1 · Tue Jun 25 2024 22:07:21 GMT+0800 (China Standard Time)

Hmmm
w/ nvidia 535 driver, I’ve also seen that message when running glxgears on gamescope …

What happens when you run gamescope -- vkcube?
If that crashes/hangs, what about DISABLE_GAMESCOPE_WSI=1 gamescope -- vkcube?

adlainewson · Answer 2 · Wed Jun 26 2024 10:11:29 GMT+0800 (China Standard Time)

Hmmm w/ nvidia 535 driver, I’ve also seen that message when running glxgears on gamescope …

What happens when you run gamescope -- vkcube? If that crashes/hangs, what about DISABLE_GAMESCOPE_WSI=1 gamescope -- vkcube?

Interesting; running without the flag seems normal, running with DISABLE_GAMESCOPE_WSI=1appears to replicate the stuttering, but without the xwm error messages.

sharkautarch · Answer 3 · Wed Jun 26 2024 20:58:25 GMT+0800 (China Standard Time)

@adlainewson
When running gamescope nested,
I suggest you put
gamescope -h 1440 -H 1440 -- %command%
In the launch options, instead of running steam ontop of gamescope

adlainewson · Answer 4 · Sat Jun 29 2024 02:24:35 GMT+0800 (China Standard Time)

thank you, sometimes running steam in gamescope gets around some errors - in this case there is no difference if gamescope runs steam or steam runs gamescope.