Devuan bug report logs - #348
libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive

Package: libpam-ck-connector; Maintainer for libpam-ck-connector is Devuan Developers <devuan-dev@lists.dyne.org>; Source for libpam-ck-connector is src:consolekit2.

Reported by: Arne Wichmann <aw@saar.de>

Date: Thu, 29 Aug 2019 13:18:01 UTC

Severity: minor

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#348; Package libpam-ck-connector. (full text, mbox, link).


Acknowledgement sent to Arne Wichmann <aw@saar.de>:
New bug report received and forwarded. Copy sent to owner@bugs.devuan.org. (full text, mbox, link).


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

From: Arne Wichmann <aw@saar.de>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Subject: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Thu, 29 Aug 2019 15:09:20 +0200
Package: libpam-ck-connector
Version: 1.2.1-4
Severity: normal

Good day to you.

When doing as root:
  echo 'su $USER ls'|at now
auth.log logs
  [...] su: pam_ck_connector(su:session): cannot determine display-device

I presume that is because there rightfully is none.

If this is not a more general bug, it should at least be possible to
silence the logging as it spams (at least my) log files.

Thank you for your effords!

AW

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux ascii
Release:	9
Codename:	n/a
Architecture: x86_64

Kernel: Linux 5.2.7 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.iso885915, LC_CTYPE=en_GB.iso885915 (charmap=ISO-8859-15), LANGUAGE=en_GB.iso885915 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libpam-ck-connector depends on:
ii  libc6             2.28-10
ii  libck-connector0  1.2.1-4
ii  libdbus-1-3       1.10.28-0+deb9u1+devuan2
ii  libpam-runtime    1.1.8-3.6
ii  libpam0g          1.3.1-5

libpam-ck-connector recommends no packages.

libpam-ck-connector suggests no packages.

-- no debconf information


Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#348; Package libpam-ck-connector. (Wed, 01 Apr 2020 16:03:01 GMT) (full text, mbox, link).


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

From: Mark Hindley <mark@hindley.org.uk>
To: 348@bugs.devuan.org
Cc: Arne Wichmann <aw@saar.de>
Subject: Re: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Wed, 1 Apr 2020 16:52:49 +0100
Arne,

Control: tags -1 moreinfo

Thanks for this and sorry about the slow reply.

On Thu, 29 Aug 2019 15:09:20 +0200 Arne Wichmann <aw@saar.de> wrote:
> Package: libpam-ck-connector
> Version: 1.2.1-4
> Severity: normal
> 
> Good day to you.
> 
> When doing as root:
>   echo 'su $USER ls'|at now
> auth.log logs
>   [...] su: pam_ck_connector(su:session): cannot determine display-device
> 
> I presume that is because there rightfully is none.

I have just tried this in a beowulf VM and cannot reproduce it.

The current version is 1.2.1-8 although I can't immediately see anything in the
changelog that might have fixed it.

Please can you verify it is still present and give instructions to reproduce.

Thanks

Mark

Added tag(s) moreinfo. Request was from Mark Hindley <mark@hindley.org.uk> to control@bugs.devuan.org. (Thu, 02 Apr 2020 09:18:02 GMT) (full text, mbox, link).


Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#348; Package libpam-ck-connector. (Thu, 02 Apr 2020 11:03:02 GMT) (full text, mbox, link).


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

From: Mark Hindley <mark@hindley.org.uk>
To: 348@bugs.devuan.org
Cc: Arne Wichmann <aw@saar.de>
Subject: Re: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Thu, 2 Apr 2020 11:52:30 +0100
Control: tags -1 -moreinfo

Arne,

On Wed, Apr 01, 2020 at 04:52:49PM +0100, Mark Hindley wrote:
> On Thu, 29 Aug 2019 15:09:20 +0200 Arne Wichmann <aw@saar.de> wrote:
> > Package: libpam-ck-connector
> > Version: 1.2.1-4
> > Severity: normal
> > 
> > Good day to you.
> > 
> > When doing as root:
> >   echo 'su $USER ls'|at now
> > auth.log logs
> >   [...] su: pam_ck_connector(su:session): cannot determine display-device
> > 
> > I presume that is because there rightfully is none.
> 
> I have just tried this in a beowulf VM and cannot reproduce it.

I have managed to reproduce this.

I can't immediately see there is a bug in what consolekit is doing. As you say,
there is no display device.

If you want to avoid the messages appearing in your logs, then I suggest the
following rsyslog configuration (or something similar to your taste).

% cat /etc/rsyslog.d/10-local.conf
:msg, contains, "cannot determine display-device" ~

That filters the messages for me.

Is that a solution for you?

Thanks

Mark

Removed tag(s) moreinfo. Request was from Mark Hindley <mark@hindley.org.uk> to 348-submit@bugs.devuan.org. (Thu, 02 Apr 2020 11:03:04 GMT) (full text, mbox, link).


Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#348; Package libpam-ck-connector. (Thu, 02 Apr 2020 11:33:02 GMT) (full text, mbox, link).


Acknowledgement sent to Arne Wichmann <aw@old-forest.org>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Thu, 02 Apr 2020 11:33:04 GMT) (full text, mbox, link).


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

From: Arne Wichmann <aw@old-forest.org>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 348@bugs.devuan.org
Subject: Re: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Thu, 2 Apr 2020 13:12:14 +0200
[Message part 1 (text/plain, inline)]
Hi, and thanks for taking the time.

begin  quotation  from Mark Hindley (in <20200402105230.GH4674@hindley.org.uk>):
> On Wed, Apr 01, 2020 at 04:52:49PM +0100, Mark Hindley wrote:
> > On Thu, 29 Aug 2019 15:09:20 +0200 Arne Wichmann <aw@saar.de> wrote:
> > > Package: libpam-ck-connector
> > > Version: 1.2.1-4
> > > Severity: normal
> > > 
> > > Good day to you.
> > > 
> > > When doing as root:
> > >   echo 'su $USER ls'|at now
> > > auth.log logs
> > >   [...] su: pam_ck_connector(su:session): cannot determine display-device
> > > 
> > > I presume that is because there rightfully is none.
> > 
> > I have just tried this in a beowulf VM and cannot reproduce it.
> 
> I have managed to reproduce this.
> 
> I can't immediately see there is a bug in what consolekit is doing. As you say,
> there is no display device.
> 
> If you want to avoid the messages appearing in your logs, then I suggest the
> following rsyslog configuration (or something similar to your taste).
> 
> % cat /etc/rsyslog.d/10-local.conf
> :msg, contains, "cannot determine display-device" ~

I should note that.

> That filters the messages for me.
> 
> Is that a solution for you?

Well - the bug is mostly logging as an error which is at most an info: not
having a display device should be considered a normal case, it can happen
for quite a number of reasons.

I surely can make the message go away.

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (aw@saar.de)
[signature.asc (application/pgp-signature, inline)]

Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#348; Package libpam-ck-connector. (Thu, 02 Apr 2020 13:03:02 GMT) (full text, mbox, link).


Acknowledgement sent to Mark Hindley <mark@hindley.org.uk>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Thu, 02 Apr 2020 13:03:05 GMT) (full text, mbox, link).


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

From: Mark Hindley <mark@hindley.org.uk>
To: Arne Wichmann <aw@old-forest.org>
Cc: 348@bugs.devuan.org
Subject: Re: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Thu, 2 Apr 2020 13:47:42 +0100
On Thu, Apr 02, 2020 at 01:12:14PM +0200, Arne Wichmann wrote:
> Well - the bug is mostly logging as an error which is at most an info: not
> having a display device should be considered a normal case, it can happen
> for quite a number of reasons.
> 
> I surely can make the message go away.

Ah, I see. We can lower the syslog level to warning for this case.

The problem with lowering it further is that in some cases it is a problem. I'll
take a look to see if there is a way of disentangling those.

Thanks.

Mark

Information forwarded to devuan-bugs@lists.dyne.org, Devuan Developers <devuan-dev@lists.dyne.org>:
bug#348; Package libpam-ck-connector. (Thu, 02 Apr 2020 13:18:01 GMT) (full text, mbox, link).


Acknowledgement sent to Arne Wichmann <aw@old-forest.org>:
Extra info received and forwarded to list. Copy sent to Devuan Developers <devuan-dev@lists.dyne.org>. (Thu, 02 Apr 2020 13:18:03 GMT) (full text, mbox, link).


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

From: Arne Wichmann <aw@old-forest.org>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 348@bugs.devuan.org
Subject: Re: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Date: Thu, 2 Apr 2020 15:06:29 +0200
[Message part 1 (text/plain, inline)]
begin  quotation  from Mark Hindley (in <20200402124742.GI4674@hindley.org.uk>):
> On Thu, Apr 02, 2020 at 01:12:14PM +0200, Arne Wichmann wrote:
> > Well - the bug is mostly logging as an error which is at most an info: not
> > having a display device should be considered a normal case, it can happen
> > for quite a number of reasons.
> > 
> > I surely can make the message go away.
> 
> Ah, I see. We can lower the syslog level to warning for this case.
> 
> The problem with lowering it further is that in some cases it is a
> problem. I'll take a look to see if there is a way of disentangling
> those.

Really understanding (and possibly documenting - at least in the code) the
problematic interactions is of course "the kings way" (as we might say in
german).

Again - thank you for caring! Even though I now see the problem is minor.

cu

AW
-- 
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (aw@saar.de)
[signature.asc (application/pgp-signature, inline)]

Severity set to 'minor' from 'normal' Request was from Arne Wichmann <aw@anhrefn.saar.de> to control@bugs.devuan.org. (Thu, 26 Oct 2023 16:14:01 GMT) (full text, mbox, link).


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: Fri Mar 29 09:07:28 2024;