"Could not determine request UID" gave me a hint perhaps failing to get
correct user from proc :-)
This may be a bit more global issue rather than something confined to
Network Manager considering gdm3 also fails to boot with this option on.
(Haven't really dig deep, but perhaps systemd, polkit,
I think I see what's going on.
This seems to happen when hidepid is set to anything other than 0. Remounted
/proc with hidepid=0 and this seems to be fixed. Though, it used to work with
other hidepid option, and is still an issue, but this may be an workaround for
those affected...
--
You
After verifying systemctl status network-manager that it is running, it
seems to be every interaction from the user seems to be failing.
sudo nmcli g
(process:3936): nmcli-CRITICAL **: Error: Could not create NMClient object:
Unable to authenticate request..
sudo nmcli c
(process:3943):
This seems to be happening with generic USB thumbdrives, too. (This
one's unmarked promotional USB thumbdrive, but confirmed this happening
on two of the identical model.)
The below is kern.log of the relevant section.
Aug 21 15:14:24 madoka kernel: [ 936.616305] usb 2-1: USB disconnect, device
It's looking like it is attempting to mount with USB2, but falling back
to USB1...
This is from different distribution, but might be relevant.
https://bbs.archlinux.org/viewtopic.php?id=167705
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
