Bug 488834 - Adaptive Panel Effect No Longer Works for Maximised Windows
Summary: Adaptive Panel Effect No Longer Works for Maximised Windows
Status: RESOLVED DUPLICATE of bug 488736
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 6.1.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-20 21:46 UTC by Eamonn Rea
Modified: 2024-06-20 21:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eamonn Rea 2024-06-20 21:46:20 UTC
SUMMARY
The "Adaptive" panel effect no longer works for maximised windows. It works if a window is moved under a panel, but not when it is maximised. This is mot noticeable with bright wallpapers.

I understand this effect will sometimes break, but I have tried many restarts and could not fix it.

If this behaviour is intentional, a new option to adapt panel transparency on window maximise and not just on windows going under panels would be much appreciated.

STEPS TO REPRODUCE
1. Create a panel with the "Adaptive" transparency setting.
2. Maximise a window.
3. The panel's transparency does not change.

OBSERVED RESULT
Panels with "Adaptive" transparency do not update when windows are maximised, only when they are under the panel. 

EXPECTED RESULT
Panels with "Adaptive" transparency should at least have the option to change transparency when a window is maximised.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.5 Linux Zen
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
I have only confirmed this on AMD hardware; one is a laptop with a "AMD Radeon 780M" iGPU and the other is a Desktop with a 7900XTX (both running latest Mesa 24.1 drivers). Unsure if this is perhaps a GPU bug, but it worked fine on both machines on Plasma 6.0.5.
Comment 1 cwo 2024-06-20 21:48:42 UTC
Thank you for the bug report! This issue has already been filed; please follow that bug report for updates on a fix - it's already in the works.

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