From: Josselin Poiret <dev@jpoiret.xyz>
To: Paul Jewell <paul@teulu.org>, raingloom <raingloom@riseup.net>
Cc: help-guix@gnu.org, 52904@debbugs.gnu.org
Subject: Re: bug#52904: nmtui - user authorisation
Date: Sun, 02 Jan 2022 12:07:05 +0100 [thread overview]
Message-ID: <875yr2flba.fsf@jpoiret.xyz> (raw)
In-Reply-To: <b1ca579e-9828-1ef9-bc2b-19a67f0c846d@teulu.org>
Hello again,
> Good morning Josselin, and Happy New Year!
>
> Many thanks for taking the time to explain this in detail for us. If I
> have properly understood your explanation, it suggests I am running
> network-manager from outside of the dbus session. If I look at the
> processes running on my system at this moment, the dbus-launch process
> has an id of 881, while the network-manager session has an id of 463,
> suggesting that it was started before dbus. My system configuration is
> relatively standard (if there is such a thing) - I don't do anything to
> change how dbus or network manager are launched, but rely on the
> defaults provided by the the desktop-service. Is there any way to ensure
> network-manager is launched inside the dbus session? I am using slim
> rather than gdm, and as a desktop manager I am using dwm (with some
> local changes).
>
> Regarding the wheel group - my user is in this group, but I don't get
> any request for a password - nmtui simply informs me that I don't have
> the necessary authorisation.
Some context is missing from the forwarded mail, so I have no idea what
script you're trying to run or how, unfortunately. Here is some more
information though:
* there are generally two (or more) dbus daemons running. One for the
system bus, launched through Shepherd (named `dbus-system`), and one for
each session, for the session bus, started either manually or often
through your DM (ie. GDM). elogind and NetworkManager both run on the
system bus.
* for Polkit to successfully reauthenticate you, it needs to have a
registered agent running. A Polkit agent is a program that registers
with Polkit via dbus, is associated with a session, and is used by
Polkit to prompt the user for a password. There are many, see [1]. You
can test whether the agent is properly set-up by simply running `pkexec
echo "Hello"`, pkexec being roughly the equivalent of `sudo`, but using
Polkit for permission checking.
[1] https://wiki.archlinux.org/title/Polkit#Authentication_agents
--
Josselin Poiret
next prev parent reply other threads:[~2022-01-02 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 7:33 nmtui - user authorisation Paul Jewell
2021-12-27 22:07 ` Paul Jewell
2021-12-27 23:20 ` Leo Famulari
2021-12-28 18:39 ` Paul Jewell
2021-12-29 0:50 ` raingloom
2021-12-29 11:04 ` Paul Jewell
2021-12-30 19:00 ` raingloom
2021-12-31 18:41 ` bug#52904: " Josselin Poiret via Bug reports for GNU Guix
2022-01-02 9:32 ` Paul Jewell
2022-01-02 11:07 ` Josselin Poiret [this message]
2022-01-02 20:42 ` Mekeor Melire
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yr2flba.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=52904@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=paul@teulu.org \
--cc=raingloom@riseup.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).