This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Autounlock kwallet under KDE neon 5.13 doesn't work

Tags: None
(comma "," separated)
stempst0r
Registered Member
Posts
2
Karma
0
Hello folks,

I'm new to this forum! Was looking on the whole www for a working solution for my problem, but couldn't find a answer. Maybe someone here can help!

With my new laptop (Lenovo Thinkpad T480s) i wanted to give KDE another try. So i decided to install KDE neon. As far I'm very happy with it as a daily driver.
The only small problem i can't solve: kwallet should automatically unlock at login.
Steps I made so far:

- kwallet uses standard blowfish encryption
- kwallet pw is the same as the current user
- autologin into user account is DISABLED
- wallet is named "kwallet"

my /etc/pam.d/sddm looks like this:
Code: Select all
#%PAM-1.0

# Block login if they are globally disabled
auth    requisite       pam_nologin.so
auth    required        pam_succeed_if.so user != root quiet_success

# auth    sufficient      pam_succeed_if.so user ingroup nopasswdlogin
@include common-auth
# gnome_keyring breaks QProcess
-auth   optional        pam_gnome_keyring.so
-auth   optional        pam_kwallet.so
-auth   optional        pam_kwallet5.so

@include common-account

# SELinux needs to be the first session rule.  This ensures that any
# lingering context has been cleared.  Without this it is possible that a
# module could execute code in the wrong domain.
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
# Create a new session keyring.
session optional        pam_keyinit.so force revoke
session required        pam_limits.so
session required        pam_loginuid.so
session required        pam_systemd.so
@include common-session
# SELinux needs to intervene at login time to ensure that the process starts
# in the proper default security context.  Only sessions which are intended
# to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
-session optional       pam_gnome_keyring.so auto_start
-session optional       pam_kwallet.so  auto_start
-session optional       pam_kwallet5.so auto_start

@include common-password

# From the pam_env man page
# Since setting of PAM environment variables can have side effects to other modules, this module should be the last one on the stack.

# Load environment from /etc/environment
session required        pam_env.so

# Load environment from /etc/default/locale and ~/.pam_environment
session required        pam_env.so envfile=/etc/default/locale user_readenv=1


on some forums I saw that "kwallet-pam" should be installed but i can't find any package with this name.
The distro is untouched so far.

Hope someone can help. mybe this is a bug with the new Ubuntu 18.04 LTE underneath KDE Neon?
gianlucapettinello
Registered Member
Posts
1
Karma
0
What you read was relating to Archlinux.
And the name of the wallet is kdewallet and not kwallet
stempst0r
Registered Member
Posts
2
Karma
0
Could resolve the issue for myself.

Kwallet can't be autounlocked if your home-folder is encrypted on startup.

So i made a new setup for my machine with an encrypted LVM (i wanted an encryption for my data) and now it works out of the box!
User avatar
bobbywibowo
Registered Member
Posts
52
Karma
0
OS
stempst0r wrote:Kwallet can't be autounlocked if your home-folder is encrypted on startup.

Darn, is there no other alternative to this? Can't it attempt to unlock the wallet AFTER decrypting home folder? :(


"LIfe is like riding a bicycle. To keep your balance, you must keep moving." - Albert Einstein

Homepage: https://fiery.me


Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot]