Arch Linux

FormBurden

Member

Registered: 2022-06-17

Posts: 5

KDEWallet not unlocking automatically with auto-login on with SDDM

While using SDDM's auto-login I'm running into an issue with KDEWallet not unlocking when I have it set up (what I think is correct) from the Wiki, and always receiving the unlock pass prompt.
Pretty much the same issue as this: KDEWallet won't automatically unlock, that never got resolved.

It's Discord, which I'm using DiscordCanary if that matters, and it's from an auto-start bash script I use.

Here are some logs:

journalctl -b | grep kwallet
Jun 17 13:47:37 Someone sddm-helper[2403]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: pam_sm_authenticate
Jun 17 13:47:37 Someone sddm-helper[2403]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get password (it is empty) *****NOTE: Already put in pass several times, but didn't here*****
Jun 17 13:47:37 Someone sddm-helper[2403]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
Jun 17 13:47:37 Someone sddm-helper[2403]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
Jun 17 13:47:38 Someone sddm-helper[2434]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Jun 17 13:47:38 Someone systemd[2405]: Started Unlock kwallet from pam credentials.
Jun 17 13:47:38 Someone kwalletd5[2435]: kf.wallet.kwalletd: Wallet failed to get opened by PAM, error code is -9
Jun 17 13:48:08 Someone kwalletd5[2435]: Application ' "discord" ' using kwallet without parent window!
Jun 17 13:48:33 Someone DiscordStart.sh[3738]: [3738:0617/134833.750464:ERROR:object_proxy.cc(642)] Failed to call method: org.kde.KWallet.open: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 17 13:48:33 Someone DiscordStart.sh[3738]: [3738:0617/134833.750498:ERROR:kwallet_dbus.cc(147)] Error contacting kwalletd5 (open)
Jun 17 14:48:38 Someone kwalletd5[2435]: Application ' "discord" ' using kwallet without parent window!

PAM /etc/pam.d/sddm

auth            include         system-login
-auth           optional        pam_gnome_keyring.so
-auth           optional        pam_kwallet5.so

account         include         system-login

password        include         system-login
-password       optional        pam_gnome_keyring.so use_authtok

session         optional        pam_keyinit.so force revoke
session         include         system-login
-session        optional        pam_gnome_keyring.so auto_start
-session        optional        pam_kwallet5.so auto_start

PAM /etc/pam.d/sddm-autologin

auth        required    pam_env.so
auth        required    pam_faillock.so preauth
auth        required    pam_shells.so
auth        required    pam_nologin.so
auth        required    pam_permit.so
-auth       optional    pam_gnome_keyring.so
-auth       optional    pam_kwallet5.so
account     include     system-local-login
password    include     system-local-login
session     include     system-local-login
-session    optional    pam_gnome_keyring.so auto_start
-session    optional    pam_kwallet5.so auto_start

PAM /etc/pam.d/login

auth       required     pam_securetty.so
auth       requisite    pam_nologin.so
auth       include      system-local-login
account    include      system-local-login
session    include      system-local-login
password   include      system-local-login

PC stats:

 

OS: Arch Linux 
Kernel: x86_64 Linux 5.18.3-arch1-1
Shell: zsh 5.9
DE: KDE 5.95.0 / Plasma 5.25.0
WM: KWin
Icon Theme: breeze-dark
CPU: AMD Ryzen 9 3900X 12-Core @ 24x 3.8GHz
GPU: NVIDIA GeForce RTX 2080 SUPER
RAM: 32021MiB

Note: I get auto-login is discuraged but I do have cryptlvm so I already have a pass prompt.

Anyway, anything I can do? Maybe some of the PAMs are mixed/not in order or something?

hypeit

Member

Registered: 2023-05-14

Posts: 8

Re: KDEWallet not unlocking automatically with auto-login on with SDDM

I have exactly the same issue, the problem is using autologin in sddm desktop session, it does not save password anywhere so pam cannot access it.