Comment 24 for bug 240437

Revision history for this message
Roger Miller (zill) wrote : Re: Users-admin fails with AMD-K6 processor

Xubuntu 9.10 (Karmic Koala) Alpha 5 (02-Sep-2009) Live CD

Starting from GUI:

Menu Users and Groups:
Users Settings box shows no users.
Select "Click to make changes" button, then enter "" (null) password.
Manage Groups box is also blank.

cat /etc/passwd shows expected full list of users (30)
cat /etc/group shows expected full list of groups (58)

Using GUI, add user "test" with UID of 1000 and administrator profile.
Error message: "The configuration could not be saved - an unknown error occurred."
Error message: "System policy prevents modifying the system configuration" and requests a password for root. Try Passwords "" (null), "ubuntu" and "root" but none accepted!
Note that this error identified as from org.freedesktop.systemtoolsbackends.set

No entry appears in Users Settings box.
However, home directory for "test" is created.

cat /etc/passwd now shows only eight users, including the new user "test":
(root, daemon, syslog, messagebus, avahi, haldaemon, ubuntu, test)

cat /etc/group now shows only nine groups:
(root, daemon, audio, nogroup, syslog, messagebus, avahi, haldaemon, ubuntu)

sudo capability now lost.

============================
Starting from terminal:

Result are very similar to starting from the GUI with the addition of this terminal output...

ubuntu@ubuntu:~/Desktop$ users-admin

(users-admin:3423): GLib-GIO-WARNING **: g_simple_async_result_complete() called from
outside main loop!

(users-admin:3423): GLib-GIO-WARNING **: g_simple_async_result_complete() called from
outside main loop!

(users-admin:3423): GLib-GIO-WARNING **: g_simple_async_result_complete() called from
outside main loop!

(users-admin:3423): Liboobs-WARNING **: There was an unknown error communicating with the
backends: Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.

(users-admin:3423): Liboobs-WARNING **: There was an unknown error communicating with the
backends: Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.

(users-admin:3423): Liboobs-WARNING **: There was an unknown error communicating with the
backends: Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
ubuntu@ubuntu:~/Desktop$

============================
Conclusion:

Fault basically unchanged from that first reported.

Should be re-opened.