Bug 102734 - kuser saves passwd file wrongly
Summary: kuser saves passwd file wrongly
Status: RESOLVED DUPLICATE of bug 100443
Alias: None
Product: kuser
Classification: Miscellaneous
Component: general (show other bugs)
Version: 2.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Szombathelyi György
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-29 13:18 UTC by Andrzej
Modified: 2005-03-29 19:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
kuser after applaying changes (82.91 KB, image/png)
2005-03-29 13:19 UTC, Andrzej
Details
passwd after changes (823 bytes, text/plain)
2005-03-29 13:22 UTC, Andrzej
Details
passwd before changes (848 bytes, application/x-trash)
2005-03-29 13:29 UTC, Andrzej
Details
Might as well try this (1.41 KB, patch)
2005-03-29 17:12 UTC, Maksim Orlovich
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrzej 2005-03-29 13:18:22 UTC
Version:           2.0 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.3.4
OS:                Linux (i686) release 2.6.9

When I do any change to an existing user e.g. assign new group to a user, kuser erase information about UID, home catalog, and shall.
There is no way to restore the previous state using kuser (in KDE 3.2.X the was at least save boton).
If some one do not spot that and reboot than he cannot access neither that user account nor the root account.
The only way to fix the problem is to restore passwd form passwd.bak or to edit it manually before booting.

BTW
The way kuser was handling saving in KDE 3.2 was much better (the save botton or a question if someone wants to save changes before leaveing the program)
Comment 1 Andrzej 2005-03-29 13:19:53 UTC
Created attachment 10400 [details]
kuser after applaying changes
Comment 2 Andrzej 2005-03-29 13:22:47 UTC
Created attachment 10401 [details]
passwd after changes
Comment 3 Andrzej 2005-03-29 13:29:15 UTC
Created attachment 10402 [details]
passwd before changes
Comment 4 Maksim Orlovich 2005-03-29 17:12:23 UTC
Created attachment 10409 [details]
Might as well try this 

I tried to fix it, but couldn't reproduce this. But there is a memory bug in
the app --- could to try the attached diff just in case it's the same issue?
Comment 5 Maksim Orlovich 2005-03-29 17:16:48 UTC

*** This bug has been marked as a duplicate of 100443 ***
Comment 6 Andrzej 2005-03-29 19:19:45 UTC
OK. I've applied the diff file and the problem seems to be solved