Bug 395421 - Resizing of windows is bugged in various ways
Summary: Resizing of windows is bugged in various ways
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-15 11:10 UTC by Filip Fila
Modified: 2023-05-11 08:51 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Output of qdbus org.kde.KWin /KWin supportInformation (5.80 KB, text/plain)
2018-06-15 11:10 UTC, Filip Fila
Details
(radeon) Output of qdbus org.kde.KWin /KWin supportInformation (5.45 KB, text/plain)
2018-08-01 12:52 UTC, Filip Fila
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Fila 2018-06-15 11:10:56 UTC
Created attachment 113338 [details]
Output of qdbus org.kde.KWin /KWin supportInformation

Hi,

After upgrading to Plasma 5.13 I  noticed resizing of all windows is very bugged. The problems manifest themselves threefold:

TYPE 1 bug = black elements and tearing; e.g. Desktop Effects window: https://youtu.be/Sy1pBCPUs0g
TYPE 2 bug = black elements and lag, e.g. SDDM theme window: https://youtu.be/7JpDvBk_p3A
TYPE 3 bug = tearing; e.g. Fonts window: https://youtu.be/PBEb1oWzow0 (BTW here you can see a bug in fonts-kcm, look at the 'Adjust all fonts' text)

All windows are affected by some of these variants, not just the ones related to settings. 

Output of qdbus org.kde.KWin /KWin supportInformation is attached. 

You may notice I have Wobbly Windows turned on, but the bugs happen even when it's turned off.
Comment 1 Filip Fila 2018-06-15 11:17:16 UTC
Additional info: everything is fine in Wayland.
Comment 2 Filip Fila 2018-06-16 09:24:15 UTC
Compositing off with Shift + Alt + F12 = still happens

Reinstalled GPU drivers, but that didn't help.

Tried with a new user, but happens there as well.
Comment 3 Filip Fila 2018-06-16 10:03:03 UTC
And I apologize for the consecutive posts, but I just wanted to additionally check if it's in any way related to my installation. I booted up a live USB of KDE Neon Developer Git Unstable from June 13th and I can reproduce this there as well.
Comment 4 Martin Flöser 2018-06-16 11:40:59 UTC
Try another distribution. Kabylake is a rather new chipset and was not released when Ubuntu 16.04 was released. It is highly unlikely that a system can support unreleased hardware in a decent manner.
Comment 5 Krešimir Čohar 2018-06-16 11:58:39 UTC
(In reply to Martin Flöser from comment #4)
> Try another distribution. Kabylake is a rather new chipset and was not
> released when Ubuntu 16.04 was released. It is highly unlikely that a system
> can support unreleased hardware in a decent manner.

I have the same problem on Manjaro Linux with completely different hardware (Intel Xeon X5470, GeForce GT 520 with nouveau through kms) so it's unlikely that it's Ubuntu's fault, especially considering the timeline of the bug. Mine isn't as bad, though, and the only place it's readily seen is systemsettings5.
Comment 6 Filip Fila 2018-06-16 12:00:38 UTC
(In reply to Martin Flöser from comment #4)
> Try another distribution. Kabylake is a rather new chipset and was not
> released when Ubuntu 16.04 was released. It is highly unlikely that a system
> can support unreleased hardware in a decent manner.

Good point. I should apologize for not indicating which OS I use ie. where I experienced the bug first. It's Manjaro, which is more or less as bleeding edge as Arch. 

Anyway, I just tried out a live USB of a Kubuntu 18.10 daily snapshot and I get the same problem. The image, however, still has Plasma 5.12.5 so that's another mistake with the original report, will fix it now.
Comment 7 Filip Fila 2018-08-01 12:51:48 UTC
So we have nouveau and intel computers affected by this, according to what was said in this bug report. Rooty's told me in private that it also happens with nvidia and radeon for him. Both of us are on the bleeding edge so it shouldn't be a driver issue. I'm adding a report for a radeon computer where I just installed Linux because the glitches are really bad here: https://youtu.be/TN6zamyYgVI

You can see more graphics card info in the video, as well as the fact that on this computer turning off compositing does help (unlike on the Intel laptop I originally reported this with).

qdbus output to follow
Comment 8 Filip Fila 2018-08-01 12:52:27 UTC
Created attachment 114254 [details]
(radeon) Output of qdbus org.kde.KWin /KWin supportInformation
Comment 9 Filip Fila 2018-08-01 13:08:29 UTC
Correction: turning off compositing only helps with this new type 4 bug that appears on this computer, the other 3 types are still present even with compositing off.
Comment 10 Filip Fila 2018-08-01 13:49:58 UTC
So I have the first 3 kinds of glitches on yet another computer, but this one uses amdgpu with an HD7790, which is more potent than the Intel HD 620 and Radeon HD 4200 on the other two computers, if that is of any importance. 

Also, I found a workaround that fixes all these types of bugs and on all three of the computers I tested with. If I turn on the "Resize Window" effect in Desktop Effects, the glitches are entirely gone. Unfortunately this effect looks bad so it would be ideal if the underlying issues were fixed.
Comment 11 Filip Fila 2018-08-04 19:13:34 UTC
And here is one more computer affected by this - Kubuntu 18.04.1 Live USB stick on a Radeon HD6570 using the radeon driver. All three types of resizing glitches plus the latest nastiest one: https://i.imgur.com/JZOGCdj.png

Additional info is that at least this worst kind of glitches was not present with Kubuntu 16.04 on this computer. 

To sum it up, all four of the devices I tested with exhibit resizing glitches, with the two older Radeon ones being affected the most, while the amdgpu and intel one do not have the worst kind of glitching. Having the latest drivers or a different distro is of no help (at least for the first 3 types), a clean install neither.  

I think with the number of computers tested and with other variables being controlled for the bug report should warrant a confirmed status, but I don't want to impose it myself. Please let me know if I can help out in any other way with testing and reporting.
Comment 12 Patrick Silva 2018-08-05 23:47:00 UTC
I see the same bugs (except the bug with 'Adjust all fonts' button in the fonts kcm).

Arch Linux
Plasma 5.13.4
Intel HD graphics, modesetting driver
Comment 13 Dušan Dragić 2018-11-04 18:55:15 UTC
I'm also seeing the same kind of resize glitching as in the screenshot in comment #11. This is on:

Fedora 28 64-bit
Plasma 5.13.5
Radeon 6450

I also tried the Fedora 29 KDE Live USB, but it's the same.
Comment 14 Filip Fila 2019-03-07 22:41:24 UTC
After asking around, it would appear that all 3 types of glitches are just due to innate X and QML qualities. 

However the 4th type (most grave one) mentioned later in the report is a regression and definitely shouldn't be happening.
Comment 15 Dušan Dragić 2019-03-09 15:12:52 UTC
After upgrading to Fedora 29 the glitch (the 4th type) was actually less noticeable then before, but still there.

Now I switched to a polaris card and with the amdgpu driver there is no resize glitching.
Comment 16 zvova7890 2019-08-19 13:58:34 UTC
Can you try intel X driver?

Section "Device"
        Identifier "iGPU"
        Driver "intel"
EndSection

I had artefacts when using modesetting driver, on intel is fine.

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)

Artefacts is like lines in konsole or kate, blinking colors in gwenview, but on intel Xorg driver all fine.
Comment 17 zvova7890 2019-08-19 13:59:59 UTC
Oh sorry, i miss that are you on amd GPU )
Comment 18 Filip Fila 2019-08-19 16:27:30 UTC
With Plasma 5.16.4, both running up to date Manjaro stable:

- Radeon HD 6570 - no more nasty resizing glitches (type 4)
- Radeon HD 4200 - nasty resizing glitches are still present
Comment 19 David Edmundson 2023-05-11 08:51:07 UTC
This bug report is not specific enough to be actionable and all comments are now very outdated. Clearly from the last comments graphic drivers made an impact.