time-admin error: "Could not authenticate"
On 08/04/2008 11:06 PM, Colin Brace wrote:
> Hi all,
> I recently installed 8.04 on a new laptop in a different time zone; now that
> I am home, I need to change the TZ, but time-admin won't "unlock"; after
> about twenty seconds it displays a dialog box saying: "Could not
> It looks like this bug was reported and fixed:
Note that 183804 does not address the unlock issue & instead refers to
183673. And even that bug only touches the surface; there are many
different bugs reported that seem to intertwine on this issue in Hardy.
[gksu dies on first run]
[[hardy] update-manager freezes after clicking on install updates]
[sudo *something which uses poliykit?* doesn't work]
[update manager doesn't work in Hardy]
[ update-manager fails to bring up the password prompt for root privileges]
[gksu doesn't always pop up a dialog]
[ [users-admin] Unlock -> "Could not authenticate. An unexpected error
> In the meantime, are there any workarounds? For some reason running
> time-admin from gksudo doesn't work either.
The first (and easiest) is to check your /etc/hosts file to make sure
that it is set like this:
Or, if you use Samba and have a workgroup share name (workgroup, mshome,
etc) you can use:
127.0.0.1 localhost <machinename>.<workgroupnameifyouhaveone>
For some reason if user-admin cannot find the localhost it craps. And,
given that your's takes about 20 sec to come back with the "Could not
authenticate", there's a good chance that it spent those 20 seconds out
trying to find localhost.
ubuntu-users mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users