Bug 842646 - Lightdm's autologin functionality does not work on F17 (pam configuration issue)
Summary: Lightdm's autologin functionality does not work on F17 (pam configuration issue)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: lightdm
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-24 10:44 UTC by Clemens Eisserer
Modified: 2012-08-06 22:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-06 22:49:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Clemens Eisserer 2012-07-24 10:44:39 UTC
Description of problem:

Lightdm's autologin functionality is broken on F17, with the following settings autologin does not work:

user-authority-in-system-dir=true
greeter-hide-users = True to hide the user list
session-wrapper=/etc/X11/xinit/Xsession
greeter-session=lightdm-greeter
autologin-user=ce
autologin-user-timeout=0

This is caused by a broken pam-configuration file. After copying /etc/pam.d/gdm-autologin to /etc/pam.d/lightdm-autologin, everything works as expected.


Version-Release number of selected component (if applicable):
lightdm-1.2.2-16.fc17.x86_64


How reproducible: Very

Actual results: Autologin does not work without manual intervention
Expected results: Autologin should work out-of-the box

Comment 1 Fedora Update System 2012-07-25 18:56:22 UTC
lightdm-1.2.2-17.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/lightdm-1.2.2-17.fc16

Comment 2 Fedora Update System 2012-07-25 18:56:32 UTC
lightdm-1.2.2-17.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/lightdm-1.2.2-17.fc17

Comment 3 Fedora Update System 2012-07-26 03:52:08 UTC
Package lightdm-1.2.2-17.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lightdm-1.2.2-17.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11074/lightdm-1.2.2-17.fc17
then log in and leave karma (feedback).

Comment 4 Clemens Eisserer 2012-08-03 08:58:40 UTC
Unfourtunatly, lightdm-1.2.2-17.fc17.i686 doesn't solve the problem - autologin with lightdmfails like it did before applying the update.

Overwriting lightdm-autologin with gdm-autologin solves the issue still.

Comment 5 Fedora Update System 2012-08-03 11:24:24 UTC
lightdm-1.2.2-17.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2012-08-03 11:27:04 UTC
lightdm-1.2.2-17.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Clemens Eisserer 2012-08-03 11:40:19 UTC
The problem still persists, as mentioned 3 hours ago :(

Comment 8 Gregor Tätzner 2012-08-03 13:44:19 UTC
(In reply to comment #4)
> Unfourtunatly, lightdm-1.2.2-17.fc17.i686 doesn't solve the problem -
> autologin with lightdmfails like it did before applying the update.
> 
> Overwriting lightdm-autologin with gdm-autologin solves the issue still.
Well, thats not helpful. We need logs: at least /var/log/secure and /var/log/lightdm/lightdm.log of an failed autologin attempt.

Comment 9 Sergio 2012-08-06 14:38:39 UTC
It's working properly here (just tested auto-login with 0 timeout).

Clemens, you need to set the default user session.
Check the contents of /usr/share/xsessions.

Here I changed

#user-session=default

for

user-session=xfce

Comment 10 Clemens Eisserer 2012-08-06 22:22:56 UTC
Sergio: I don't even have a file /usr/share/xsessions, its a directory which contains just a single file named xfce.desktop
Are you on F17?

I'll re-test soon and provide the required log files.

Comment 11 Clemens Eisserer 2012-08-06 22:49:03 UTC
Please don't shoot - I just gave it a try again and it worked out-of-the-box.
Thanks for fixing this issue.


Note You need to log in before you can comment on or make changes to this bug.