Bug 121881 - [kdm] new user not shown on login screen
Summary: [kdm] new user not shown on login screen
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: unspecified
Hardware: Other All
: P2 - High : Enhancement (vote)
Target Milestone: ---
Assignee: Stephan Kulow
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-09 14:28 UTC by Thorsten Staerk
Modified: 2008-06-25 09:52 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Staerk 2005-10-09 14:28:20 UTC
With my SUSE 9.3, I had the users user1 and user2. Then, I upgraded to SUSE 
10, and there was a figure shown for user1 and user2 on the login screen. I 
liked this. Then, I added user3. Now, only user1 was shown on the login 
screen. Now, all users who logged in since then are shown on the login screen.  
 
This is not as the user expects it, please make it consistent.
Comment 1 Michael Radziej 2005-10-09 16:47:12 UTC
Can you please attach the /var/log/YaST2 directory (as a tar file)?
Comment 2 Jiří Suchomel 2005-10-10 06:38:46 UTC
This is a login manager issue.
Comment 3 Stephan Kulow 2005-10-10 08:16:22 UTC
this is tricky. The login manager tries not to display more than 7 users. For 
this it first lists the existing accounts and if there are more than 7, it 
will switch to the last logged in. 
 
So you will always have a point where it switches to that mode and I can't 
make it "consistent". There is one issue unfixed though: the display manager 
doesn't give feedback that it did. 
 
But what you describe should be another bug: it shouldn't switch with 3 users. 
You sure only had 3 users? 
Comment 4 Thorsten Staerk 2005-10-10 17:18:54 UTC
no, it were "around seven" users when this happened. I should have mentioned. 
Coolo, thanks for your work on KDE... 
Comment 5 Thorsten Staerk 2005-10-10 17:20:42 UTC
trying to change bug status to assigned... tagging field did not work... 
Comment 6 Thorsten Staerk 2005-10-11 21:10:01 UTC
The following scenario occurred: 
I had seven users and someone came and visited me. I told her: Look at my 
Linux login screen, I have some users and I will add you. Then, I added her by 
means of yast2. Then, I logged out and she was not shown on the login screen - 
only the user who had logged in as the last one. 
 
So, this is how it should be: 
- up to seven users, show all users 
- when more than seven users exist, show the users with the most recent 
activation. 
- a user activation can either be a login by the user or his or her creation. 
Comment 7 Stephan Kulow 2005-10-12 05:32:00 UTC
I'm afraid that info does not exist. And it surely does not make sense in a 
NIS/LDAP environment 
Comment 8 Bodo Bauer 2006-04-24 11:54:41 UTC
There has been no activity for more than 3 month. I'm closing this bug as
WONTFIX. If you feel this is inappropriate and the bug should remain open,
or you have new information which may lead to an actual resolution, please
reopen the bug and add the new status.
Comment 9 Stephan Kulow 2006-04-24 12:00:36 UTC
it's a missing feature
Comment 10 Stephan Kulow 2006-09-07 12:49:08 UTC
tracking over fate now
Comment 11 Stephan Kulow 2008-06-25 09:33:47 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 12 Stephan Kulow 2008-06-25 09:35:24 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 13 Stephan Kulow 2008-06-25 09:41:24 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 14 Stephan Kulow 2008-06-25 09:52:55 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(