| Summary: | Switching primary monitor switches desktop panels | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Dennis Schridde <heri+kde> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | nate, niccolo.venerandi |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | NixOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dennis Schridde
2025-07-27 11:09:37 UTC
Yep, that's how this is expected to work. To be more specific, the primary monitor setting doesn't affect only panels; it affects the entire desktop on the primary monitor, including any panels on it. Basically the primary monitor setting means "which physical monitor would you like your main desktop and its panels to live on?" This is all explained in the little info tooltip next to the primary monitor checkbox. There aren't any plans to change this; Plasma did different things in the past, and it was a huge mess. The current approach was the sustainable and maintainable outcome we settled on. Do you know of a way to feed "primary monitor" information to applications that's different from the desktop's settings? E.g. via environment variables that are read by wayland client libraries? Or would gamescope as an intermediate compositor be my only chance to achieve this? I'm not sure about that, sorry. It seems that there's a deeper UX problem here with primary screen metadata being used somewhat inappropriately. |