Bug 428028

Summary: OSD: always show on the primary screen
Product: [Plasma] KScreen Reporter: Guo Yunhe <i>
Component: OSD and Plasma appletAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED FIXED    
Severity: wishlist CC: kde, kde, luca_zerb, nate, plasma-bugs-null, postix
Priority: NOR Keywords: usability
Version First Reported In: 5.20.0   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=459560
Latest Commit: Version Fixed/Implemented In: 5.27
Sentry Crash Report:

Description Guo Yunhe 2020-10-20 17:10:58 UTC 
Not a bug or a feature request. Just some thoughts on the OSD behavior on dual screen setup.

So we have sound volume, screen brightness OSD. When you have dual screen setup, the OSD only shows in the desktop that has window focus.

For screen brightness OSD, it usually only works for the laptop screen. When you adjust it, you must be looking at the laptop screen, not the external screen. So showing screen brightness OSD in focused desktop isn't always ideal. If it is too hard to know which screen is laptop screen, duplicate the OSD on every screen is also fine.

Then for the sound valume OSD, it is basically independent to screen. Maybe I have my window focus in a screen. But I am watching YouTube video in the other screen. Maybe the sound is from the laptop speaker or the external speakers behind the external display. Maybe in this case, showing the sound volume OSD in all screen is better.
Comment 1 ahmed m. 2020-11-14 18:14:33 UTC 
I also agree about the focus thing, I guess now it only depends on which display is the primary but having the option to make it whatever display am I actually using right now makes sense.
Comment 2 Ridge 2022-08-29 02:25:51 UTC 
I agree, the OSD being all over the place is a bit confusing. As someone with three screens, I wish I could have an option to make the OSD appear on my primary screen ONLY.
Comment 3 Nate Graham 2022-08-30 17:31:26 UTC 
That would make sense, now that we have a primary screen concept on Wayland.
Comment 4 Nate Graham 2022-11-07 20:49:42 UTC 

*** This bug has been marked as a duplicate of bug 459560 ***
Comment 5 Nate Graham 2023-07-26 20:03:50 UTC 
This is now implemented.

See also Bug 459560, which requests to go back to the old behavior!