SUMMARY When I try to watch a video in fullscreen using vivaldi or webcord it first shows a black screen, and then it shows the video (it doesn't pause the video, audio still works and everything still works. It also properly accepts keyboard input like a shortcut to open the plasma program launcher or space to pause the video). If I trigger ANY input event (touchpad, mouse, keyboard) like move the mouse or pressing a key it will again trigger the bug and display a black screen for a couple of seconds and then display what you would expect. PS: It does not happen when I try it with firefox. STEPS TO REPRODUCE 1. Open webcord/vivaldi 2. Try playing any video in fullscreen OBSERVED RESULT Trying to display a video in fullscreen causes a 3-second black screen and do so any input events. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: Zenbook UN5401QAB_UN5401QA System Version: 1.0
Please add > QT_LOGGING_RULES="kwin_*.debug=true" to your /etc/environment, reboot, reproduce the problem again and upload the output of > journalctl --boot 0 | grep kwin_wayland_drm
Created attachment 150838 [details] journalctl log
(In reply to Matej Starc from comment #2) > Created attachment 150838 [details] > journalctl log I also encountered this problem when opening an image in NeoChat (with NeoChat'a built-in viewer)
Seems like from KWin's perspective nothing is wrong or out of the ordinary. We can get more information if you execute > echo 0x1FF | sudo tee /sys/module/drm/parameters/debug to enable drm debug logging and then > sudo dmesg -w > drm-debug.log (leave that running), reproduce the bug again, cancel the dmesg command and upload the log it produces. As this also sounds like it might be related to direct scanout, does putting > KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and rebooting resolve the problem?
(In reply to Zamundaaa from comment #4) > Seems like from KWin's perspective nothing is wrong or out of the ordinary. > We can get more information if you execute > > echo 0x1FF | sudo tee /sys/module/drm/parameters/debug > to enable drm debug logging and then > > sudo dmesg -w > drm-debug.log > (leave that running), reproduce the bug again, cancel the dmesg command and > upload the log it produces. > > As this also sounds like it might be related to direct scanout, does putting > > KWIN_DRM_NO_DIRECT_SCANOUT=1 > into /etc/environment and rebooting resolve the problem? Still present.
(In reply to Zamundaaa from comment #4) > Seems like from KWin's perspective nothing is wrong or out of the ordinary. > We can get more information if you execute > > echo 0x1FF | sudo tee /sys/module/drm/parameters/debug > to enable drm debug logging and then > > sudo dmesg -w > drm-debug.log > (leave that running), reproduce the bug again, cancel the dmesg command and > upload the log it produces. > > As this also sounds like it might be related to direct scanout, does putting > > KWIN_DRM_NO_DIRECT_SCANOUT=1 > into /etc/environment and rebooting resolve the problem? I couldn't upload the file here because of file size. https://cloud.aljaxus.eu/index.php/s/MgkqBDfGigryXtC
Alright, afaict from the drm side there's no problems, neither in KWin nor in the kernel. This sounds more and more related to bug 456569.
(In reply to Zamundaaa from comment #7) > Alright, afaict from the drm side there's no problems, neither in KWin nor > in the kernel. > > This sounds more and more related to bug 456569. I experience the black screen when I move the mouse (or trigger any input events). Whereas, his screen goes black when the loading bar goes away.
(In reply to Zamundaaa from comment #7) > Alright, afaict from the drm side there's no problems, neither in KWin nor > in the kernel. > > This sounds more and more related to bug 456569. After testing more, it indeed looks more like the mentioned bug.
*** This bug has been marked as a duplicate of bug 456569 ***