Bug 482560

Summary: Screen brightness widget treat both of my monitors (that are two different brands) as one
Product: [Plasma] Powerdevil Reporter: Kalzi <kalzwayed>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: me, natalie_clarius, nate
Priority: NOR Keywords: qt6
Version: 6.0.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Kalzi 2024-03-06 16:58:31 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I have a dell and sceptre monitors. Both are 27". I used to have a widget called ddcci-plasmoid that helped me change the brightness on the monitors individually. It does not work with plasma 6 for now, so I am now resorting to the built in plasma widget "display brightness" and it treats both monitors as one and the brightness increases on both monitors at the same time when I adjust the slider. Is there a way to make it display two different sliders for each monitor?

STEPS TO REPRODUCE
1. have two different brand monitors
2. adjust the brightness from the display brightness widget
3. observe the outcome.

OBSERVED RESULT
both screens change brightness

EXPECTED RESULT
each screen should change brightness individually

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: A520I AC
System Version: -CF
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-03-07 03:45:11 UTC
There will be in

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