Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48077 - [lightdm] desktop fails to start after login
Attached to Project:
Arch Linux
Opened by Ken Milmore (octree) - Sunday, 07 February 2016, 19:25 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 07 February 2016, 20:55 GMT
Opened by Ken Milmore (octree) - Sunday, 07 February 2016, 19:25 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 07 February 2016, 20:55 GMT
|
DetailsDescription:
Logging in through lightdm fails to start desktop and returns immediately to login prompt. Same behaviour occurs on both Xfce and KDE plasma desktops. User .xsession-errors is empty after the failed login. Cause seems to be as follows: See the lightdm PKGBUILD, prepare() function, the patch to config file has recently been commented out. This causes the upstream version of /etc/lightdm.conf to be installed, which does not appear to work. Note that a user who has edited /etc/lightdm.conf locally may not notice the problem, as their old copy should be retained when upgrading. Additional info: Affects lightdm 1:1.16.7-2 Steps to reproduce: 1. Install lightdm lightdm-1:1.16.7-2 with empty or unedited config in /etc/lightdm. 2. Attempt to log in to desktop from the lightdm prompt. Observe that the login fails. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 07 February 2016, 20:55 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#48075
Sunday, 07 February 2016, 20:55 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Marten Lienen (cqql) -
Sunday, 07 February 2016, 19:42 GMT
I, too, just ran into this. The problem is that the new default configuration uses an unknown script named `lightdm-session` instead of `/etc/lightdm/Xsession`.