[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#857977: marked as done (libpam-kwallet5: Kwallet doesn't unlock on login)



Your message dated Wed, 26 Apr 2017 11:24:45 +0200
with message-id <20170426092445.vhrgqwmrhwzmn3wm@gnuservers.com.ar>
and subject line Re: Bug#857977: libpam-kwallet5: Kwallet doesn't unlock on login
has caused the Debian Bug report #857977,
regarding libpam-kwallet5: Kwallet doesn't unlock on login
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
857977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857977
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-kwallet5
Version: 5.8.4-1
Severity: normal

Dear Maintainer,

on login, the default wallet doesn't seem to unlock, because programs prompt me
to enter wallet password.

Here are some more details:
- Password of the default wallet matches the login password and it uses
standard encryption
- Default wallet name is kdewallet
- I'm using default Stretch install + some additional programs. Login manager
is sddm
- As per guides on the Arch wiki, the /etc/pam.d/sddm file contains the
following

-auth   optional        pam_kwallet5.so
-session optional       pam_kwallet5.so auto_start

It seems to be setup properly out of the box. I didn't change anything.

Please provide some assistance on how to debug this situation.

Best Regards,
Andrej Mernik



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-kwallet5 depends on:
ii  libc6                  2.24-9
ii  libgcrypt20            1.7.6-1
ii  libpam-kwallet-common  5.8.4-1
ii  libpam0g               1.1.8-3.5
ii  socat                  1.7.3.1-2+b1

libpam-kwallet5 recommends no packages.

libpam-kwallet5 suggests no packages.

--- End Message ---
--- Begin Message ---
¡Hola!

In a private mail the submitter reported that the issue was related to an encrypted private folder containing the kwallet files, moving these to a folder that's present at login time fixed the issue. As such, I'm closing this issue. It might be interesting to reorder the private folder unlock so that it's there when kwallet tries to access it, it might be worth documenting these findings if someone tries this.

Happy hacking,
--
"If you can't write it down in English, you can't code it." -- Peter Halpern
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: