Bug 480976 - Desktop Effects Window Open/Close Animation "Scale": Task Switcher creates enormous graphical artefacts on screen when "Window close scale" is set to a high number
Summary: Desktop Effects Window Open/Close Animation "Scale": Task Switcher creates en...
Status: REOPENED
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: 5.93.0
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-07 01:03 UTC by fin-w
Modified: 2024-02-21 06:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Video of the graphical issue (3.24 MB, video/mp4)
2024-02-07 01:40 UTC, fin-w
Details
Browser viewable video, since the H.265 video can't be played... (3.80 MB, video/webm)
2024-02-07 03:59 UTC, fin-w
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fin-w 2024-02-07 01:03:12 UTC
SUMMARY
System Settings→Desktop Effects→Window Open/Close Animation has three options. The "Scale" option allows the user to change the open/close scale in its menu. The scale is 0.8 by default (i.e. opening / closing animation happens within the bounds of the animated object: shrink to 0.8 of original size when closing, expand from 0.8 of target size when opening) and is limited to no more than 9.99. This scale feature affects how the Task Switcher appears / disappears.

When using the Task Switcher when the close scale is set to more than 1.0, graphical artefacts start appearing on the screen once the close animation has finished. The larger the number, the bigger and more obvious the artefacts are. The artefacts seem to be remnants of the animation that are still being drawn to the screen, and they seem to only ever appear in areas of the screen that the Task Switcher did NOT fill when it was open. They can be cleared by running the mouse over them, opening the start menu over them, or going into the desktop overview with Meta+Tab. They seem to flicker / respond to changes drawn to other windows (see them flashing as the timer updates in the attached video, for instance).

STEPS TO REPRODUCE
1. In Desktop Effects, set the Window Open/Close Animation to "Scale"
2. Open the "Scale" options and set "Window close scale" to more than 1.0 (3.0+ will be more obvious)
3. Select Apply and then OK in the "Scale" options.
4. Use the Task Switcher with Alt+Tab.

OBSERVED RESULT
On releasing Alt+Tab, parts of the Task Switcher's close animation continue to be drawn to the screen. They flicker and are not the same each time they appear, but are reproducible.

EXPECTED RESULT
The close animation ends cleanly.

SOFTWARE/OS VERSIONS
KDE Neon Testing
Wayland
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
Laptop GPU: Mesa Intel HD Graphics 3000
Comment 1 fin-w 2024-02-07 01:40:10 UTC
Created attachment 165633 [details]
Video of the graphical issue
Comment 2 fin-w 2024-02-07 03:59:06 UTC
Created attachment 165638 [details]
Browser viewable video, since the H.265 video can't be played...
Comment 3 Doug 2024-02-07 05:47:44 UTC
Can reproduce.  Interestingly, can't screenshot it, as that cleans up the screen of the artifacts.

Operating System: KDE neon Testing Edition
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.1
Kernel Version: 6.5.0-15-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Pro WX 3200 Series
Comment 4 Doug 2024-02-17 02:54:05 UTC

*** This bug has been marked as a duplicate of bug 48118 ***
Comment 5 fin-w 2024-02-17 14:07:05 UTC
Have you incorrectly marked this bug as closed? Seems the bug it's supposedly a duplicate of is entirely unrelated? I'm reopening for now but please do change this if your closing it was intentional :)
Comment 6 Doug 2024-02-21 06:38:55 UTC
(In reply to fin-w from comment #5)
> Have you incorrectly marked this bug as closed? Seems the bug it's
> supposedly a duplicate of is entirely unrelated? I'm reopening for now but
> please do change this if your closing it was intentional :)

Yes, it must have been the wrong bug # I put in, sorry.