Devuan bug report logs - #301
slim logins don't get registered in utmp

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

Reported by: Ralph Ronnquist <ralph.ronnquist@gmail.com>

Date: Thu, 7 Mar 2019 10:03:01 UTC

Severity: normal

Done: Mark Hindley <mark@hindley.org.uk>

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#301: slim logins don't get registered in utmp
Reply-To: Mark Hindley <mark@hindley.org.uk>, 301@bugs.devuan.org
Resent-From: Mark Hindley <mark@hindley.org.uk>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: owner@bugs.devuan.org
Resent-Date: Thu, 07 Mar 2019 19:03:01 UTC
Resent-Message-ID: <handler.301.B301.15519846077780@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: report 301
X-Devuan-PR-Package: slim
X-Devuan-PR-Keywords: 
Received: via spool by 301-submit@bugs.devuan.org id=B301.15519846077780
          (code B ref 301); Thu, 07 Mar 2019 19:03:01 UTC
Received: (at 301) by bugs.devuan.org; 7 Mar 2019 18:50:07 +0000
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Thu, 07 Mar 2019 19:50:07 +0100 (CET)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(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 9FBA7F60A32
	for <301@bugs.devuan.org>; Thu,  7 Mar 2019 19:40:15 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1h1xwA-0002f2-AT; Thu, 07 Mar 2019 18:40:12 +0000
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1h1xw6-0008AQ-Iu; Thu, 07 Mar 2019 18:40:06 +0000
Date: Thu, 7 Mar 2019 18:40:06 +0000
From: Mark Hindley <mark@hindley.org.uk>
To: 301@bugs.devuan.org
Cc: Ralph Ronnquist <ralph.ronnquist@gmail.com>
Message-ID: <20190307184006.GX17160@hindley.org.uk>
References: <13b902a1-2c17-4c1b-691a-f8fccf5a6e2d@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13b902a1-2c17-4c1b-691a-f8fccf5a6e2d@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org
On Thu, Mar 07, 2019 at 08:55:43PM +1100, Ralph Ronnquist wrote:
> I've also got a dist-upgraded beowulf with a no-install-recommends
> installation of task-xfce-desktop, and this one is fine wrt 'w'/'last'
> report for slim using consolekt, and still fine when I downgraded
> consolekit to the ascii version. The newest 'slim' is fine btw.
> 
> A little bit of digging tells me that my laptop has XDG_SESSION_COOKIE
> set which my beowulf VM doesn't. That difference might be enough to
> steer things differently for /etc/X11/Xsession.d/90consolekit, which (by
> guesswork) has a significant decision point about the session startup.
> Basically, X startup only runs /usr/bin/ck-launch-session if the
> variable is unset (at that time).
> 
> Someone who knows stuff might kindly pull me right, but now I'm chasing
> the reason why may latop gets XDG_SESSION_COOKIE set (while my beowulf
> VM doesn't)...

XDG_SESSION_COOKIE is set by consolekit. elogind doesn't set it, so that makes
me think your beowulf VM which is working OK is using elogind rather than
consolekit. Can you check?

Thanks

Mark


Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Thu Oct 22 23:35:57 2020;