From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Andy Wingo <wingo@igalia.com>, 22565@debbugs.gnu.org
Subject: bug#22565: Cannot talk to upowerd over D-Bus
Date: Mon, 29 Feb 2016 10:29:03 +0100 [thread overview]
Message-ID: <87lh63kgps.fsf@gnu.org> (raw)
In-Reply-To: <87si0cat0v.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 29 Feb 2016 08:13:20 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> I’m trying to figure out why we cannot use the Xfce menu to shut down or
>>> reboot, and while doing that I found that
>>>
>>> loginctl poweroff
>>>
>>> (as root on the TTY) does have the intended effect. When run as a user
>>> I see a similar error as mentioned above:
>>>
>>> Failed to power off: Interactive authentication required.
>>>
>>> I think this is just fine.
>>
>> I don’t know if it’s fine. :-) I would expect that on GNOME/Xfce a
>> password window would pop up when that RPC is invoked, but I’m not sure
>> how it’s supposed to happen, or under what conditions.
>
> After strace’ing “xfce4-session” when clicking on the shutdown button in
> the Xfce menu I see the same error returned over DBus.
Presumably the underlying problem is the polkit issue (determining which
users are “active” and thus allowed to execute privileged operation)
that Andy has been working on and discussed on IRC and at:
https://lists.gnu.org/archive/html/guix-devel/2016-02/msg01139.html
https://lists.gnu.org/archive/html/guix-devel/2016-02/msg01000.html
https://gnunet.org/bot/log/guix/2016-02-28#T936426
Ludo’.
prev parent reply other threads:[~2016-02-29 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 14:32 bug#22565: Cannot talk to upowerd over D-Bus Ludovic Courtès
2016-02-07 14:49 ` Ludovic Courtès
2016-02-17 22:03 ` Ricardo Wurmus
2016-02-21 22:47 ` Ludovic Courtès
2016-02-29 7:13 ` Ricardo Wurmus
2016-02-29 9:29 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lh63kgps.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22565@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=wingo@igalia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.