Login issue: Lightdm + LDAP + Kerberos
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
Fix Released
|
Critical
|
Wojciech |
Bug Description
lightdm 1.7.15-0ubuntu1, Ubuntu 13.10
- Local users can login without problems on command line and LightDM
- Kerberos/LDAP authenticated users can login on command line
- Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes "/usr/sbin/
- If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to "init" in the .xsession-errors. First of them is "init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory"
.xession-errors for both setup attached to this bug report
No problems with Ubuntu 12.04.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lightdm 1.7.15-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Fri Sep 20 12:21:13 2013
InstallationDate: Installed on 2013-09-20 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917)
MarkForUpload: True
ProcEnviron:
LANGUAGE=de_DE
TERM=xterm
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in lightdm (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in lightdm (Ubuntu): | |
importance: | Undecided → Critical |
Changed in lightdm (Ubuntu): | |
assignee: | nobody → Wojciech (wojaugustow) |
status: | Confirmed → Fix Committed |
Changed in lightdm (Ubuntu): | |
status: | Fix Committed → Fix Released |
Would you be able to try this with another display manager, e.g. gdm?
Can you see what $PATH is set to when logging in on a terminal? It looks at first glance like the session can't find upstart, and that can't find the session processes to run.