Description of problem: GDM do not even enable the login button until something is entered in the password field. Mageia have traditionally always supported empty passwords. Not solving this would cause problems when upgrading -> i set severity = Major
CC: (none) => olav, thierry.vignaud
It works smoothly for me as of gdm-3.22.0-2.mga6 It doesn't ask for password for such a user
Severity: major => normalKeywords: (none) => NEEDINFO
Interesting: Yes, for a user that was created during install with no password, gdm do not even ask - it starts the DE directly when i click the user icon. BUT for a user without password created using MCC, it stubbornly wants a password. - try to create a fresh user using mcc withour pwd, and try log in that user! Interestingly, this is the same problem and difference the Plasma screen locker shows, so maybe same cause? Bug 19318 - Plasma screen locker fail with empty passwords
This works fine for a user created with adduser and manually emptying the password entry in /etc/shadow (which is not supported by all apps)
I just realised GDM have another problem with passwordless users: they can not select DE! To select DE from GDM, user normally clicks his icon, and then appear the password field and login button, and next to login button there is a tiny cogwheel-like button that is used to select DE. But the user that works without password (the user who was created during install) when he clicking his icon a DE is started immediately without chance to choose! I wonder if this bug is in our configuration, GDM imoplementation, or GDM design flaw...? BTW, GDM fail to launch Plasma for any user; i get that message popup about dbus.
(In reply to Morgan Leijström from comment #4) > I just realised GDM have another problem with passwordless users: they can > not select DE! That's as per design and it's not going to change.
OK good to know. Curiously: *how* do user select DE then?
They never were able to
Pour souls ;) Workaround is of course to have every user use password ( Seem a bit unneccesary though on a one user system with encrypted drive or childrens play computer... ) I apply that for now as gdm is visually nice...
CC: (none) => mageia
Neoclust mentions in bug 19318 that a similar issue with the PLasma5 screenlocker seems to be a pam issue. CC'ing a bunch of pam committers Assigning to the Gnome maintainers, anyway, because it is not certain pam is the culprit, but it is certain GDM is affected. Removing "NEEDINFO", because there is no information request. Maybe such a request was intended but forgotten?
Source RPM: gdm-3.22.0-2.mga6.src.rpm => gdm-3.22.0-2.mga6.src.rpm, pam?See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=19318Assignee: bugsquad => gnomeKeywords: NEEDINFO => (none)CC: (none) => anssi.hannula, cjw, luigiwalser, mageia, mageia, marja11, pterjan, tmb
Interestingly, in bug 3368 people complained that people without a password couldn't select a desktop. They could login though. I do not understand pam.
This looks OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED