Package: slim; Reported by: Ralph Ronnquist <ralph.ronnquist@gmail.com>; dated Thu, 7 Mar 2019 10:03:01 UTC; Maintainer for slim is (unknown).
Received: (at 301) by bugs.devuan.org; 13 Jun 2019 15:30:04 +0000 From: Dimitris <dimitris@stinpriza.org> To: 301@bugs.devuan.org Subject: Re: slim logins don't get registered in utmp Date: Thu, 13 Jun 2019 18:24:35 +0300 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hZAhE0hJQ75DVqXBZkXLkPtiAF4yuuhH7 Content-Type: multipart/mixed; boundary="v4slUxddPXxdvuKVQlhOutynJZfgD6XyU"; protected-headers="v1" From: Dimitris <dimitris@stinpriza.org> To: 301@bugs.devuan.org Message-ID: <92c951e8-ba3e-cbf6-94d3-bb3f3cdf29f3@stinpriza.org> Subject: Re: slim logins don't get registered in utmp --v4slUxddPXxdvuKVQlhOutynJZfgD6XyU Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Content-Language: en-US dGVzdGVkIGFnYWluIHVzaW5nIHNsaW0vZXhwZXJpbWVudGFsIC7CoCBkZXZ1YW4gdGVzdGlu Zy9jZXJlcyBhbWQ2NC4KCiMgdwrCoDE4OjE4OjEwIHVwwqAgODozOSzCoCAxIHVzZXIswqAg bG9hZCBhdmVyYWdlOiAwLjc1LCAwLjY2LCAwLjczClVTRVLCoMKgwqDCoCBUVFnCoMKgwqDC oMKgIEZST03CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAgTE9HSU5AwqDCoCBJRExFwqDCoCBK Q1BVwqDCoCBQQ1BVIFdIQVQKdXNlciDCoMKgwqDCoMKgIDowLjDCoMKgwqDCoCA6MC4wwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgIDA5OjM4wqDCoCA/eGRtP8KgwqAgMjo1M23CoCAyLjI3 cwp4LXNlc3Npb24tbWFuYWdlcgoKIyBsYXN0wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgCnVz ZXIgwqDCoMKgwqDCoCA6MC4wwqDCoMKgwqDCoMKgwqDCoCA6MC4wwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgIFRodSBKdW4gMTMgMDk6MzjCoMKgIHN0aWxsIGxvZ2dlZCBpbgpyZWJvb3TC oMKgIHN5c3RlbSBib290wqAgNC4xOS4wLTUtYW1kNjTCoMKgIFRodSBKdW4gMTMgMDk6MzjC oMKgIHN0aWxsIHJ1bm5pbmcKCiMgbGFzdGxvZyAtdSB1c2VyClVzZXJuYW1lwqDCoMKgwqDC oMKgwqDCoCBQb3J0wqDCoMKgwqAgRnJvbcKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCBMYXRl c3QKdXNlciDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA6MC4wwqDCoMKgwqDCoMKgwqDC oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgIFRodSBKdW4gMTMgMDk6Mzg6NTggKzAzMDAg MjAxOQoKIyBhcHQgcG9saWN5IHNsaW3CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqAKCnNsaW06 CsKgIEluc3RhbGxlZDogMS4zLjYtNS4xK2RldnVhbjMKCgp0aGFua3MsCgpkaW1pdHJpcy4K CgoK --v4slUxddPXxdvuKVQlhOutynJZfgD6XyU-- --hZAhE0hJQ75DVqXBZkXLkPtiAF4yuuhH7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEddlu1gom7sXWP9ZRvUcY7+WkADkFAl0CarMACgkQvUcY7+Wk ADnLyAv/fHXx/8T3KstrF90R2e8gBQMVwNau/4RfOTNKzqHGN+DSPPiSI4+f7vfl JkezES99dp2HnTRB8aFR2A8JRXbDuoxfmiTG2cvE/D4Md1ez65b1fQItY7cF9vEu inVGAiJ87pZoVYIgbpFNz3Y1CpaEQKpnna6Dzn9tYhom/X9G/CmK7VRmRugl154W MY4QGCYivtba3m62g8zFd2BLGQgXrLgp1vxwE1P1E8S0iYsUPmHExAFrTXRxHRL4 IEUJXt7aBNHfYKPphbob4BQdkzDmf7pjl0aGv3lz+xWJEHN3ypjz5gxR+aOM/x7V QkzoFlgk2pd1uWoob5jxpM/D1BXWbZIRUbO+1WXY3jllPEUhFyJJwaQsoa5JQR/D 1OJ4/4VXH3DmQ57cQ/ZkzShwdBiT90XSJ9v51dPGLCd8utuLTNWEr085EqjA7+dk w+7t9+bLIYASELjXpy1MvvqeY67JazzS5i6XovJ07W/UkPxYnejU08GmJv1yANbW iTCW3ezx =62fu -----END PGP SIGNATURE----- --hZAhE0hJQ75DVqXBZkXLkPtiAF4yuuhH7--
Dimitris <dimitris@stinpriza.org>:owner@bugs.devuan.org.
Full text available.devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:bug#301; Package slim.
Full text available.Received: (at 301) by bugs.devuan.org; 17 Apr 2019 10:40:06 +0000 Date: Wed, 17 Apr 2019 11:33:08 +0100 From: Mark Hindley <mark@hindley.org.uk> To: 301@bugs.devuan.org Subject: Re: slim logins don't get registered in utmp 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
Mark Hindley <mark@hindley.org.uk>:owner@bugs.devuan.org.
Full text available.devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:bug#301; Package slim.
Full text available.Received: (at 301) by bugs.devuan.org; 8 Mar 2019 17:30:05 +0000 Date: Fri, 8 Mar 2019 17:27:34 +0000 From: Mark Hindley <mark@hindley.org.uk> To: 301@bugs.devuan.org Subject: Re: slim logins don't get registered in utmp 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.... Mark
Mark Hindley <mark@hindley.org.uk>:owner@bugs.devuan.org.
Full text available.devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:bug#301; Package slim.
Full text available.Received: (at 301) by bugs.devuan.org; 7 Mar 2019 18:50:07 +0000 Date: Thu, 7 Mar 2019 18:40:06 +0000 From: Mark Hindley <mark@hindley.org.uk> To: 301@bugs.devuan.org Subject: Re: slim logins don't get registered in utmp 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
Mark Hindley <mark@hindley.org.uk>:owner@bugs.devuan.org.
Full text available.devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:bug#301; Package slim.
Full text available.Received: (at submit) by bugs.devuan.org; 7 Mar 2019 10:00:02 +0000 To: Devuan Bug Tracking System <submit@bugs.devuan.org> From: Ralph Ronnquist <ralph.ronnquist@gmail.com> Subject: slim logins don't get registered in utmp Date: Thu, 7 Mar 2019 20:55:43 +1100 Package: slim Version: 1.3.6-5+devuan6 slim doesn't seem to update /var/run/utmp and /var/log/wtmp anymore? ........... also previous versions of slim: I'm still getting the 'w' report: ------ 08:06:53 up 0 min, 0 users, load average: 0.29, 0.08, 0.02 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT ------ Likewise, 'last' tells about reboot and tty1 login(s) but not my 'slim' logins. I getting the same with the previous slim distributions as well; I returned to 1.3.6-5.1+devuan2 just to verify, and I've now also gone "back" to 1.3.6-5+devuan4, which 'apt-cache policy slim' claims is the jessie version; the 'w' report stays the same (also after reboots). So, apparently 'slim' since long ago believes something else is responsible for registring the session(s), but that something else doesn't agree. Maybe that's down to 'consolekit', then? ......... [addition by wirelessduck via dng@lists.dyne.org] I’m running consolekit with lightdm on a regular ascii. I just installed slim alongside lightdm and set it as default. Rebooted and logged in via slim. I get nothing listed when running 'w' and 'who'. Checking output of 'last' shows the reboot time correctly but my slim login doesn’t appear at all. I switched back to lightdm and I see my user appearing in the output of both 'w' and 'who'. The 'last' output also shows my lightdm login from tty7. I should note that this login account comes from winbind, but I don’t think that should be affecting this at all? —Tom .............. Further on this: 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)... Ralph.
Ralph Ronnquist <ralph.ronnquist@gmail.com>:owner@bugs.devuan.org.
Full text available.devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:bug#301; Package slim.
Full text available.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:
Tue, 18 Jun 2019 06:39:01 UTC