Description of problem:
Using the KDE User Manager gui tool as root on a fully updated FC5 as of
2/5/2006. When I added a fresh user, all my other users' home directories were
Version-Release number of selected component (if applicable):
Not sure if this is kdeadmin or not. The window was definitely called 'user
Manager'. I was using it under KDE.
Daren't risk it!
Steps to Reproduce:
1. Log in under KDE as root.
2. Select Users and Groups from menu.
3. Add user called guest with name 'Guest'.
4. Specify userid=503, taking all other defaults.
5. Enter password.
/home/guest not created
/home/daddy etc all deleted (nasty!)
/home/daddy all intact.
Just realised, it's system-config-users that did the damage, nto kdeadmin.
Hm, I'm a bit doubtful about that one. Namely because I just created a user
(with a specified userid of 503) which somehow didn't delete anything, only
created the user's home directory. Afterwards I deleted the user, which removed
the home dir, mail spool and (non-existent) temporary files -- and nothing else.
The "remove stuff" parts will only be executed when deleting a user (just
checked the code) so I really don't know why s-c-users should delete _anything_
when creating a user.
Now one difference is that you did this under KDE while I use GNOME, but
s-c-users should be pretty agnostic of the used desktop environment...
I did it on an x86_64 machine. Was yours x86_64?
The problem is that it's a bit drastic to experiment with on a live machine.
s-c-users is platform independent (it's written in python). Which version of
s-c-users are you using anyway?
Why not leave this bug report lying around for a while.
Then when some-one else confirms it, you will have confirmation.
Even so, there was no way I could have accidentally done an rm -rf /home/*
whilst using system-config-users.
Just going through my open bugs -- it seems nobody else experienced this (I
didn't get other bug reports for this).
I've added the libuser maintainer to Cc.
Mirek, do you have an idea? I mean I'm pretty sure there is nothing in s-c-users
or libuser that could cause this...
Has anyone tried adding a new user with a new user name, but 'accidentally'
setting the UID (i.e. 501 or something) to be that of an existing user?
Maybe I originally did something daft like that?
Even if I did, it is undesirable behaviour :(
I've tried this with current CVS, it catches this kind of error (and has been
doing so for a long time).
I have checked both libuser and s-c-users and I can't find anything either, I'm