Is this the inhibit dialog which appears? RequestReboot() is non-interactive
in the sense that it bypasses the session dialog, but still triggers all the
usual session teardown stuff (asking clients if it is ok to shutdown, to
give them a chance to block etc), so you may still see an inhibit dialog,
and some clients may ask if you want to save work. This is the intended
behavior, but I suppose the DBus API could be expanded to provide a truly
non-interactive option which just stops the session. However, that can
already be achieved by calling Stop() on consolekit.
It might be worth working out which client inhibits though, so that can be
fixed instead.
On Jun 24, 2009 1:05 PM, "Colin Watson" <email address hidden> wrote:
Is this the inhibit dialog which appears? RequestReboot() is non-interactive
in the sense that it bypasses the session dialog, but still triggers all the
usual session teardown stuff (asking clients if it is ok to shutdown, to
give them a chance to block etc), so you may still see an inhibit dialog,
and some clients may ask if you want to save work. This is the intended
behavior, but I suppose the DBus API could be expanded to provide a truly
non-interactive option which just stops the session. However, that can
already be achieved by calling Stop() on consolekit.
It might be worth working out which client inhibits though, so that can be
fixed instead.
On Jun 24, 2009 1:05 PM, "Colin Watson" <email address hidden> wrote:
** Attachment added: "Dependencies.txt" launchpadlibrar ian.net/ 28277290/ Dependencies. txt
http://
-- RequestReboot() causes dialog to appear briefly /bugs.launchpad .net/bugs/ 391559 You rece...
https:/