Is this project abandoned?

[m3thm4th]

I switched on my monitor and found my desktop unlocked, with all programs and windows open. I was sure I locked it, so I found it strange. I moved the mouse and immediately was thrown back to the lockscreen. This is a HUGE issue.
I came here and looked for similar issues, I found nothing like this, but I found many severe issues from years ago that didn't even receive an answer, the latest release is from 4 years ago and only one commit was made the past year.
@robert-ancell Is this project dead?

[lo1ol]

Under "switching on my monitor" you mean switching to different tty? What DE are you use?

Yeah, it's popular problem. Lightdm opens lock screen at different TTY and send DBus lock command to logind. If your desktop environment doesn't handle this signal -- your session still will be opened on another tty.

For example, GNOME even disables its lock screen if it was started not via GDM.

I agree that it's kind of issue of lightdm. But in general you should use lightdm with DE that properly handle logind signals, to avoid such issues. Another option is not use lightdm Lock Screen and rely on Lock Screen of your DE, but I don't know how to force lightdm to disable its Lock Screen functionality.

[lo1ol]

Btw I don't know about status of Lightdm. It looks like abandoned, at least because their maintainers ignore all issues and MRs

[m3thm4th]

I'm using it with xfce, and no, I didn't switch tty, I locked the screen, turned display off and when I turned it on again I could see the desktop with all apps open until an input was registered.

I realized this might be an issue with X11 itself becauseon X11 the lockscreen is a full screen app, and if it crashes you can just access the desktop, or if whatever else happens relusts may be unpredictable. I don't know if switching display manager might solve the issue, but I never experienced that with SDDM on KDE for example, with lightdm it happened 2 or 3 times already.

Apparently you are right the devs don't care about issues here, maybe it's because Ubuntu officially supports Gnome only. Sad.

[elig0n]

@m3thm4th missing details. What DE? what lock screen application ? do you have loginctl lingering enabled ?

[m3thm4th]

@elig0n I already said I'm on xfce, the lockscreen is lightdm itself.

loginctl only returns 2 sessions, the manager and the user, I didn't enable lingering and it's a single user device.

[codethief]

@lo1ol

Yeah, it's popular problem. Lightdm opens lock screen at different TTY and send DBus lock command to logind. If your desktop environment doesn't handle this signal -- your session still will be opened on another tty.

I came across this ticket by accident but I just checked and… it looks like my desktop environment doesn't handle the lock signal, either. Where can I read up on this and on what needs to happen behind the scenes? (My DE isn't really a full-blown DE as much as it is a bespoke Xsession + i3 setup, so I'm not surprised at all that the signal isn't handled. :) I'm just wondering what I need to do to fix this.)

Also, am I understanding this correctly that if my DE handles the lock signal, LightDM will not use different TTYs but a single one for all sessions + greeter?

[codethief]

@m3thm4th May I suggest you rename the ticket? Your question whether LightDM is still being maintained is valid but the discussion now revolves around the specific issue you raised, so I'd propose separating these topics. (Which might also make it easier for other people experiencing the same issue to find the present ticket.)

[lo1ol]

LightDM will not use different TTYs

As I know LightDM always opening in different TTY.

Xsession + i3 setup

Yeah, i3 has no build-in Lock Screen. So, you need to install your own and start it on session start up. I found that there is some xss-lock and it says that it support logind commands.

So, try and setup it or different Lock Screen:)

[m3thm4th]

@codethief the discussion is tangential, the real issue is this project has seen no activity for more than 1 year and no maintainer is monitoring anything here.

[miasma]

@m3thm4th If you look at the releases, the last one is almost 4 years old. After that there has been only a handful of real commits that affect the actual runtime behavior. CI patches, updates to tests, service files, documentation etc. don't fix any real bugs. Even before the very latest release, there was a 3 year gap between the releases. If you look at the changelogs, half of the entries are useless for ordinary users. I'd say this project has been dead for 7 years now.

[m3thm4th]

Thanks @miasma it is very unfortunate considering how many distros and DEs rely on lightdm. The light login managers are all gone, ly seems to be the last one standing.