Bug 447705

Created attachment 144975 [details]
Output of lshw

Created attachment 144976 [details]
Video showing the flickering

Do you have an Intel UHD 620 GPU? If so, this is almost certainly https://gitlab.freedesktop.org/mesa/mesa/-/issues/5731.

(In reply to Nate Graham from comment #3)
> Do you have an Intel UHD 620 GPU? If so, this is almost certainly
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/5731.

No, I have an Asus AMD Radeon R7 240 card.

Beside this, in the linked report I could not see any hint that it is related to suspend/resume like my report. So it seems to me that this is a different issue than mine.

Thanks.

Would you be able to provide some system logs? you should be able to get them with the following command:
journalctl --user-unit plasma-kwin_wayland 

Also you can see if there's errors from the drivers using dmesg.

Created attachment 146557 [details]
Output of journalctl --user-unit plasma-kwin_wayland

Ok, I'm not sure if there's anything suspicious here.

Created attachment 146558 [details]
Output of dmesg

I'm attaching the output of dmesg here too. At first glance I couldn't see errors that seems cleary related to the graphics driver.

I see this on dmesg, it could be related.

[10956.771516] [drm] Fence fallback timer expired on ring sdma0
[10957.315506] [drm] Fence fallback timer expired on ring sdma0
[10957.827495] [drm] Fence fallback timer expired on ring sdma0
[10958.339484] [drm] Fence fallback timer expired on ring sdma0
[10958.851473] [drm] Fence fallback timer expired on ring sdma0
[10959.363464] [drm] Fence fallback timer expired on ring sdma0
[10959.540717] [drm] UVD initialized successfully.
[10959.868009] OOM killer enabled.
[10959.868014] Restarting tasks ...

Exact same problem here on Ryzen 4500U with integrated Renoir Vega 6 GPU. Using Manjaro testing, Plasma 5.23.5.

Similar problem here, but the flickering is just in the background, if i have a window opened it isn't affected. It's sufficient to open a dialog menu or application launcher to make it stop.
Intel core i7 1065g7 and Iris Plus graphics.
Plasma 5.24.2 
KDE Frameworks 5.91
Qt Version 5.15.2

*** Bug 450329 has been marked as a duplicate of this bug. ***

Like I have reported in #450329 (including screen recordings etc.), I see this flickering on Wayland with KWin 5.24.2 and and AMD RX580 graphics card and dual screen (hdmi + dp), in general (with some exceptions) when I unlock my locked session.

It's always only one of the screen which flickers (strobe): Sometimes the whole screen, sometimes parts of it, sometimes it seems to be synchronized with the mouse movement. However, as in the OP described, it goes away, when clicking somewhere.

Same issue on my end (Intel Iris xe graphics on an i7-1185G7)

There are also issues where, when resuming a session, unlocking the desktop, etc. my laptop screen is suddenly activated (even when it is closed) and the wallpaper on my 4k screen shrinks to fill just 1/4 of the screen (like when you snap a window to the upper right of a screen)

I have to reopen my laptop lid, close it again, change my main screen resolution briefly and then set it back to 4k, and then it works fine again (I have to follow these steps every time)

I see the following entries in my logs in regards to the flickering:
3/5/22 8:58 AM	xdg-desktop-portal-kde	xdp-kde-background: GetAppState called: no parameters
3/5/22 8:59 AM	xdg-desktop-portal-kde	xdp-kde-background: GetAppState called: no parameters
3/5/22 8:59 AM	xdg-desktop-portal-kde	xdp-kde-background: GetAppState called: no parameters

*** Bug 451325 has been marked as a duplicate of this bug. ***

I'm experiencing this same issue as well. Seems to be intermittent (at least for me), sometimes resuming from lock results in no flickering, but other times it's exactly as the above comments describe. It flickers with each pixel the mouse moves, creating a strobe effect when moving the mouse a multitude of pixels at a time. The area that flickers is always outside of the currently focused application, and it goes away when clicking anywhere outside of the currently focused window.

This line appears in ~/.local/share/sddm/wayland-session.log after unlocking, I suspect it may be related:
-------------------------------------------------------------------------------------------------------
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool
-------------------------------------------------------------------------------------------------------


I'm using Intel Integrated Graphics, here's the output of 'inxi -G' if it helps:

--------------------------------------------------------------------------------------------------------
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.0
    compositor: kwin_wayland driver: X: loaded: modesetting gpu: i915
    resolution: 1920x1200
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 21.3.7
--------------------------------------------------------------------------------------------------------

Operating System: Arch Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

*** Bug 450780 has been marked as a duplicate of this bug. ***

I have now experienced it several times in Thunderbird 91.7.0 on openSUSE TW: I got a vertical layout with "Folders" and "Message Pane" (three columns in total) and when I go through my received mails, it may happen that the right pane with the message content starts to flicker in this bug's sense. 

Unfortunately, I can only reproduce it by chance.

I can confirm this behaviour, I cannot reliably reproduce it though.

It seems to me that we are never issuing the full repaint we need in the DamageJournal (?).

Submitted this fix, maybe someone can confirm it addresses the issue as well?
https://invent.kde.org/plasma/kwin/-/merge_requests/2188

bug 450780 is not a duplicate, on the corners of my screen where no windows are, the whole screen doesn't flicker, but let's see if the aforementioned fix, fixes my issue as well.

(In reply to Aleix Pol from comment #20)
> Submitted this fix, maybe someone can confirm it addresses the issue as well?
> https://invent.kde.org/plasma/kwin/-/merge_requests/2188

The first patch from this morning seems to make no difference for me (flickering is still there). I can try to make a build with the additional changes tomorrow or so.

*** Bug 452405 has been marked as a duplicate of this bug. ***

(In reply to Aleix Pol from comment #20)
> Submitted this fix, maybe someone can confirm it addresses the issue as well?
> https://invent.kde.org/plasma/kwin/-/merge_requests/2188

Sorry, took a while to test the patch, had to figure out how to build patched Kwin on my test installation of Neon Unstable.

Unfortunately, the patch from the merge request doesn't fix the bug for me - still flickering after resume sometimes.

Maybe it's relevant to mention that I don't have screen locking enabled (no password prompt on resume).

Git commit d3259fe94593ecad247faf9dc1b697512aa88080 by Aleix Pol Gonzalez, on behalf of Aleix Pol.
Committed on 13/04/2022 at 11:17.
Pushed by apol into branch 'master'.

Fix unlocking wayland sessions

We were never issuing a repaint which confused thoroughly the
compositor.

M  +2    -0    src/wayland_server.cpp

https://invent.kde.org/plasma/kwin/commit/d3259fe94593ecad247faf9dc1b697512aa88080

Git commit ee625b2d8acad2ba81693107740a12d8a03863c0 by Aleix Pol.
Committed on 13/04/2022 at 13:34.
Pushed by apol into branch 'Plasma/5.24'.

Fix unlocking wayland sessions

We were never issuing a repaint which confused thoroughly the
compositor.

M  +3    -0    src/wayland_server.cpp

https://invent.kde.org/plasma/kwin/commit/ee625b2d8acad2ba81693107740a12d8a03863c0

I feel a bit confused that the bug is now marked as 'Fixed', after I wrote yesterday in #24 that the changes from the merge request don't fix the bug for me. Am I missing something, or was my comment somehow unclear?

There was an in-between version of the MR that wasn't working well, but it was addressed.

I can easily reproduce the (now former) problem and fix it, so I think there's no doubt that the problem is fixed at least to some extent. If you can still reproduce it on the stable branch as is or master, please open a new ticket with a way for us to reproduce as I cannot reproduce the problem anymore.

(In reply to Aleix Pol from comment #28)
> There was an in-between version of the MR that wasn't working well, but it
> was addressed.

 Ah, thanks for the explanation. I'll see if I can still reproduce it on one of the branches containing the final version of the fix - it may take some time before I can a definitive answer.

*** Bug 453413 has been marked as a duplicate of this bug. ***

*** Bug 453396 has been marked as a duplicate of this bug. ***

I have posted a follow-up report: https://bugs.kde.org/show_bug.cgi?id=454639

*** Bug 451914 has been marked as a duplicate of this bug. ***