https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor en a blog about Debian and self-hosting Mon, 02 Jun 2014 16:09:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401725340-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401725340-1 @noname : But that way, with a command instead of real configuration, is not as satisfying. Also, it is for a single user, and I prefer all my static configuration to be done globally, and it will not apply to a desktop manager but only to the user session. Mon, 02 Jun 2014 16:09:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401724580-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401724580-1 You can turn off monitor with xrandr, I put in ~/.xsession $ xrandr --output VGA1 --off check your projector name with xrandr, mine is VGA1 Mon, 02 Jun 2014 15:56:00 +0000 noname https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401407051-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401407051-1 Thanks for the info on consolekit! I recently ran into an issue with that, and couldn't find out by myself that on can explicitly invoke ck-launch-session to solve it. I certainly agree that this kind of things are painfully underdocumented. Thu, 29 May 2014 23:44:00 +0000 ManuelPG https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401287201-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401287201-1 @hugo : Thanks! It would be more appropriate to allow it only to users members of the powerdev group though, so I would have to add this I guess: polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.upower.suspend" && subject.isInGroup("powerdev")) return polkit.Result.YES; }); Wed, 28 May 2014 14:26:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401286568-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401286568-1 Create /etc/polkit-1/rules.d/suspend.rules with content polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.upower.suspend") return polkit.Result.YES; }); Then every user can suspend the system with the dbus-call you mentioned. The polkit-manpage http://www.freedesktop.org/software/polkit/docs/latest/polkit.8.html contains more information on how to write these rules (e.g. to restrict it to certain users or groups). If you don't want a login manager like ConsoleKit or logind, that's probably the best way to go. Wed, 28 May 2014 14:16:00 +0000 hugo https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401279325-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401279325-1 @hugo : Great, one piece of complex crap replaced by another one. systemd being persona non-grata on systems I manage, I guess I will turn to using sudo, which has the advantage of being understandable (although it has a really lousy man page). Wed, 28 May 2014 12:15:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401278643-1 https://tanguy.ortolo.eu/blog/article128/ck-allow-suspend-xorg-disable-monitor/#c1401278643-1 ConsoleKit is not longer maintained and many people consider it deprecated. It is (or will be) replaced by logind, at least on systems using systemd. Wed, 28 May 2014 12:04:00 +0000 hugo