[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #6 from Johan Sköld --- It does not, the same thing still happens. Even more weirdly, it happens when I fullscreen a transparent window as well, so I don't think direct scanout would be active either way? Although I just realized what's causing it. I remembered my second monitor technically supports VRR, but tends to flicker when it's enabled (only in Linux though, likely a driver bug). Both my monitors had VRR set to "Automatic". If I disable it on the second monitor the flicker stops. Is it possible that KWin enabled VRR on the second monitor too when fullscreening something on my main monitor? Otherwise this may also be some driver bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #4 from Johan Sköld --- Created attachment 166080 --> https://bugs.kde.org/attachment.cgi?id=166080=edit Image shifting on monitor before it turns off. Thanks for the link. I applied that patch to version 5.93.0 of kwin and built it, and while it did get rid of the journalctl spam, my monitor still flickers when I enter or exit fullscreen with some window, and occasionally while just having a window fullscreened. So the original problem is still there. If it helps, just before the monitor turns off the image shifts a bit. When entering fullscreen it shifts down, while when leaving fullscreen it shifts up. Attaching a slow-mo clip of what it looks like when entering fullscreen on my other monitor (just out of view). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #2 from Johan Sköld --- Sorry, one more thing to add that I just noticed. If I open Spectacle and press "Rectangular Region", the monitor flickers off/on every single time I move the mouse cursor. Regardless of which monitor I move it on. And I thought to check `journalctl`. Looking at the last 50 thousand lines, just about every single line says: feb 24 00:13:58 pc kwin_wayland[2937]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glUniformMatrix(matrix size mismatch) The even remotely relevant lines that don't say that are: feb 24 00:09:34 pc kwin_wayland[2937]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x592bbe8e7690) [...] feb 24 00:10:16 pc systemd[2870]: Starting Spectacle screenshot capture utility... [...] feb 24 00:10:16 pc spectacle[6436]: QApplication: invalid style override 'adwaita-dark' passed, ignoring it. Available styles: Breeze, Oxygen, Windows, Fusion [...] feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc systemd[2870]: Started Spectacle screenshot capture utility. [...] feb 24 00:10:16 pc plasmashell[3214]: QQuickItem: Cannot set FocusScope once item has children and is in a window. [...] feb 24 00:11:18 pc plasmashell[3214]: error creating screencast "Could not find window id 0" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #1 from Johan Sköld --- To clarify: It flickers regardless of if a window is fullscreened on my first or second monitor. I wrote most of the original summary before verifying that, and forgot to update parts of it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Johan Sköld changed: What|Removed |Added Summary|Periodic flicker on |Periodic flicker on |secondary monitor with |secondary monitor with |fullscreen window on|fullscreen window on any |primary monitor |monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] New: Periodic flicker on secondary monitor with fullscreen window on primary monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Bug ID: 481750 Summary: Periodic flicker on secondary monitor with fullscreen window on primary monitor Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jo...@skold.cc Target Milestone: --- SUMMARY Using wayland with two monitors: - Dell AW3423DW, 3440x1440 @ 175 Hz, DisplayPort - cocopar 133LR, 1920x1080 @ 60 Hz, HDMI My GPU is an AMD RX 6900 XT, and I'm using the RADV vulkan drivers (v. 24.0.1). The AMDVLK drivers are not installed. Whenever I have a window in fullscreen on the Dell monitor, the cocopar will flicker from time to time. As in it goes black for a second or two before coming back on. Sometimes I can go several minutes without seeing the flicker, other times it happens again within seconds. It seems to happen very frequently when toggling fullscreen on or off, so that's a fast way to repro. If I force atomic modesetting off (`KWIN_DRM_NO_AMS=1`) it's a 100% repro rate whenever toggling fullscreen on or off. STEPS TO REPRODUCE 1. Have two monitors connected and configured to extend the desktop. 2. Toggle fullscreen on or off in some application on one monitor. OBSERVED RESULT The second monitor turns off and on again. EXPECTED RESULT The second monitor does not turn off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.6-zen1-1-zen / 6.0 RC2 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION - The Dell monitor never flickers, it's always the cocopar. - Toggling fullscreen on or off on the cocopar also causes it to flicker. - The same setup worked in an older version of plasma (unsure of what version, but whatever was in arch's repos a few months ago), with `KWIN_DRM_NO_AMS=1`. Unsure about without. - The same setup also works in sway, with or without atomic modesetting. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #35 from Johan Sköld --- It happened again this morning, so I looked at `journalctl` in a tty before unlocking it. Nothing appears to show up when I click "Unlock", but there are a few lines that appear to be potentially relevant earlier in the log. Filtered to skip device connect spam from switching back/forth between ttys: > Jul 18 11:57:58 pc kwin_wayland[2002]: QMetaProperty::read: Unable to handle > unregistered datatype 'KWin::SessionState' for property > 'KWin::EffectsHandlerImpl::sessionState' > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onConfigurationChanged" in Connections > element. This is probably intended to be a signal handler but no signal of > the target matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onRepaintNeeded" in Connections element. > This is probably intended to be a signal handler but no signal of the target > matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool There's also a bit of bismuth spam since I installed that yesterday to give it a try, but I did not have that installed yet when I ran into this yesterday so it seems unrelated and I thus filtered it out above. Operating System: EndeavourOS 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Searching for something automatically selects the second item instead of the first
https://bugs.kde.org/show_bug.cgi?id=454349 Johan Sköld changed: What|Removed |Added CC||jo...@skold.cc --- Comment #8 from Johan Sköld --- I can reproduce this consistently as well in kickoff, but I also seem to have figured out what happens (but not why). 1. Open kickoff and search for something 2. Highlight one of the options with the mouse 3. Press escape to close kickoff 4. Move the cursor away 5. Open kickoff and search for something again (it doesn't have to be the same term) When I do that, it selects the same entry that I hovered with the mouse in step 2. So if I hovered the third entry, it will select the third entry. It sometimes even reproduces without searching for anything once you re-open kickoff, if you had the cursor in a position where it would highlight something in the default view. If I search for something and hover the 6th entry on the left side of the view, once I re-open kickoff it selects "Games" without me doing anything. 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 -- You are receiving this mail because: You are watching all bug changes.