Bug 501665

Summary:	Hang when going into fullscreen with jellyfin
Product:	[Plasma] kwin	Reporter:	kostadinshishmanov
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	xaver.hugl
Priority:	NOR
Version First Reported In:	6.3.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	backtrace which may be useful

Description kostadinshishmanov 2025-03-17 23:30:48 UTC

SUMMARY

Whenever I play something with Jellyfin and enter fullscreen, the screen freezes. Pressing keys and audio still work, but the screen is completely frozen. It only happens if I use Wayland and Fractional scaling. It doesn't happen with Gnome or X11.

Using kernel 6.11.4 and Mesa 24.2.8 doesn't help.

```
Mar 18 01:00:43 thinkpad kwin_wayland[4525]: kwin_scene_opengl: 0x1: Shader Stats: SGPRS: 48 VGPRS: 12 Code Size: 1100 LDS: 0 Scratch: 0 Max Waves: 10 Spilled SGPRs: 0 Spilled VGPRs: 0 PrivMem VGPRs: 0 LSOutputs: 0 HSOutputs: 0 HSPatchOuts: 0 ESOutputs: 0 GSOutputs: 0 VSOutputs: 0 PSOutputs: 1 InlineUniforms: 4 DivergentLoop: 0 (PS, W64)
Mar 18 01:00:44 thinkpad kernel: amdgpu 0000:06:00.0: [drm] Mode Validation Warning: Unknown Status failed validation.
Mar 18 01:00:46 thinkpad kwin_wayland[4525]: kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver
Mar 18 01:00:46 thinkpad kwin_wayland[4525]: kwin_wayland_drm: Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues
Mar 18 01:00:46 thinkpad kwin_wayland[4525]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'
Mar 18 01:00:54 thinkpad kernel: amdgpu 0000:06:00.0: [drm] *ERROR* [CRTC:73:crtc-0] flip_done timed out
```

STEPS TO REPRODUCE
1. Use Wayland and fractional scaling
2. Play somethin on jellyfin
3. Enter fullscreen
4. Screen frozen

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 5650U with Radeon Graphics
Memory: 14.4 GiB of RAM
Graphics Processor: AMD Radeon RX Vega 7

Comment 1 kostadinshishmanov 2025-03-17 23:52:08 UTC

Created attachment 179516 [details]
backtrace which may be useful

Comment 2 Zamundaaa 2025-03-18 00:06:07 UTC

The log you pasted says what this is, and what you can do about it (once gitlab.freedesktop.org is up again). There's no bug in KWin here.

Comment 3 Zamundaaa 2025-03-18 00:18:11 UTC

(not meant to be rude, but a genuine question) How did you decide to report it here, rather than reporting it to amdgpu? What can we do to make it more obvious that it shouldn't be reported to KWin?
The three big graphics vendors have a lot of these kinds of issues, so we get a lot of bug reports about it. The existing logging was added to make as many people as possible report it directly to their graphics vendor with at least some useful information, instead of our bug tracker filling up with driver issues.
If you could help make it more effective, that would be very useful. Thanks!

Comment 4 kostadinshishmanov 2025-03-18 00:28:06 UTC

(In reply to Zamundaaa from comment #3)
> (not meant to be rude, but a genuine question) How did you decide to report
> it here, rather than reporting it to amdgpu? What can we do to make it more
> obvious that it shouldn't be reported to KWin?
> The three big graphics vendors have a lot of these kinds of issues, so we
> get a lot of bug reports about it. The existing logging was added to make as
> many people as possible report it directly to their graphics vendor with at
> least some useful information, instead of our bug tracker filling up with
> driver issues.
> If you could help make it more effective, that would be very useful. Thanks!

The messaging is already very clear, I just thought of reporting it here since it happened in a very specific way only with Plasma. And you aren't rude at all. I will report it to amd's bug tracker whenever it's back up (the 22nd i think?). And you aren't being rude, don't worry about it.