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

Full log

🔗 View this message in rfc822 format

Subject: bug#348: libpam-ck-connector: pam_ck_connector logs cannot determine display-device when non-interactive
Reply-To: Arne Wichmann <aw@old-forest.org>, 348@bugs.devuan.org
Resent-From: Arne Wichmann <aw@old-forest.org>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Devuan Developers <devuan-dev@lists.dyne.org>
Resent-Date: Thu, 02 Apr 2020 11:33:02 +0000
Resent-Message-ID: <handler.348.B348.158582640524520@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
References: <156708416092.7556.11299955678221931618.reportbug@anhrefn.saar.de> <20200401155249.GF4674@hindley.org.uk> <20200402105230.GH4674@hindley.org.uk> <156708416092.7556.11299955678221931618.reportbug@anhrefn.saar.de>
Date: Thu, 2 Apr 2020 13:12:14 +0200
From: Arne Wichmann <aw@old-forest.org>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 348@bugs.devuan.org
Message-ID: <20200402111214.GD25187@anhrefn.saar.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="2Z2K0IlrPCVsbNpk"
Content-Disposition: inline
In-Reply-To: <20200402105230.GH4674@hindley.org.uk>
Return-Receipt-To: aw@anhrefn.saar.de
User-Agent: Mutt/1.10.1 (2018-07-13)

[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)]

Send a report that this bug log contains spam.

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

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