Bug 487713

Summary: Panel doesn't work occasionally when not present on primary display
Product: [Plasma] plasmashell Reporter: eputty123
Component: PanelAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: kde, lorenzo.darkside, niccolo.venerandi
Priority: NOR    
Version First Reported In: git-stable-Plasma/6.1   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: a video on how the panel responds on different displays

Description eputty123 2024-05-28 21:27:52 UTC
Created attachment 169922 [details]
a video on how the panel responds on different displays

SUMMARY
The entire panel stops visually updating when on a non-primary display with a fullscreen or maximized window on the main display without a panel.
It's possible that this only happens on wayland with nvidia gpus, I haven't tested X11, but it's consistent at least.
STEPS TO REPRODUCE
1. Have 2 displays connected and a panel only on one of them
2. Set the primary display to not have a panel
3.  Maximize a window(firefox is most consistent) on the primary display
4. the panel still accepts input, but doesn't update until the window is no longer maximized or fullscreen.

OBSERVED RESULT
Panel seemingly unresponsive or broken when on non-primary display

EXPECTED RESULT
panel to function properly on all displays regardless of if there is a panel on the primary display

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux TKG kernel 6.9.1 on Arch Linux
(available in About System)
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Nvidia Driver 555.42.02
Comment 1 Marco Martin 2024-05-30 08:12:45 UTC
*** Bug 487783 has been marked as a duplicate of this bug. ***
Comment 2 David Edmundson 2024-05-30 12:25:37 UTC
Nvidia is known to have some wayland issues currently, please confirm if this is still an issue with the newly coming driver
Comment 3 eputty123 2024-05-30 20:05:05 UTC
(In reply to David Edmundson from comment #2)
> please confirm if this is still an issue with the newly coming driver

The issue is resolved with both the latest proprietary driver and the beta proprietary driver, all around working as intended now.