[kwallet-pam] [Bug 356785] New: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 Bug ID: 356785 Summary: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5 Product: kwallet-pam Version: 5.4.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i...@kobaltwit.be I have installed pam-kwallet-5.4.2-1 from updates-testing. This version should be able to open both kwallet4 and kwallet5 at login. However 9 times out of 10 I am still asked for a password for kwallet4 on login. Kwallet5 is always opened without asking for a password. Reproducible: Always Steps to Reproduce: 1. Install pam-kwallet-5.4.2-1, kde-runtime-15.08.1-2.fc22.x86_64 (for kde4's kwallet), kf5-kwallet-5.14.0-1.fc22.x86_64 (for kf5's kwallet). Optionally also install kde4's and kf5's version of kwalletmanager for easy testing. 2. Make sure you use the same password for login, and the default wallets in both versions 3. Log in to the system and verify which wallets are opened automatically Actual Results: On my system, kf5's default wallet is always opened, while kde4's default wallet isn't. I remember it worked a couple of times early on. Expected Results: Both default wallets should be opened at login. I have tested this with a recent version of sddm (0.12..0-5). I am aware old versions won't work. A couple of links that may be of interest: * https://quickgit.kde.org/?p=kwallet-pam.git&a=shortlog&h=352904c7500e44fcc6788291244882484c7b5962 is the git commit log for pam-kwallet on branch 5.4. Commits on 2015-07-28 are related to getting this functionality to work with both versions of kwallet at the same time. * http://martys.typepad.com/blog/2015/07/kwallet5-can-be-auto-unlocked-during-login-again.html?cid=6a012876e7556d970c01b7c7c640fc970b was the announcement of this feature. The comments have some discussion on initial issues with it, leading to the commits I refer to in the previous link. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 356785] New: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 Bug ID: 356785 Summary: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5 Product: kwallet-pam Version: 5.4.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i...@kobaltwit.be I have installed pam-kwallet-5.4.2-1 from updates-testing. This version should be able to open both kwallet4 and kwallet5 at login. However 9 times out of 10 I am still asked for a password for kwallet4 on login. Kwallet5 is always opened without asking for a password. Reproducible: Always Steps to Reproduce: 1. Install pam-kwallet-5.4.2-1, kde-runtime-15.08.1-2.fc22.x86_64 (for kde4's kwallet), kf5-kwallet-5.14.0-1.fc22.x86_64 (for kf5's kwallet). Optionally also install kde4's and kf5's version of kwalletmanager for easy testing. 2. Make sure you use the same password for login, and the default wallets in both versions 3. Log in to the system and verify which wallets are opened automatically Actual Results: On my system, kf5's default wallet is always opened, while kde4's default wallet isn't. I remember it worked a couple of times early on. Expected Results: Both default wallets should be opened at login. I have tested this with a recent version of sddm (0.12..0-5). I am aware old versions won't work. A couple of links that may be of interest: * https://quickgit.kde.org/?p=kwallet-pam.git&a=shortlog&h=352904c7500e44fcc6788291244882484c7b5962 is the git commit log for pam-kwallet on branch 5.4. Commits on 2015-07-28 are related to getting this functionality to work with both versions of kwallet at the same time. * http://martys.typepad.com/blog/2015/07/kwallet5-can-be-auto-unlocked-during-login-again.html?cid=6a012876e7556d970c01b7c7c640fc970b was the announcement of this feature. The comments have some discussion on initial issues with it, leading to the commits I refer to in the previous link. -- You are receiving this mail because: You are watching all bug changes.
