Summary: | pam_kwallet6 not being built on/for Qt6 systems | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kwallet-pam | Reporter: | Fernando M. Muniz <fernandommuniz> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kimiblock, moyamat555, nate, reverier.xu |
Priority: | NOR | ||
Version: | 6.1.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kwallet-pam/-/commit/44fc23974b895b4d69709edaa6a2e63297f824a2 | Version Fixed In: | 6.1.2 |
Sentry Crash Report: | |||
Attachments: | kded6 - kdewallet |
Similar situation here. After upgrading to 6.1.1 kdewallet for some reason is not unlocking itself automatically even when login password and wallet password match. seems pam_kwallet5.so is broken: $ journalctl -b | grep kwallet Jun 27 21:03:08 Reverier-Arch greetd[866]: PAM unable to dlopen(/usr/lib/security/pam_kwallet5.so): /usr/lib/security/pam_kwallet5.so: undefined symbol: gcry_check_version Jun 27 21:03:08 Reverier-Arch greetd[866]: PAM adding faulty module: /usr/lib/security/pam_kwallet5.so Jun 27 21:03:09 Reverier-Arch greetd[961]: PAM unable to dlopen(/usr/lib/security/pam_kwallet5.so): /usr/lib/security/pam_kwallet5.so: undefined symbol: gcry_check_version Jun 27 21:03:09 Reverier-Arch greetd[961]: PAM adding faulty module: /usr/lib/security/pam_kwallet5.so Jun 27 21:05:53 Reverier-Arch systemd[1476]: Started Unlock kwallet from pam credentials. Jun 27 21:05:55 Reverier-Arch xdg-desktop-por[1570]: Choosing kwallet.portal for org.freedesktop.impl.portal.Secret via the deprecated UseIn key Jun 27 21:15:23 Reverier-Arch systemd[1476]: Created slice Slice /app/dbus-:1.2-org.kde.kwalletd6. Jun 27 21:15:23 Reverier-Arch systemd[1476]: Started dbus-:1.2-org.kde.kwalletd6@0.service. Jun 27 21:15:23 Reverier-Arch kwalletd6[12837]: Application ' "Microsoft Edge" ' using kwallet without parent window! Downgrading kwallet-pam to 6.1.0-1 temporarily resolves the issue. kwallet 6.1.1-2 has been pushed which fixes this issue > seems pam_kwallet5.so is broken:
pam_kwallet5 is for Qt5 software. You need pam_kwallet6.so. I see on my own system that it isn't getting built though.
(In reply to Nate Graham from comment #5) > > seems pam_kwallet5.so is broken: > pam_kwallet5 is for Qt5 software. You need pam_kwallet6.so. I see on my own > system that it isn't getting built though. No, there is only pam_kwallet5 which is Qt version agnostic. The issue is a failure to pick up libgcrypt 1.11 at build time and should be fixed with https://invent.kde.org/plasma/kwallet-pam/-/merge_requests/17 Oh I see, I guess the number is just misleading then. Git commit 3c11e10bbb8f30efd8fc95bd0f0ff6487310fd11 by Albert Astals Cid, on behalf of Daniel Exner. Committed on 01/07/2024 at 14:46. Pushed by aacid into branch 'master'. Switch to pkgconfig to find libgcrypt (allows building with libgcrypt 1.11) see https://invent.kde.org/libraries/qca/-/merge_requests/113 and https://invent.kde.org/libraries/qca/-/merge_requests/115 M +3 -3 CMakeLists.txt D +0 -67 cmake/modules/FindLibGcrypt.cmake https://invent.kde.org/plasma/kwallet-pam/-/commit/3c11e10bbb8f30efd8fc95bd0f0ff6487310fd11 Git commit 44fc23974b895b4d69709edaa6a2e63297f824a2 by Albert Astals Cid, on behalf of Daniel Exner. Committed on 01/07/2024 at 14:48. Pushed by aacid into branch 'Plasma/6.1'. Switch to pkgconfig to find libgcrypt (allows building with libgcrypt 1.11) see https://invent.kde.org/libraries/qca/-/merge_requests/113 and https://invent.kde.org/libraries/qca/-/merge_requests/115 (cherry picked from commit 3c11e10bbb8f30efd8fc95bd0f0ff6487310fd11) M +3 -3 CMakeLists.txt D +0 -67 cmake/modules/FindLibGcrypt.cmake https://invent.kde.org/plasma/kwallet-pam/-/commit/44fc23974b895b4d69709edaa6a2e63297f824a2 |
Created attachment 171078 [details] kded6 - kdewallet Now that I've updated to Plasma 6.1.1 , this message/window in the screenshot attached keeps popping up after login into my account. I don't use "kdewallet", so I don't know why this is happening on every login.