If you define a user with no password, GDM detects this and bypasses the password prompt; as soon as you click on the username, you go to the desktop. Unfortunately, the password prompt is the only place you can select a desktop other than the KDE4 default or the last one used. Not sure if this is just bad design or a build option....
Seems this upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=634811
Keywords: (none) => UPSTREAMSee Also: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=634811
No news upstream
CC: (none) => marja11
Keywords: (none) => NO_PATCH
*** Bug 4986 has been marked as a duplicate of this bug. ***
CC: (none) => gruescubogdan
I've just found (by chance) this trick ... If I add a password for the user (for instance, using Mageia Control Centre), then remove the password, GDM no longer bypass the password prompt, I can select the desktop (session), ... all good. I did a <log out> and <log in> between adding and removing the password, though perhaps it's not necessary. Well, almost all is good as there are at least two disadvantages: now I have to click twice from GDM to reach the desktop (when automatic log in is disabled) and mgaapplet asks me for authentication when it launches.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I am almost certain this bug is still valid, but after using the workaround I have no knowledge on how to revert it (and have suspicion the trick/workaround was functioning due to a different bug). Probably someone who performed a clean install should verify this bug.
yes it is, this since it's an upstream bug, we need to have a better mass pinging for the next time
Keywords: NEEDINFO => (none)
(In reply to comment #7) > yes it is, this since it's an upstream bug, we need to have a better mass > pinging for the next time I'm pretty sure we've had upstream bugs that appeared to be fixed when we pinged a bug, while nothing indicated upstream had done anything. Not every upstream is as aware of what is in their bug tracking system as we are, and even with us it happens that a bug get fixed long before someone notices there is an open bug report about the issue. @ Manuel You confirmed the bug is still valid, didn't you?
Whiteboard: (none) => MGA2TOO
*** Bug 7600 has been marked as a duplicate of this bug. ***
CC: (none) => kristoffer.grundstrom1983
CC: (none) => fundawang, mageia, olav
For Olav, Damien and Funda, according to upstream https://bugzilla.gnome.org/show_bug.cgi?id=634811#c10 this should be fixed now But it seems not the case after testing the alpha2 live
(In reply to Manuel Hiebel from comment #10) > For Olav, Damien and Funda, according to upstream > https://bugzilla.gnome.org/show_bug.cgi?id=634811#c10 this should be fixed > now > > But it seems not the case after testing the alpha2 live Ok it's not fixed, according to someone else too, forget the previous comment.
It is still no fixed.
Assignee: bugsquad => olavCC: (none) => thierry.vignaud
Mga5 running in vm. Added new user no password, installed gdm restarted dm. Clicked on user Test shown on login screen. Password field active, clicked on desktop settings, selected another window manager and locked in successfully. No issues. So is the issue that the password field is there when there is no need for it or it is not possible to change window managers? If the first then no fixed but if the second then fixed
CC: (none) => nic
Assignee: olav => gnome
Ping ?
Select the desktop prior to clicking on the user name.
CC: (none) => davidwhodgins