Devuan bug report logs - #540
slim fails to get logind session if logout/login cycle is rapid

Package: slim; Maintainer for slim is Devuan Dev Team <devuan-dev@lists.dyne.org>; Source for slim is src:slim.

Reported by: Frank <fbug@xs4all.nl>

Date: Mon, 18 Jan 2021 20:33:01 UTC

Severity: normal

Fixed in version 1.3.6-5.2+devuan1

Done: dak@devuan.org

Forwarded to https://github.com/elogind/elogind/issues/95

Full log

Message #58 received at 540@bugs.devuan.org (full text, mbox, reply):

Received: (at 540) by bugs.devuan.org; 21 Jan 2021 10:10:04 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Thu, 21 Jan 2021 10:10:04 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-5.cfwn.uk [193.36.131.5])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 7A51AF60574
	for <540@bugs.devuan.org>; Thu, 21 Jan 2021 11:00:12 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1l2Wl8-0003K9-Jy; Thu, 21 Jan 2021 10:00:10 +0000
Received: (nullmailer pid 25241 invoked by uid 1000);
	Thu, 21 Jan 2021 10:00:10 -0000
Date: Thu, 21 Jan 2021 10:00:10 +0000
From: Mark Hindley <mark@hindley.org.uk>
To: Frank <fbug@xs4all.nl>
Cc: 540@bugs.devuan.org
Subject: Re: bug#540: elogind unmounts /run/user/$UID tmpfs filesystem after
 logging in again
Message-ID: <YAlQqj7R/L1rZj2x@hindley.org.uk>
References: <799226dc9af49ffdf449c54e013032e1@xs4all.nl>
 <YAbC59HtYZjxzfBo@hindley.org.uk>
 <799226dc9af49ffdf449c54e013032e1@xs4all.nl>
 <0d28c7c8b0ca461ef8376eee0c5ec18e@xs4all.nl>
 <YAcjg31ZR9ilODdY@hindley.org.uk>
 <7b2bac156d658c49f638856d445a3b3b@xs4all.nl>
 <85c8573180e595ee5805d973cc6b1cfa@xs4all.nl>
 <YAhkQkGH3fTAAHdP@hindley.org.uk>
 <a15165161f13c160ee428ad13b24eb6d@xs4all.nl>
 <2a8c1d6c190c0213201a9f496e9363e0@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2a8c1d6c190c0213201a9f496e9363e0@xs4all.nl>
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Frank,

Thanks. Very helpful.

On Wed, Jan 20, 2021 at 08:15:25PM +0100, Frank wrote:
> Adding "pam.setenv("XDG_SESSION_CLASS", "greeter");" to app.cpp, line 228,
> also works.
> That might be better than adding "export XDG_SESSION_CLASS=greeter" to
> "/etc/init.d/slim".

I am still trying to fully understand the implications of this.

It certainly makes sense for the slim login screen to be greeter class. But,
semantically, I would also expect the subsequent user login to be class user. I
don't yet know what other effects (if any) having the user login as class
greeter has.

Maybe we unset XDG_SESSION_CLASS again before pam.open_session? But maybe that
would no longer fix the issue you came across?

> Writing Display Managers (HOWTO):
> https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/

This seems to confirm that the user login itself should not be class greeter.

Mark

Send a report that this bug log contains spam.

Devuan bug report logs - #540 slim fails to get logind session if logout/login cycle is rapid

Devuan bug report logs - #540
slim fails to get logind session if logout/login cycle is rapid