I have worked around my problem by using "adduser" on the cmdline to add my users. I agree that there at least should be some docs explaining policykit and why the unlock button is greyed out.
On Mon, Dec 29, 2008 at 9:21 AM, mc2008 <michaelcook_...@yahoo.com> wrote: > After some consideration I like the 'feature' of authorisations based on > local/remote consoles. I have not changed the defaults as it is more > secure and I dont have a monitor nearby. > > I think it was more frustrating (for a noob) to not know that this was > the problem/root cause for 'unlock' being greyed out. Perhaps a pop-up > on the greyed-out 'unlock' button saying "remote console: not > authorised" would at least give us a clue! I haven't yet run into a > wiki guide yet to adjust authorisations via the cmd-line (which I do > have sudo access) to enable these features... which would be a happy > compromise as I believe 'everything can be done on the cmd-line'... but > not sure how. ;o( Any suggestions Chris? > > -- > policykit not available over Vnc sessions > https://bugs.launchpad.net/bugs/238799 > You received this bug notification because you are a direct subscriber > of the bug. > -- policykit not available over Vnc sessions https://bugs.launchpad.net/bugs/238799 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
