http://qa.mandrakesoft.com/show_bug.cgi?id=2611


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From [EMAIL PROTECTED]  2003-24-06 19:05 -------
Fixed in latest userdrake-0.92-1mdk (with latest libuser package).
Changes made for a user/group apply instantly. No need to save and no more 
/etc/{ptmp,gtmp} harassments.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date: 
description: 
When userdrake is invoked from mcc, the following
problems exist after a user has been created, but not
saved.

The first problem is that the close action of mcc fails
to invoke a proper close action for userdrake.  This in
turn means two things:  (1) the unsaved work of creating
new users is simply discarded without warning, and (2) the
/etc/ptmp and /etc/gtmp files are not deleted.

Point (2) here leads to further downstream problems, such as that
reported with bug 2444.

The second problem is that there is no prompt or other
clear indication that the work of adding a new user has
not been saved.  The new user appears in the displayed
user list just as if the task of adding the user was complete.
My suggestion here is to highlight added but unsaved users
in some way in the list of users.  

This second problem is a problem with userdrake itself.   It is
not so serious when userdrake is invoked directly, because
userdrake's close action does prompt for the saving of unsaved
work.

I have rated this as major, because this bug would snare
most people who try to add users to their system.  Once the
/etc/ptmp and /etc/gtmp files have been left on the system,
most people would find it impossible to add users to the
system (not knowing that the solution is to su to root and
delete these files).

Reply via email to