This is an academic exercise!
Note, nothing is broke, I have not dug in deep yet to answer this question, and this 'issue' would likely never be visible in typical usage. This installation is clean, though nowhere near virgin. It has lived multiple lives and been many things. It was born in a VM as Jessie and is now Bullseye. EVERYTHING has been changed more than once, derivatives are in service. Everything includes machine-id, all uuid's, disk, partition schemes, etc,etc.
Likely of relevance is that the user's have been rearranged. Going to disk and bare metal usage, I added a new user as 1000, moved the former to 1007. There are other users configured. It all works and was done when I moved this image to bullseye and unique-ified the image almost a year ago. It is current Bullseye now
I was looking at pkecxec's treatment of the mount command. Not really helpful or a step forward if the result is simply substituting 'sudo' for 'pkexec' on the command line. It doesn't look to me pkexec can replace sudo yet, a tangent to this issue, but where I was going.
Code: Select all
~/Desktop$ pkexec mount /dev/disk/by-label/tree ~/Public/tree ==== AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is needed to run `/bin/mount' as the super user Multiple identities can be used for authentication: 1. original,,, (original) 2. hosted user environment,2nd Floor,,,vm (hue) 3. ,,, (altadmin) Choose identity to authenticate as (1-3): ^C
It looks to me pkexec's user list is a snapshot upon install and any tools to add/change users or their uid's never propagates back to polkits user list. Any ideas?