46075fc92b
Desktops cannot currently tell the difference between a power action being set to challenge permanently (i.e. because the sysadmin wanted to restrict the given user) and a power action being set to challenge because it's temporarily inhibited. Thus, a desktop might take an action that is valid in the first case but not the second case. For instance: GNOME hides all of its automatic suspend settings from the UI whenever a sleep inhibitor is active. This now returns a new state: "inhibited". It communicates to the desktop that the action is available normally, but at the moment the desktop isn't allowed to perform the action due to an inhibitor. Related: https://github.com/systemd/systemd/issues/37311
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