Bug 456608

Summary:	Window refresh randomly glitches out
Product:	[Plasma] kwin	Reporter:	nttkde <watisthispoo>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	danielroschka, kde, nate
Priority:	NOR
Version:	5.25.3
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	video some kwin errors in system log

Description nttkde 2022-07-12 01:16:44 UTC

Created attachment 150549 [details]
video

It's possible that this is some amdgpu driver glitch but since it started after the 5.25 updates I think the problem could be in Kwin. (I installed the 5.25.0, .1 and .2 updates all at pretty much same time so can't say which one)

Sometimes a window suddenly glitches and its contents refresh gets really slow (like <1 fps) and glitchy.
So far this has happened to Firefox, Dolphin, Kwrite and Opera IIRC. Closing and restarting the glitched app fixes the problem. It seems to happen like almost once a day to some app so it's quite annoying.

Please see the attached video to see what it looks like.
Note how showing the window thumbnail from the panel behaves. The thumbnail itself shows the window contents perfectly fine and smoothly. There is also the large margin around the thumbnail popup which seems to be updating the underlying window differently.

There are some kwin_x11 XCB errors in system logs around when the bug occurs; I think they may be related. I haven't seen those in that large numbers before.

https://bugs.kde.org/show_bug.cgi?id=456511 could be related but in my case apps never freeze completely.


Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.13.0-52-generic (64-bit)
Graphics Platform: X11
Graphics Processor: Radeon RX Vega 56

Comment 1 nttkde 2022-07-12 01:17:45 UTC

Created attachment 150550 [details]
some kwin errors in system log

Comment 2 nttkde 2022-07-15 10:17:29 UTC

I think this might actually be same as https://bugs.kde.org/show_bug.cgi?id=449301
I tried and window contents refresh normally when I'm dragging it around. So Plasma version 5.25 might be unrelated.

I also saw the glitch happen to the Plasma panel.

The bug also affects kernel 5.15 and Plasma 5.25.3.

One common thing every time a window glitches seems to be those 4 errors in the log:
kwin_core: XCB error: 14 (BadIDChoice)
kwin_core: XCB error: 140 (Unknown)
kwin_core: XCB error: 140 (BadRegion)
kwin_core: XCB error: 140 (BadRegion)

Comment 3 nttkde 2022-07-17 13:13:32 UTC

I booted an older kernel from before I started seeing the bug and the bug still occurred, so at least it's not the kernel alone that causes it.

Comment 4 Daniel Roschka 2022-09-09 06:32:14 UTC

I'm also affected by this bug and I'm also using an AMD GPU. I can confirm that it happens randomly to all kind of apps (for me even regularly to plasmashell) and is quite annoying. Log records in syslog are the same as already reported:

> kwin_core: XCB error: 14 (BadIDChoice), sequence: 10038, resource id: 7658211, major code: 138 (XFIXES), minor code: 5 (CreateRegion)
> kwin_core: XCB error: 140 (Unknown), sequence: 10039, resource id: 7658211, major code: 143 (DAMAGE), minor code: 3 (Subtract)
> kwin_core: XCB error: 140 (BadRegion), sequence: 10040, resource id: 7658211, major code: 138 (XFIXES), minor code: 19 (FetchRegion)
> kwin_core: XCB error: 140 (BadRegion), sequence: 10041, resource id: 7658211, major code: 138 (XFIXES), minor code: 10 (DestroyRegion)

While I'm also uncertain if this bug is related to kwin or amdgpu, I also suspect kwin, as it started right after upgrading to 5.25 for me as well.

Operating System: Debian/sid
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.4
Kernel Version: 5.18.16
Graphics Platform: X11
Graphics Processor: AMD Ryzen 5 PRO 4650G

Comment 5 nttkde 2022-11-27 22:22:44 UTC

Looks like this was fixed by https://bugs.kde.org/show_bug.cgi?id=456511
I have still sometimes seen the errors in log but it no longer causes app windows to glitch out.

*** This bug has been marked as a duplicate of bug 456511 ***