David Santamaría Rogado
4ed1e2ea17
Actually GNOME sets a clamp of 1% and divides in 20 steps the brightness control. Using 5% clamp makes things like in a device with max value 640 to always be in the first brightness step in GNOME and we can't leave in the minimum. GNOME set steps of 640/20 = 32 with the zero step 640 * 1% = 6. When we restart the device with the lowest bright systemd sees 6 but sets 640 * 5% = 32, so we get the brightness in the first step. Tests in IPS and OLED panels have been done and 1% still seems a comprensive minimun usable value so use that to allow all environments to be able to set lower brightness values that won't be raised by systemd at boot. If your user enviroment allow to set excesive lower unusable values you should blame it or yourself if you directle changes it through sysfs but not systemd.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release