You are not logged in.
- Topics: Active | Unanswered
#26 2015-05-21 14:15:02
- andreyv
- Member
- From: Riga, Latvia
- Registered: 2012-11-02
- Posts: 34
Re: LightDM still running after unlock
It is another bug: https://bugs.launchpad.net/lightdm/+bug/1441356
Offline
#27 2015-05-21 14:17:03
- Chazza
- Wiki Maintainer
- Registered: 2013-06-02
- Posts: 506
Re: LightDM still running after unlock
Ah yes - I should have read the thread more carefully. Thanks andreyv.
Offline
#28 2015-05-26 06:55:24
- Alucryd
- Developer
- From: France
- Registered: 2011-05-07
- Posts: 110
- Website
Re: LightDM still running after unlock
Finally got the time to test 2.0.1. For some reason I still had several lightdm sessions with it, but rebuilding the greeter with --enable-kill-on-sigterm fixed the issue.
Chazza: There will always be one lightdm session running in the background, gdm is the same.
The bird of Hermes is my name, eating my wings to make me tame.
Offline
#29 2015-05-26 07:05:16
- andreyv
- Member
- From: Riga, Latvia
- Registered: 2012-11-02
- Posts: 34
Re: LightDM still running after unlock
There will always be one lightdm session running in the background, gdm is the same.
LightDM closes greeter sessions if they are not needed. If not for the bug I linked above, there should be no lightdm sessions when a user is logged in and active.
Offline
#30 2015-05-26 08:40:01
- Chazza
- Wiki Maintainer
- Registered: 2013-06-02
- Posts: 506
Re: LightDM still running after unlock
Chazza: There will always be one lightdm session running in the background, gdm is the same.
I was talking about the greeter processes though, not the lightdm session. Say I have a session running on tty7 and then I decide to user switch. The session on tty7 will be locked and I'll be brought to a newly started lightdm greeter on tty8. If I then authenticate the user through that greeter, I'll be brought back to the user session on tty7 which will have been unlocked. Now, if I switch back to tty8, I should find a black screen and a flashing cursor because the greeter process should have been killed. What I should not find is that the greeter is still running.
Edit: adding the --enable-kill-on-sigterm flag appears to have fixed the issue I describe above. Thanks Alucryd.
Last edited by Chazza (2015-05-26 08:50:10)
Offline