Sorry, it was not clear to me whether your report was a duplicate or
not, partly because I didn't have much information about the other
report. So yours is about the fact that new administrator users cannot
authenticate until the computer is rebooted. That may well come from the
same problem as bug 315002, but you're right, we cannot be sure for now.
I've investigated a little more, and I can reproduce the problem. It comes from
a failure to send a D-Bus message to the backends, with error:
Rejected send message, 4 matched rules; type="method_call", sender=":1.212"
(uid=1004 pid=5031 comm=[DIRECTORY])
interface="org.freedesktop.SystemToolsBackends.Platform" member="getPlatform"
error name="(unset)" requested_reply=0
destination="org.freedesktop.SystemToolsBackends" (uid=0 pid=4418
comm="/usr/sbin/system-tools-backends))
So that may well be a problem with D-Bus, or only a problem in PAM that
affects D-Bus. Though I can confirm that other admin tasks using
PolicyKit or sudo are working.
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => Low
--
"Administer the system" for new user requires reboot
https://bugs.launchpad.net/bugs/418337
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
