Bug 506504

Created attachment 182878 [details]
xwayland logs

SUMMARY


STEPS TO REPRODUCE
1. Connect PC running RTX 3070 to LG B4 4K OLED TV with HDMI deep color enabled
2.  Launch Steam big picture mode and launch Dying Light with xbox controller via bluetooth
3. Play the game for a few minutes, press the guide button or shift+tab to bring up the steam overlay

OBSERVED RESULT
Kwin notification center shows "Xwayland has crashed" with all my applications running X (steam, discord, etc.) crashing too. It does not boot me back to the log in screen, and I can re-open my apps just fine.

EXPECTED RESULT
For this not to happen.

SOFTWARE/OS VERSIONS
Fastfetch output:
OS: Arch Linux x86_64
Kernel: Linux 6.15.4-arch2-1
Display (LG TV SSCR2): 2560x1440 @ 120 Hz in 72" [External, HDR]
DE: KDE Plasma 6.4.1
WM: KWin (Wayland)
CPU: AMD Ryzen 5 5600X (12) @ 4.65 GHz
GPU: NVIDIA GeForce RTX 3070 [Discrete]
Memory: 4.98 GiB / 62.72 GiB (8%)
Swap: 760.00 KiB / 16.00 GiB (0%)

ADDITIONAL INFORMATION

Note: These crashes do NOT exist on X11 whatsoever, especially with HDMI deep color enabled and my display settings in plasma at 1440p 120hz.


 I connected my 3070 build to my MSI gaming monitor (at 1080p 144hz) through both HDMI and Displayport. Xwayland did not crash at all in the 30 minutes I played Dying Light, and bringing up the Steam big picture overlay every couple of minutes.

On my LG OLED B4 4K TV, I tried disabling HDMI deep color on the HDMI port my 3070 card was plugged into, and brought the resolution down to 1080p, no HDR, 60fps. I would get no signal if I went above 1080p and above 60hz with deep color disabled anyway.

Xwayaland DID crash with the same errors, but only once in the additional 30 minutes I tested while bringing up the big picture overlay every couple minutes.

I flipped HDMI deep color back on and went back to 1440p, HDR enabled, 120fps, and within a couple minutes of playing Dying Light, xwayland crashed.

There is definitely a nasty bug between the wayland compositor and nvidia when displaying greater than 1080p, and this case should be marked as such. Whether it's an issue with Wayland or Nvidia is unknown. I'm going to say a Wayland issue, since X11 has no crashes whatsoever while I'm playing games at 1440p 120hz.

I reported this issue over on gitlab (https://gitlab.freedesktop.org/xorg/xserver/-/issues?show=eyJpaWQiOiIxODI5IiwiZnVsbF9wYXRoIjoieG9yZy94c2VydmVyIiwiaWQiOjEzNDc4MX0%3D) and the first result there had me post some wayland logs by changing the binary and writing a script. I will post those logs here as well.

My journalctl logs also show this: 

journalctl --since "10 minutes ago" | grep -i xwayland
Jun 26 14:36:54 nefarious kwin_wayland_wrapper[2459]: XWAYLAND: error marshalling arguments for lock_pointer (signature noo?ou): null value passed for arg 2
Jun 26 14:36:54 nefarious kwin_wayland_wrapper[2459]: XWAYLAND: Error marshalling request: Invalid argument
Jun 26 14:36:54 nefarious kwin_wayland_wrapper[2459]: (EE) failed to write to Xwayland fd: Invalid argument