Bug 512064

Summary: Unable to configure opacity of plasma Application Menu submenus with Blur disabled
Product: [Plasma] plasmashell Reporter: Coacher <itumaykin+kde>
Component: Application Menu (Kicker) widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, kdedev
Priority: NOR    
Version First Reported In: 6.5.2   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Popup over dark window
Popup over light window

Description Coacher 2025-11-14 07:59:54 UTC
Created attachment 186764 [details]
Popup over dark window

SUMMARY
Unable to configure opacity of plasma popups

STEPS TO REPRODUCE
1. Open window with a text
2. Make a plasma popup appear on top of it.

OBSERVED RESULT
Plasma popup text is hard to read because of the underlying window content. There is no way to adjust it.

EXPECTED RESULT
The opacity can be turned off or opacity strength can be adjusted.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics
Comment 1 Coacher 2025-11-14 08:00:18 UTC
Created attachment 186765 [details]
Popup over light window
Comment 2 TraceyC 2025-12-01 22:40:10 UTC
Thanks for the bug report. 

Note: The screenshots show submenus of Application Menu

I can't reproduce this on Fedora 43 with the Layan Global Theme with Blur enabled, but I *can* reproduce with Blur *disabled*
I can also reproduce with Plasma built from git-master with blur disabled, using the Breeze Dark global theme with either the Breeze Dark Plasma Style or other Plasma Styles.

That said, it looks like the same problem reported in bug 481595. I'll merge this report in with that one, please follow the other report for updates. Thanks!

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