FS#36446 - [lxdm] Additional line in /etc/pam.d/lxdm needed to prevent error after second logout from xfce4

Attached to Project: Community Packages
Opened by Tuomas Jäntti (qwertypoke) - Wednesday, 07 August 2013, 17:03 GMT
Last edited by Balló György (City-busz) - Sunday, 08 September 2013, 21:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Balló György (City-busz)
Daniel Wallace (gtmanfred)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After second logout from xfce4, lxdm hangs or does not show logon screen. This is discussed in detail:
https://bbs.archlinux.org/viewtopic.php?pid=1289209

A solution to this seems to be:

Add following line:
[code]
session required pam_systemd.so
[/code]
to /etc/pam.d/lxdm

This seems to be required also by slim and other display managers. I cannot verify if the problem concerns other desktops than xfce4. I do not know if something should be fixed in xfce4 rather than in this configuration file (that is owned by the lxdm-package). I also do not know, would adding the line to /etc/pam.d/lxdm break some other desktop.

I was going to report this upstream but sourceforge contains an old 0.3.0 package.

Additional info:
* package version(s)
0.4.1-22
* config and/or log files etc.


Steps to reproduce:

install lxdm (or slim and probably any display manager).
install xfce4
start lxdm
login
logout
login
logout
Lxdm is dead now.
This task depends upon

Closed by  Balló György (City-busz)
Sunday, 08 September 2013, 21:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  Restart=always is added to the systemd unit file in lxdm 0.4.1-24
Comment by Daniel Wallace (gtmanfred) - Friday, 09 August 2013, 22:38 GMT
Merge your pacnews, don't just delete them.

This is the last two lines of the file and does it correctly.

-session optional pam_loginuid.so
-session optional pam_systemd.so
Comment by Tuomas Jäntti (qwertypoke) - Saturday, 17 August 2013, 02:05 GMT
  • Field changed: Percent Complete (100% → 0%)
This is not true on my installation. I have a fresh installation. There are no .pacnew files and I have certainly not deleted any.

My /etc/pam.d/lxdm contains:

#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
auth required pam_unix.so
account required pam_unix.so
session required pam_limits.so
session required pam_unix.so
password required pam_unix.so
-session optional pam_loginuid.so
-session optional pam_systemd.so

After second logout the graphical greeter is not shown. Ctrt-alt-f7 shows a text console. The lxdm.service seems to be running according to systemctl status. What additional information is required?
Comment by Balló György (City-busz) - Saturday, 17 August 2013, 02:16 GMT
I think it would better to include system PAM configuration as in LightDM and SLIM:
https://projects.archlinux.org/svntogit/community.git/tree/trunk/lightdm.pam?h=packages/lightdm
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/slim.pam?h=packages/slim

Related report for LightDM:
https://bugs.archlinux.org/task/34298

@Tuomas: is it solve the problem if you replace the /etc/pam.d/lxdm file with one of the files above?
Comment by Tuomas Jäntti (qwertypoke) - Monday, 19 August 2013, 07:04 GMT
I tried both above files. Both result in no GUI logon after second logout.

I have also slim installed. The problem seems to be the same there. The above /etc/pam.d/slim requires adding:

session required pam_systemd.so

else the behaviour is also no GUI logon screen afer second logout.

I can verify the behaviour only with xfce4.
Comment by Balló György (City-busz) - Friday, 06 September 2013, 06:03 GMT
Please test the version 0.4.1-24, it's in the [community-testing] repository. It still crashes for me on every second logout, but now the systemd file contains the 'Restart=always' parameter, so lxdm will be restarted immediately.
Comment by Tuomas Jäntti (qwertypoke) - Sunday, 08 September 2013, 18:02 GMT
I confirm that 0.4.1-24 works just as György described.
Comment by Balló György (City-busz) - Sunday, 08 September 2013, 21:06 GMT
Okay, then I'm closing this bug. The crash is a session handling problem, it's reported here: https://bugs.archlinux.org/task/36533

Loading...