sddm-greeter and IdleHint?

[dirteat]

Hi there,
got an issue with sddm-greeter running. It seems that the session it opens always return an active state thereby preventing systemd-logind to detect an Idle state (which I use to put the system automatically in suspend). Any chance this could be fixed?

Thanks.

[plfiorini]

This is something that the desktop you are using should deal with.

[eatdust]

Thanks for your comment, but I would have said that this cannot be related to the desktop, but to the system as it is a systemd feature. Not logging in into any DE, sddm running as "sddm" user and not reporting idle prevent systemd to do its suspending job.
Cheers.

[plfiorini]

Ah sorry I didn't understand the issue completely and having seen no answer for 22 days I decided to close.

That being said I'm not sure how to handle this without involving too much external libraries, so I will leave this open until a good solution can be found.

[eatdust]

Ok, thanks!
I'll have a look too in the meantime, that is important to us (@mageia) as this feature used to work with kdm. With the plasma move, the next mga6 release will certainly have its main dm as sddm!
cheers.

[dirteat]

I am bouncing on this old issue first because it still there and then because I suspect it is more profound than just preventing the system to suspend.
The fact that sddm opens a user session is bad. More precisely, it opens an user session which, as far as I understand, is undifferentiated from a standard user. So all systemd --user services are also triggered by the sddm user's slice. I have no idea how this could be improved, but that causes a lot of troubles at various levels.
Any ideas would be welcome,
Cheers.

[davidedmundson]

because I suspect it is more profound than just preventing the system to suspend.
Based on what?

The fact that sddm opens a user session is bad.
I understand, is undifferentiated from a standard user
We do report to pam_systemd that this is a special greeter session as the XDG_SESSION_CLASS.
Both of these are as described in https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/

[dirteat]

If I reverse engineer you very short answer, you are trying to say that the fact that sddm beaks systemd autosuspend and automatically triggers all systemd user services as a real user is not the sddm problem but some underlying bug within systemd/pam_systemd?

I am happy to report such a problem upstream, if that so (although I thought you were a bit upstream already). Sorry to have assumed that you were actually understanding systemd better than I do...