Bug 490913

Summary: Panel settings window in Edit mode prevent access to settings of nearby widgets
Product: [Plasma] plasmashell Reporter: realkpavel
Component: Edit ModeAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: filip.kendes1
Priority: NOR    
Version: 6.1.3   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screenshot showing the System tray widget popup being covered over

Description realkpavel 2024-07-28 07:19:02 UTC
Created attachment 172062 [details]
Screenshot showing the System tray widget popup being covered over

In the new Edit mode, the "Pannel settings" window is drawn over the little popup windows of widgets placed on the panel, preventing access to those popups. This means that the settings and remove buttons for the default placement of the System tray, Digital clock and Peek at desktop widgets are inaccessible.

STEPS TO REPRODUCE
1. Right click the panel on a default Plasma 6.1.3 installation
2. Click "Show Panel Configuration"
3. Hover mouse over the System tray

OBSERVED RESULT
The popup with the name of the widget, it's settings and a remove button is almost completely covered by the Panel settings (see screenshot)

EXPECTED RESULT
The popup is drawn over the panel settings / the panel settings move out of the way / the panel settings close to make way


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.10-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx
Memory: 13.5 GiB of RAM
Graphics Processor: AMD Radeon Vega 10 Graphics
Manufacturer: LENOVO
System Version: ThinkPad T495

ADDITIONAL INFORMATION
Initially discovered on this machine when using fractional scaling.
Also confirmed on an Acer Travelmate P214 running Fedora KDE using 100% scaling.
Comment 1 filip.kendes1 2024-07-28 07:41:16 UTC

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