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

Package: slim; Reported by: Ralph Ronnquist <ralph.ronnquist@gmail.com>;
Date: Thu, 7 Mar 2019 10:03:01 UTC;
Done: Mark Hindley <mark@hindley.org.uk>;
Maintainer for slim is (unknown).

View this report as an mbox folder.


Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#301; Package slim. Full text available.



Message sent to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:

Subject: bug#301: slim logins don't get registered in utmp
Date: Wed, 17 Apr 2019 11:33:08 +0100
From: Mark Hindley <mark@hindley.org.uk>
To: 301@bugs.devuan.org

On Fri, Mar 08, 2019 at 05:27:34PM +0000, Mark Hindley wrote:
> Ralph,
> 
> Could you try adding this configuration to /etc/slim.conf please?
> 
> # sessreg. You can use the %user variable
> sessionstop_cmd exec sessreg -d -l $DISPLAY %user
> sessionstart_cmd exec sessreg -a -l $DISPLAY %user
> 
> It fixes slim utmp/wtmp/lastlog registration for me although the process is
> identified as ?xdm?. Trying to fix that....

Ralph,

Just a follow up on this.

Although it is ugly, I think the ?xdm? in the IDLE column out from w is
technically correct: w is unable to determine the correct idle time for X. You
need xprintidle or the like for that.

Other than that, sessreg correctly registers sessions in utmp and lastlog for
me.

Can you confirm it works for you?

Mark





Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Mon, 18 Nov 2019 07:39:09 UTC