https://qa.mandrakesoft.com/show_bug.cgi?id=1179
------- Additional Comments From [EMAIL PROTECTED] 2003-02-20 20:40 ------- On Thu, 2003-02-20 at 04:03, kde wrote: Yes but unlisted ones could be accessed. And it didn't suddenly get installed along the way and lock the user out because they are used to being able to not list users and when they logout of their user they suddenly find that they can't login at all. Yes there is... that's why people are complaining. If your statement where accurate these complaints wouldn't exist. But apples works nothing repeat nothing like this. Second most people do use computers for pleasure. More than use it for work. For example in my family (mean parents inlaws sisters and brothers) there are maybe 30 computers. Out of all of those Mine is the ONLY one used for work. The rest are for pleasure. Document this. And offer a choice during update/upgrade I discovered it by accident once I set up and found myself unable to login to by computer when in the process of updating cooker I suddenly couldn't login because I had kdm set to not show users. So I fumble bumble through cooker trying to find out what happened and stumbled across kdebase-kdm and mdkkdm and began to figure out what happened. Yep and so do most corporates. This is a very common situation. See your above statement about this being intended for the non-geek user. To the lay user of computers ... If the button isn't grayed out I can use it. If I click and nothing happens ... it's broken. Again you said that this is intended for the lay user. msec is a bit of work for the expert. (great tool for servers and open access desktops. not as much so for personal use computers / openly access or directly connected to the net but that is another argument.) And since when do you control my computer? I log into every box I build as root. Set it up. etc. I don't have the foggiest idea when I build one of them who the users will be, (people who use these boxes don't want to have james on every one of their boxes.) Where they will be used or why? Just because you are incapable of handling the power of root does not give you, or anyone else the right to tell me / limit me / or prohibit me from logging in as root on a computer that I own, not you. Yes but it was accessible. And a large number of people think you are wrong. Rather than tell us we are wrong or stupid. Please make it an option. We think you are wrong in your design and desire the opportunity to dialog and adjust. Your attitude evokes a feeling of shut-up and use what we give you and this is not good. On a side not. Jeff Raskin (the father of the original Mac UI and one of the foremost experts on UI) considers the two page login a UI mistake. ------- 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: I've openned this as a bug because I think it has real usability and security problems, and because there is an easy solution: The new Mandrake "kdm" that removes the login text field, forces users to login in only if they are listed, and makes loging in a two-stage process is a big usability and security problem. A good solution would probably be: 1) A mdkkdm package (that can be installed by default) that has this new kdm in it (although, I surely hope that it is improved before it's used anywhere!) 2) The original unmodified (but it can be branded, as usual--we have no problem with that) kdm being installed by kdebase, and used if mdkkdm is not installed. Others have made plenty of comments in the cooker ML and can add comments here as appropriate.
