[kde] [Bug 444148] New: Night color settings cannot set night brightness
David
bugzilla_noreply at kde.org
Wed Oct 20 21:36:14 BST 2021
https://bugs.kde.org/show_bug.cgi?id=444148
Bug ID: 444148
Summary: Night color settings cannot set night brightness
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: david.cortes.rivera at gmail.com
Target Milestone: ---
Created attachment 142695
--> https://bugs.kde.org/attachment.cgi?id=142695&action=edit
kde_redshift_settings
SUMMARY
The new night color settings is missing some important functionality that was
present in redshift, namely: controlling brightness and and per-color gamma
(with bright in particular being perhaps more important than the redder color
itself for a better night mode).
See attached screenshort for the old settings. It allowed:
- Setting color temperature for day and night.
- Setting brightness for day and night.
- Setting per-color gamma for day and night.
- Setting transition type.
- Setting switch time, potentially based on geographical coordinates.
The new one allows:
- Setting night color temperature.
- Setting switch time, potentially based on geographical coordinates.
Any changes in brightness or gamma have to be done through a different setting
and are not possible to do for day and night separately, and not from the
widget settings eigher.
STEPS TO REPRODUCE
1. Go to settings -> Display and Monitor -> Night color.
2. Try setting a brightness level for the night.
OBSERVED RESULT
Not possible.
EXPECTED RESULT
Should be possible, like in the older system that this aims at replacing.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.0-3-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD VEGA10
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list