Bug 505315 - Undesirable increase in window transparency
Summary: Undesirable increase in window transparency
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Show Desktop/Minimize All widgets (other bugs)
Version First Reported In: 6.3.91
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-07 20:56 UTC by Kurt Bärtschi
Modified: 2025-06-08 15:11 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Bärtschi 2025-06-07 20:56:17 UTC
If the transparency for the windows is activated in the system settings, the windows become increasingly transparent when they are minimized several times and then restored using the minimize button (far right in the panel) and finally remain completely frozen on the desktop.

This bug was already reported in Beta1 but not fixed in Beta2

STEPS TO REPRODUCE
1. Go to System-settings / Manage Windows / Desktop Effects /
2. Activate the Transparency Effect
3. Setup in the Settings of the Transparency 80% for inactive Windows 
4. Setup in the Settings of the Transparency 80% for moving Windows
5. Confirm by Clicking the Apply Button
6. Close the Menu by Clicking the OK Button
7. Close the System-settings by Clicking the Apply-Button on the Bottom right
8. Open now some Apps like Dolphin, System-settings, Okular etc...
9. Press now the Minimize-Button in the Panel max right, so all windows disappear in the Panel
10. Restore all Windows again by clicking the same Minimize-Button  in the Panel max right
11. Repeat Step 9, Step 10 Step 9, Step 10, Steip 9

OBSERVED RESULT
Undesirable increase in window transparency

EXPECTED RESULT
Transparency should stay by 80%


SOFTWARE/OS VERSIONS
KDE NEON 6.3.91
Download-Name : neon-testing-20250603-0430

ADDITIONAL INFORMATION
This bug was already reported by me in Beta 1, was fixed by the developer and I was notified about it.

However, I have now noticed that the bug has still not really been fixed. Have I misunderstood or done something wrong?

I am new and I want to support this project as much as I can. It's a great project! Thank you very much !
Comment 1 cwo 2025-06-08 15:11:03 UTC
Thanks for testing!

The bug is fixed (I just tested it), but currently only in master (i.e. what will become 6.5), not in the 6.4 branch. I have added a comment to the MR that the cherry-pick to 6.4 (and possibly 6.3) is still outstanding at this point, but it is planned and marked as such.