Bug 11379

Summary: Unable to login with lightdm
Product: Mageia Reporter: martyn vidler <martynvidler>
Component: RPM PackagesAssignee: Jani Välimaa <jani.valimaa>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins, eeeemail, jani.valimaa, mageia, martynvidler, tremyfr
Version: CauldronKeywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: lightdm CVE:
Status comment:
Attachments: lightdm log
x-0-greeter
.Xauthority
.xsessions-errors
This is from test user .xsession-errors

Description martyn vidler 2013-10-05 00:33:46 CEST
Description of problem:Cant login 


Version-Release number of selected component (if applicable):
lightdm-1.7.17-1.mga4.x86_64

How reproducible:
Tempromental

Steps to Reproduce:
1.Fresh install of MAG4 64 dvd, on Desk Top selection page I unticked KDE and used custom, selected Enlightenment DT. Installed Light DM set that as login manager
2.Tempromental to login, it gose in a loop back to login. Root seems ok to login.
If user logged in on tty2 then switch back to tty1 it seems to login ok
3.LXDM logs in ok.


Reproducible: 

Steps to Reproduce:
martyn vidler 2013-10-05 00:34:26 CEST

CC: (none) => martynvidler

Comment 1 Dave Hodgins 2013-10-05 01:49:48 CEST
I've confirmed the problem.

Switching to tty2, logging in, and use startx --:1,
it worked. Logged out, then went back to tty1, and
it then worked, even after rebooting.

No idea where the problem is, but a successful login
from a console fixes it.

CC: (none) => davidwhodgins

claire robinson 2013-10-05 20:26:27 CEST

CC: (none) => eeeemail, jani.valimaa, mageia, tremyfr

Manuel Hiebel 2013-10-07 12:45:06 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => jani.valimaa
Source RPM: Light DM => lightdm

Manuel Hiebel 2013-10-07 12:46:26 CEST

Summary: Unable to login => Unable to login with lightdm

Comment 2 Jani Välimaa 2013-10-07 16:05:10 CEST
Please, test if new lightdm fixes this issue.
Comment 3 martyn vidler 2013-10-07 20:24:37 CEST
Hi jani

I have updated from version 1.7.17.1 to 1.7.18.1 mga4 I still get the problem.
Comment 4 Jani Välimaa 2013-10-07 20:27:19 CEST
Did you reboot or restarted X after update? Try also removing ~/.Xauthority.
Comment 5 martyn vidler 2013-10-07 20:39:53 CEST
jani 

I did reboot. I have now removed .Xauthority it seems to work but is tempromental. I will reinstall and try from there.
Comment 6 Jani Välimaa 2013-10-07 20:50:51 CEST
IMHO reinstalling is never a good choice if we want to find out where's the bug.

Could you check if ~/.xsession-errors and ~/.xsession-errors.old contains any lightdm related info?
Comment 7 Jani Välimaa 2013-10-07 20:55:54 CEST
Check also /var/log/lightdm/lightdm.log and /var/log/lightdm/x-0-greeter.log.
Comment 8 martyn vidler 2013-10-07 20:59:55 CEST
I will
Comment 9 Dave Hodgins 2013-10-07 21:10:24 CEST
(In reply to Jani Välimaa from comment #6)
> IMHO reinstalling is never a good choice if we want to find out where's the
> bug.

In this case, as the procedure to create the bug
conditions is documented in the Description, and
has been confirmed to create the bug, testing a
reinstall is appropriate, as that will show whether
the bug is still present.

Martyn, in order to ensure the updated version is
used during the install, please be sure to enable
an online repo at the beginning of the install,
before package selection.
Comment 10 martyn vidler 2013-10-07 22:04:02 CEST
lightdm.log
http://pastebin.com/dX3ri61D

x-0-greeter.log
http://pastebin.com/TZF4HS16

I have created a new user rebooted user cant login. Checked home/user no .Xauthority file

This is not a new install just added a user
Comment 11 martyn vidler 2013-10-07 22:46:49 CEST
It is very tempromental, I was logged in as my user logged out went to log back in again looped, 2nd attempt I logged in My opion this has nothing todo with .Xauthority
sorry jani
Comment 12 Jani Välimaa 2013-10-08 10:55:34 CEST
Asking to remove ~/.Xauthority was just a shot in the dark as we must start from somewhere..

Please also attach ~/.xsession-errors and ~/.xsession-errors.old but please don't use pastebin as those pastes might expire and be unavailable later. Use bugzilla's "Add an attachment" feature instead and attach logs as text files.
Comment 13 Colin Guthrie 2013-10-08 11:54:42 CEST
I really don't like the lightdm pam files... They should likely include system-auth and not reinvent the wheel by themselves each time. Certain bits are needed locally but I would at least follow the gdm example whenever possible.

I suspect problems here could be related to the pam files setup, but would have to look myself to see and likely wont be able to do that for a while, so someone else could have a play around and see what they can find.
Comment 14 martyn vidler 2013-10-08 23:06:46 CEST
Created attachment 4415 [details]
lightdm log

Here are the files you asked for, more testing has also found the same problem with LXDE. I cant login into E17, ICEwm or gnome.
I have installed GDM and that seems to login ok
Comment 15 martyn vidler 2013-10-08 23:08:22 CEST
Created attachment 4416 [details]
x-0-greeter
Comment 16 martyn vidler 2013-10-08 23:09:33 CEST
Created attachment 4417 [details]
.Xauthority
Comment 17 martyn vidler 2013-10-08 23:10:17 CEST
Created attachment 4418 [details]
.xsessions-errors
Comment 18 martyn vidler 2013-10-08 23:23:19 CEST
Created attachment 4419 [details]
This is from test user .xsession-errors

This is where I cant login as test user
Jani Välimaa 2013-10-09 15:02:59 CEST

Attachment 4419 mime type: application/octet-stream => text/plain

Jani Välimaa 2013-10-09 15:03:37 CEST

Attachment 4417 mime type: application/octet-stream => text/plain

Jani Välimaa 2013-10-09 15:04:23 CEST

Attachment 4416 mime type: text/x-log => text/plain

Jani Välimaa 2013-10-09 15:04:49 CEST

Attachment 4418 mime type: application/octet-stream => text/plain

Comment 19 Jani Välimaa 2013-10-09 15:08:26 CEST
(In reply to martyn vidler from comment #14)
> Here are the files you asked for, more testing has also found the same
> problem with LXDE. I cant login into E17, ICEwm or gnome.
> I have installed GDM and that seems to login ok

Can't see anything weird in logs. Unfortunately I can't reproduce this bug, login to fresh E17 and Xfce works fine.
Comment 20 Jani Välimaa 2013-10-09 15:14:01 CEST
Related to PAM, what does 'ls /etc/pam.d/lightdm*' show?

You could also try lightdm with gdm's pam config. Do 'mv /etc/pam.d/lightdm /etc/pam.d/lightdm.orig' and 'cp /etc/pam.d/gdm /etc/pam.d/lightdm' and restart your machine.
Comment 21 martyn vidler 2013-10-09 18:30:53 CEST
jani

To recreate problem login as user, "sudo useradd" with passwd, logout then try to login as new user. I find once the new user has logged in then the problem is not so often, but it can also affect the original user login.

output of ls lightdm*
lightdm  lightdm-autologin  lightdm-greeter  lightdm-org

I have swapped lightdm for gdm as you asked so far it seems to work,
but when new user "as above" tried to login it did look like it was going to fail, but eventually did login.

Ref comment 14 It should of been LXDM I have had that fail as well
Comment 22 Jani Välimaa 2013-10-10 11:34:58 CEST
No "luck" with a new user either, can't reproduce.

To please Colin, I've now adapted pam configs from gdm. :P Copied them directly and renamed to suit for lightdm. Tested changes locally before pushing and all worked fine for me and my usage cases. However, if my change introduced regressions we have plenty of time to debug/fix them before mga4.

Please test new lightdm (which is also updated to 1.8.0). Check after update there're no lightdm related .rpmnew files in /etc/pam.d/. Mv them to original name if there're such files.
Comment 23 martyn vidler 2013-10-10 23:41:49 CEST
jani

That seems to have fixed it I have tried with new lightdm and cant get it to fail.

Just 1 other thing I can get LXDE display manger to fail the same way 

sorry

If I have to create a new bug or can you fix it in this report
Comment 24 Jani Välimaa 2013-10-30 20:31:26 CET
Please file a new bug about lxdm. You can mention this bug (bug 11379) in your new report.

I'm closing this as fixed.

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