*** This bug is a duplicate of bug 59946 *** Though not an exact duplicate, 59946 did give me the answer to the problem - the configuration daemon needed restarting after creating the admin group (which happened when I shut down for the night...) I hadn't realised there was a daemon for these tasks now. I guess it makes more sense than requiring a root password for a clock change (yes, I know the security implications of anyone being able to tweak the clock, but most desktop users can't understand why they shouldn't be able to set the time!)
So, the real bug here is that the upgrade process does not ensure the creation of an admin group. I would also note that the privilege settings in users-admin does not complain about the problem, and indicates falsely that a user can "administer the system" when the admin group does not exist. -- time-admin, menu items as installed in edgy does not gksu, and so fails https://launchpad.net/bugs/63895 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
