Bug 19772

Summary:	LXDM adding second user causes login fail for original user (login loops)
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	Nicolas Salguero <nicolas.salguero>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	6
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	lxdm-0.5.3-4.mga6	CVE:
Status comment:

Description Barry Jackson 2016-11-13 21:17:20 CET

Description of problem:
After adding a second user to a system using LXDM, the original user's login fails.

After appearing to work (no fail message) the process loops back to the login screen.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Barry Jackson 2016-11-13 21:18:33 CET

Source RPM: (none) => lxdm-0.5.3-4.mga6

Marja Van Waes 2016-11-13 21:34:59 CET

CC: (none) => marja11
Assignee: bugsquad => nicolas.salguero

Comment 1 Marja Van Waes 2016-11-13 21:35:43 CET

Please tell how exactly you added the 2nd user

Comment 2 Barry Jackson 2016-11-14 01:40:21 CET

(In reply to Marja van Waes from comment #1)
> Please tell how exactly you added the 2nd user

I used drakuser from drakconf. The system was using LXDM with Plasma.

I will attempt to replicate the issue on a different (my) machine tomorrow (today).

Sorry the report was a bit sparse but I was visiting my brother-in-law and the issue is on his laptop. I wanted to file this while I was there and it was fresh in my mind.

Even after fully removing the second user (me) it was not possible for him to log in using LXDM but he could log in via a tty and startx and then revert back to sddm which then worked OK.

Comment 3 Barry Jackson 2016-11-14 14:04:21 CET

I cannot reproduce this on my x86_64 system here with the same DE and DM, so whether this is an i586 only issue I don't know.

The only difference that springs to mind is that the user (baz) I added had pre-existed on the machine but had been removed (using drakuser) leaving only the /home/baz folder.

The issue arose when I added 'baz' back as a user.

Whether there was some UID/GID mix-up created by this process I cannot now check as the machine is 25 miles away :\

Unless anyone else can confirm this on i586 then I will close as WFM in a week or so.

Comment 4 Nicolas Salguero 2021-01-20 15:48:04 CET

I think the problem concerned only Mageia 6.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Version: Cauldron => 6