Bug 127561

Please provide:
- yast-logs
- /etc/passwd

Thanks.

Created attachment 53646 [details]
yast2 log files

Still working on it ;) .. here it is ...

Created attachment 53647 [details]
/etc/passwd plain text

Contents of the file should be correct by now.

The non-existend 'user1' is also activated in the auto-login feature, therefore
KDM says there is a major error...

Created attachment 53939 [details]
patch for /usr/share/YaST2/include/users/dialogs.ycp

This patch should fix moving the directory.

Could you please apply the patch to your
/usr/share/YaST2/include/users/dialogs.ycp and test renaming user again?

Sure - going to test it in a couple of minutes.

Renaming the user-account works fine now.
But there's still the issue with the kdm auto-login: I renamed the account from
'olduser' to 'newuser' (still being logged in as olduser - therefore programs
like kat, kget, krpmbuilder, firefox and thunderbird went really mad - but hey,
life is hard ;) ) and rebooted. As kdm started up, it mentioned that some sort
of error occured and console 10 showed:

kdm:0:[5778]: getpwnam(olduser) failed

Created attachment 53943 [details]
patch for /usr/share/YaST2/modules/Users.pm

This new patch should fix both problems.

Could you please test the new patch for /usr/share/YaST2/modules/Users.pm? (It
works for me, I just want to see also the confirmation from the bug founder:-))
Thanks.

I've patched the Users.pm file and set the dialogs.ycp to its original state.
Renaming works fine with the new patch, but for some reason the KDM problem
persists - I still get the getpwnam() message :( and the login dialogue also
remembers the old name. 

Hmm, that's strange. Could you attach your /etc/sysconfig/displaymanager file?
And maybe also current yast2 logfiles?

Created attachment 54017 [details]
yast2 log files

Created attachment 54019 [details]
/etc/sysconfig/displaymanger

Here they are. Name of the account 'user' was changed to 'user10' - in
displaymanger all seems to fine - very strange indeed.

But when you reboot, autologin works fine, doesn't it?

Now when I read it better, the main problem is probably that you rename the user
which is logged in - no wonder it behaves strange (maybe I should forbid it at
all in yast2-users). Does everything work correctly if you rename the user (set
for autologin), which is not logged in?

>> But when you reboot, autologin works fine, doesn't it?
No, it doesn't. It doesn't matter whether I reboot or init3-init5 - kdm always
complains.

>> Does everything work correctly if you rename the user (set
for autologin), which is not logged in?
I thought along the same line, but even if I rename as root (with noone else
logged in), the next startup kdm prints it's message.

Hmm, and does it work after you run SuSEconfig?

No, SuSEconfig says it can't alter kdmrc (I'll attach the output, and the kdmrc
files SuSEconfig mentions). As you can see, in the original kdmrc , there is the
old 'user10' instead of the correct 'usernew'.

Created attachment 54070 [details]
Output of SuSEconfig and kdmrc files

Looks like some kdm issue - Stephan?

If you once edited kdmrc manually (or by kcontrol means), SuSEconfig won't 
touch it anymore. Nothing more to say - and SuSEconfig tells you it did not. 
You need to decide on yourself which version you prefer, the changed one or 
the suseconfig generated one 

OK, so I assume yast2-users bug is fixed while the rest stands for user's KDM
configuration.

>> If you once edited kdmrc manually (or by kcontrol means), SuSEconfig won't 
touch it anymore. 

So you mean, you can only use Yast OR kcontrol to manage the accounts, else
you'll encounter this behaviour. If it works that way, I personally thing that
this should be fixed in some way, but, anyway thank you a lot.

fixed in yast2-users-2.13.4 (will be in SL10.1 including some of its next Alpha releases).