Bug 458638 - When using transparency, when moving a window and closing it, the program window does not close
Summary: When using transparency, when moving a window and closing it, the program win...
Status: RESOLVED DUPLICATE of bug 458423
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (other bugs)
Version First Reported In: 5.25.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-02 15:36 UTC by X_Server Linuxoid
Modified: 2022-09-02 18:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Visual description of the bug (988.50 KB, image/png)
2022-09-02 15:36 UTC, X_Server Linuxoid
Details

Note You need to log in before you can comment on or make changes to this bug.
Description X_Server Linuxoid 2022-09-02 15:36:34 UTC
Created attachment 151783 [details]
Visual description of the bug

I'm using the transparency effect when moving windows, which was recently disabled by default in KDE Plasma. I recently noticed that when using it, a bug occurs due to which the program window (any window, be it the main, modal or dialog) does not completely disappear when closed. Instead of completely closing the window, it leaves a transparent plume

STEPS TO REPRODUCE
1. Enable transparency effect in System Settings: Workspace Behavior > Desktop Effects, mark the effect "Translucency"
2. Launch any program so that its window appears
3. Grab the window with the mouse cursor to make the window transparent, then close it with Alt + F4

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97
Qt Version: 5.15.5

ADDITIONAL INFORMATION
With the transparency effect turned off, this bug does not appear. X11 session in use. Fixable only by relogin or rebooting. This bug also works with windows that can close on their own (like progress bars, the Steam login window, etc)
Comment 1 Nate Graham 2022-09-02 18:48:09 UTC

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