

61·
2 months ago@bimbimboy I think it’s needed because kwallet does no longer get the password from the login via a PAM module, so it has no way to unlock the wallet that’s encrypted with your password anymore.
@bimbimboy I think it’s needed because kwallet does no longer get the password from the login via a PAM module, so it has no way to unlock the wallet that’s encrypted with your password anymore.
@Zamundaaa @arcsnim i guess equal or even more features should equal more ram usage. But I also think that the lower ram usage is due to the lack of telemetry and bloat and ai and bing and online only stuff :D
@bimbimboy I don’t think that would solve the problem. KWallet-PAM would be the way it gets the password from the login manager. PAM is the pluggable authentication modules framework, where you can plug in a module to do stuff during authentication, so kwallet inserts itself into the login process to read the password and unlock your wallet.
According to the arch linux wiki on KWallet: “When using autologin, the wallet can only be unlocked if the autologin method saves the password. pam_autologin does, for example.” https://wiki.archlinux.org/title/KDE/_Wallet maybe there is a way then.