Devuan bug report logs - #391
keyring is not not unlocked

version graph

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

Reported by: Saša Janiška <gour@atmarama.com>

Date: Fri, 7 Feb 2020 13:03:01 UTC

Severity: normal

Found in version 1.3.6-5.1+devuan6

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

Full log


🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Saša Janiška <gour@atmarama.com>
Subject: bug#391 closed by Mark Hindley <mark@hindley.org.uk> (Re:
 bug#391: keyring is not not unlocked)
Message-ID: <handler.391.D391.15813515008388.notifdone@bugs.devuan.org>
References: <20200210161150.GP14807@hindley.org.uk>
 <20200207134846.647a18fb@atmarama.ddns.net>
X-Devuan-PR-Message: they-closed 391
X-Devuan-PR-Package: slim
Reply-To: 391@bugs.devuan.org
Date: Mon, 10 Feb 2020 16:33:05 +0000
Content-Type: multipart/mixed; boundary="----------=_1581352385-8413-1"
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your bug report
which was filed against the slim package:

#391: keyring is not not unlocked

It has been closed by Mark Hindley <mark@hindley.org.uk>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.


-- 
391: https://bugs.devuan.org/cgi/bugreport.cgi?bug=391
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
From: Mark Hindley <mark@hindley.org.uk>
To: Saša Janiška <gour@atmarama.com>
Cc: 391-done@bugs.devuan.org
Subject: Re: bug#391: keyring is not not unlocked
Date: Mon, 10 Feb 2020 16:11:50 +0000
Version: 1.3.6-5.1+devuan6

On Mon, Feb 10, 2020 at 04:15:03PM +0100, Saša Janiška wrote:
> Mark Hindley <mark@hindley.org.uk> writes:
> 
> > Are you using consolekit or elogind for session managment?
> 
> I was using consolekit and 'solved' the problem by changing display
> manager to lightdm and using elogind.

OK.

I am going to close this since you had Debian's version of slim installed
(1.3.6-5.1) rather than Devuan's (1.3.6-5.1+devuan6).

As far as I can tell Devuan's version works correctly in this regard.

Thanks

Mark
[Message part 3 (message/rfc822, inline)]
From: Saša Janiška <gour@atmarama.com>
To: submit@bugs.devuan.org
Subject: keyring is not not unlocked
Date: Fri, 7 Feb 2020 13:48:46 +0100
Package: slim
Version: 1.3.6-5.1

Hello, I do not have auto-login enabled and created default keyring with the
same passwd as for my login, but the keyring is not unlocked automatically
after login although I've enabled launching of 'GNOME services'

According to e.g. Arch's wiki
(https://wiki.archlinux.org/index.php/SLiM#Gnome_Keyring): "Note: slim 1.3.5-1
ships with /etc/pam.d/slim preconfigured to unlock keyring upon login. Users no
longer need to modify the file."

Any hint?

I'm on Ceres.

$ uname -a
Linux atmarama 5.4.0-3-amd64 #1 SMP Debian 5.4.13-1 (2020-01-19) x86_64 GNU/Linux
Sincerely,
Gour

 
-- 
Bewildered by the modes of material nature, the ignorant fully
engage themselves in material activities and become attached. But
the wise should not unsettle them, although these duties are inferior
due to the performers' lack of knowledge.

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 Apr 26 03:31:53 2024;