Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#32 pass environment variables to scripts

open
nobody
None
5
2013-11-28
2013-11-28
Jason Haar
No

I'm playing around with blueproximity on gnome-3.10 and had a great deal of difficulty finding the "magic incantation" to use dbus-send to replace gnome-screensaver-command (as Fedora-19+ doesn't use gnome-screensaver anymore)

Anyway, I think others could benefit from knowing that, so the lock command is included here

dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock

There is also no "unlock" equivalent - I guess for security reasons. However, one thing I'd love to see is some form of command that would at least tell the gnome screenlocker to act like I physically hit the ENTER key as I came back into range - so that I can directly enter my password. However, I cannot figure out how to do that and I'm hoping someone here does?

Finally, I think it would be great for blueproximity to pass other "metadata" into those scripts (via environment variables). The RSSI value, along with how long the screen has been locked since "Locking Command" was called would be great. I appreciate these can be coded into the appropriate script (I have done that myself), but it just seems that blueproximity is tracking those details anyway, so making them available would allow others to mess about more?

Thanks - surely having a bit of fun with this :-)

Jason

Discussion