Bug 495482 - Changing brightness using Fn keys changes brightness on the laptop display and the external displays
Summary: Changing brightness using Fn keys changes brightness on the laptop display an...
Status: RESOLVED INTENTIONAL
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 6.2.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-28 13:30 UTC by Filip
Modified: 2024-10-28 13:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
showcase (OSD) (401.65 KB, video/mp4)
2024-10-28 13:30 UTC, Filip
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Filip 2024-10-28 13:30:59 UTC
Created attachment 175307 [details]
showcase (OSD)

SUMMARY
Changing brightness using Fn keys changes brightness on the laptop display and the external displays.

This feature might be intentional and it could be useful, but I think the default (shortcut?) should affect only laptop and maybe shift+Fn would change all displays if this is not a bug and we want to have this?

Note, this doesn't change the brightness set on the monitor/TV. If it is set to 50, it stays at 50 in the monitor settings, just displayed brightness is dimmed down.

I probably missed the component, please fix if needed.

STEPS TO REPRODUCE
1. Connect laptop to an external display
2. Change brightness using the Fn keys -> Brightness changes on the laptop display and on the external display

OBSERVED RESULT
Brightness changes on the laptop display and on the external display

EXPECTED RESULT
Brightness changes only on the laptop display

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2024-10-28 13:56:19 UTC
Indeed, this is intentional. We had similar discussions internally and decided to go with what we ended up shipping.