Comment 27 for bug 240437

Thanks for these new tests! Something seems weird to me: the commands I asked you to run did not print the messages they should when creating an user. Did you Ctrl+C before creating the user? Maybe I was not clear enough: you should run these commands, and reproduce the procedure without stopping them.

The explanation of the problem is somewhat simple here: if the user list is empty, when creating an user, the tool will try to make system users list match the list it knows about, which is empty. Some deletions must go wrong, and this can eventually stop the user from even creating test. I'd like to fundamentally change this behavior for the next version, but for now we may still fix the bug that makes the list empty.

Another information I'd need: does the message
> (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.
appear before you try to create the user? If so, please have a look at /var/log/auth.log
and report if you find errors concerning D-BUS (or attach the file). Thanks!