-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify requirements for each method - systemd, dbus-send, dbus-daemon..? (linux) #33
Comments
Starting from the very end: The current implementation calls Inhibit method of the
At specifications.freedesktop.org it says that "org.freedesktop.ScreenSaver — The Idle Inhibition Service manages the inhibition requests". In what packet this service is installed and on what linux distributions it is available? |
Answers Q1) dbus-send, in general case, cannot be used as solution. See #34 (comment) I have seen it used to take locks, though, so probably it depends on the D-Bus service version (flavor and version of Desktop Environment). Skipping dbus-send at least for now. Q2) If there is systemd, there will be dbus available. Source: https://wiki.archlinux.org/title/D-Bus D-Bus seems to be very widely available in linux distributions. Could say that most of the Desktop Environments also provide some D-Bus interface which can be used for either "presentation mode" or "long task mode" purposes. Q3) Not sure when dbus-python would really be needed. The 0.7.0 will depend on jeepney only, but I'm considering adding support for different dbus libraries later on, or then creation a small D-Bus (subset) implementation for just wakepy. Q4) About |
There are multiple possible ways to set a keepawake / inhibitor on linux:
These need clarification
Q1) If a system has dbus-daemon running, does it also can dbus-send executable available? Could dbus-send replace jeepney solution? Or can jeepney be used as dbus solution in a situation where dbus-send executable is not available?
Q2) If a system does have systemd (systemctl command) available, does it automatically mean that dbus is available? Could systemd solution be dropped in favor of a dbus solution? Does the systemctl command use dbus internally?
Q3) In which situations dbus-python would be needed? (Related: #32 )
Edit: Added dbus-python
The text was updated successfully, but these errors were encountered: