Bug 11810

Summary:	Connection impossible in kdm - bad login or password
Product:	Mageia	Reporter:	André DESMOTTES <lebarhon>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	balcaen.john, lmenut, mageia, mageia, philippe.flat
Version:	Cauldron
Target Milestone:	Mageia 4
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description André DESMOTTES 2013-11-28 17:19:27 CET

Description of problem:

Hello,
DELL Latitude D630 with QWERTZ KB layout (Swiss)

Following a crash, I re-install M4B1 with the same USB stick than the first time. No problem during the clean re-install.
After the reboot, in the connection screen (kdm) the system refused the user password. I opened a tty console with ALT+CTRL+F2, same problem, user and root passwords refused. I thought to a keyboard configuration problem because I have a qwertz layout (Swiss).
I re-did a clean install taking great care to the KB choice and passwords. Same behaviour in kdm, but I could connect under root in a tty console, I had a qwerty KB !! I changed it to qwertz with drakconf, I also created a new user with login and password made with only prints that are the same in all KB layouts (login=dfg password=dfg). Back in kdm, I could connect the user dfg but not the original one, even trying with several KB layouts. In the tty console I deleted the users, re-create them (only two) with realistic login and password and now connection is OK. And still OK after another reboot.

Note: The very first M4B1 install with the same USB stick went fine.

Version-Release number of selected component (if applicable):
Mageia 4 Beta1 x86-64 KDE4
DVD ISO dumped on USB stick. MD5sum OK

How reproducible:
I made two installs and had twice this problem. May be connected with the bug 11184.

Steps to Reproduce:
1.Install locale=French and KB layout=qwertz
2.connection impossible in kdm, and qwerty layout in a tty
3.

Reproducible:

Steps to Reproduce:

Manuel Hiebel 2013-11-29 20:15:39 CET

CC: (none) => balcaen.john, lmenut, mageia, nicolas.lecureuil

Comment 1 Philippe Flat 2013-12-22 12:16:00 CET

Same problem with MGA4 B2:
After a fresh install, no problem of login
After update  of mandatory packages (rpm-, perlgtk), no problem
After update of all other packages, no more access to root without rebooting, no access to MCC to correct the problem.
I have done a fresh install, because I had the same problem with Cauldron.
Mga x64, KDE ATI drivers, PhenomII
Locale=French  and KB layout=azerty
No user proposed by kdm at the login (xguest and standard user desappeared)

CC: (none) => philippe.flat
Target Milestone: --- => Mageia 4

Comment 2 Colin Guthrie 2014-01-21 10:54:50 CET

(In reply to Philippe Flat from comment #1)
> Same problem with MGA4 B2:
> After a fresh install, no problem of login
> After update  of mandatory packages (rpm-, perlgtk), no problem
> After update of all other packages, no more access to root without
> rebooting, no access to MCC to correct the problem.
> I have done a fresh install, because I had the same problem with Cauldron.
> Mga x64, KDE ATI drivers, PhenomII
> Locale=French  and KB layout=azerty

So from the description above, I *strongly* suspect this is ultimately the race condition in systemd that creates a /run/nologin file.

This race used to happen when a sysvinit script was enabled via "systemctl enable sysvinitscript[.service]"

This would trigger a daemon-reload from both chkconfig (which systemctl deferred to) and from systemctl itself. Sadly this is racy and causes problems.

The symptoms and reproduction case are all the same so I'd be very surprised if this is not the the same problem.

> No user proposed by kdm at the login (xguest and standard user desappeared)

That bit is however different.

Are you still seeing this problem with the RC?

Comment 3 Philippe Flat 2014-01-21 18:27:50 CET

I have no more this problem, it has disappeared sometime ago , after updates.
For me, the bug can be closed.

Comment 4 Colin Guthrie 2014-01-21 18:41:01 CET

OK, closing then, but as you opened the bug André, please do reopen if you're still affected.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 5 André DESMOTTES 2014-01-21 19:40:20 CET

It's OK for me
Thx