It is possible to send D-Bus messages directly with dbus-sen

Consider using dbus-send as method? about wakepy HOT 2 CLOSED

fohrloop commented on July 17, 2024

Consider using dbus-send as method?

from wakepy.

Comments (2)

fohrloop commented on July 17, 2024

I tested it and for some reason I can't get the Inhibit to be permanent:

First, send the same Inhibit command as in wakepy 0.6.0:

niko@niko-ubuntu-home:~$ dbus-send --print-reply --dest=org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver org.freedesktop.ScreenSaver.Inhibit string:'foo' string:'bar'
method return time=1681232979.721795 sender=:1.59 -> destination=:1.2805 serial=209 reply_serial=2
   uint32 1498678652

Then, check the inhibitors (there is nothing):

niko@niko-ubuntu-home:~$ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitors
method return time=1681232980.977727 sender=:1.29 -> destination=:1.2806 serial=806 reply_serial=2
   array [
   ]

If I use wakepy, I'll see (there is one, Inhibitor34):

niko@niko-ubuntu-home:~$ dbus-send --print-reply --dest=org.gnome.SessionManager /org/gnome/SessionManager org.gnome.SessionManager.GetInhibitors
method return time=1681233237.707105 sender=:1.29 -> destination=:1.2812 serial=813 reply_serial=2
   array [
      object path "/org/gnome/SessionManager/Inhibitor34"
   ]

I saw similar behavior (inhibitor lost) when closing the connection in python. So, probably the connection should be kept alive somehow? Not sure it that's possible with dbus-send or other CLI tools.

from wakepy.

fohrloop commented on July 17, 2024

Seems that it is not possible. The power manager(s) release the inhibit lock if the process calling Inhibit dies.

Refs:

from wakepy.

Recommend Projects