The following command solved the issue:
usermod -a pi -G netdev
Other useful commands:
whoami
more /etc/group
grep netdev /etc/group
groups pi
Thank you for your help... :)
On Sat, 31 Oct 2020 at 15:26, Christopher Schramm
wrote:
> 31.10.20 13:26 Andrew McCarthy:
> > Error checking for auth
31.10.20 13:26 Andrew McCarthy:
Error checking for authorization org.blueman.network.setup:
GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted
callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for
subjects belonging to other identities
That means that
Results from running command: pkcheck --action-id org.blueman.network.setup
--process $PID
*Without authentication at startup:*
Error checking for authorization org.blueman.network.setup:
GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted
callers (e.g. uid 0 or an action owne
(Please don't forget to send your replies to 973...@bugs.debian.org as
well. Thanks)
30.10.20 16:32 Andrew McCarthy:
The netdev group already has the user pi added to it. pi is the user
account of the gnome session.
You can verify the Polkit-1 setup by running
pkcheck --action-id org.blueman
2020-10-30 09:29, Andrew McCarthy:
I attempted to add my user pi to the netdev group, but the system
reports it already exists...
What exists?
You can check the user's groups with the groups command.
Hi Andrew,
the 2.0.8 security update enabled Polkit-1 authorization. There is a
rules file at /usr/share/polkit-1/rules.d/blueman.rules that allows
access without authentication to users in the sudo and netdev groups.
You should be fine if you add your user to netdev.
Cheers
Package: blueman
Version: 2.0.8-1+deb10u1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* I performaned a system update.
* On start-up the next day I had authenticate blueman twice, once for
Network and the second for RFKi
7 matches
Mail list logo
