| Summary: | black screen when watching video in fulscreen using webcord and vivaldi | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Matej Starc <matej.starc> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.25.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | journalctl log | ||
|
Description
Matej Starc
2022-07-21 21:24:27 UTC
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 *** |