Bugzilla – Bug 1221445
kde mega release, kwallet, automatical signon, fail
Last modified: 2024-03-25 08:35:37 UTC
Created attachment 873534 [details] kwallet installation Yesterday there was the famous kde mega release. Today when kde logging I must fill the kwallet password. I assume all about kwallet 6 is badly updated. If you see all about kwallet with yast software manager you can see there is a mix of 5 and 6 version of kwallet , kwallet pam,kwallet signon. Some kwallet 6 version packages are installed and some not. Some kwallet 5 version packages are installed and some not. Same things for kwallet pam and kwallet signon packages.
I had to add auth optional pam_kwallet5.so to common-auth-pc and password optional pam_kwallet5.so to common-password-pc and session optional pam_kwallet5.so to common-session-pc. After that, the qllet is unlocked again during login with the login password. Nevertheless, Kontact still asks for my IMAP passwords, while it connects to nextcloud calendars with the passwords fro the wallet.
> After that, the qllet is unlocked again during login with the login password. ^ wallet
Duplicate of bug 1221371. (In reply to Michael Hirmke from comment #1) > I had to add > > auth optional pam_kwallet5.so > > to common-auth-pc and > > password optional pam_kwallet5.so > > to common-password-pc and > > session optional pam_kwallet5.so > > to common-session-pc. You need to undo those changes and run `zypper in --force pam_kwallet6` to have it properly configured again. *** This bug has been marked as a duplicate of bug 1221371 ***
thanks but "zypper in --force pam_kwallet6" leads to "Problème : l'élement pam_kwallet6-6.0.1-1.1.x86_64 à installer nécessite '(pam_kwallet6-32bit if pam-32bit)', mais cette exigence ne peut pas être remplie Solution 1 : Les actions suivantes seront exécutées : désinstallation de pam-32bit-1.6.0-4.1.x86_64 désinstallation de pam_kwallet-32bit-5.27.10-1.2.x86_64 désinstallation de pam_pwquality-32bit-1.4.5-2.2.x86_64 désinstallation de samba-client-libs-32bit-4.19.5+git.342.57620c4f7e-1.1.x86_64 désinstallation de samba-winbind-libs-32bit-4.19.5+git.342.57620c4f7e-1.1.x86_64 désinstallation de systemd-32bit-254.9-2.1.x86_64 désinstallation de gnome-keyring-pam-32bit-42.1-3.2.x86_64 désinstallation de samba-ad-dc-libs-32bit-4.19.5+git.342.57620c4f7e-1.1.x86_64 rétrogradation de libavformat60-32bit-6.1.1-1699.3.pm.18.x86_64 à libavformat60-32bit-6.1.1-1.4.x86_64 installer libavformat60-32bit-6.1.1-1.4.x86_64 du fournisseur openSUSE en remplaçant libavformat60-32bit-6.1.1-1699.3.pm.18.x86_64 du fournisseur http://packman.links2linux.de désinstallation de samba-libs-32bit-4.19.5+git.342.57620c4f7e-1.1.x86_64 Solution 2 : ne pas installer pam_kwallet6-6.0.1-1.1.x86_64 Solution 3 : casser pam_kwallet6-6.0.1-1.1.x86_64 en ignorant certaines de ses dépendances " What to do ?
I select "1" i logged out then logged in. the problem is still there. I must fill the password for kwallet.
> You need to undo those changes and run `zypper in --force pam_kwallet6` to > have it properly configured again. > > *** This bug has been marked as a duplicate of bug 1221371 *** So, it is still pam_kwallet*5*.so?
(In reply to Michael Hirmke from comment #6) > > You need to undo those changes and run `zypper in --force pam_kwallet6` to > > have it properly configured again. > > > > *** This bug has been marked as a duplicate of bug 1221371 *** > > So, it is still pam_kwallet*5*.so? And it doesn't help anyway - Kontact still asks for IMAP passwords.
Created attachment 873537 [details] installed kwallet packages see the installation of kwallet
I confirm this is about akonadi imap password which needs to access to kwallet.
(In reply to Episteme PROMENEUR from comment #5) > I select "1" If pam_kwallet6 was not installed at all before, you'll have to run `zypper in --force pam_kwallet6` again. > i logged out then logged in. > > the problem is still there. I must fill the password for kwallet. (In reply to Michael Hirmke from comment #6) > > You need to undo those changes and run `zypper in --force pam_kwallet6` to > > have it properly configured again. > > > > *** This bug has been marked as a duplicate of bug 1221371 *** > > So, it is still pam_kwallet*5*.so? Yes.
i installed kf6-kwallet-tools and kf6-kwallet-tools-lang. no success. it remains a package "libkwalletbackend5-5"
I did again sudo zypper in --force pam_kwallet6 there is no more problem. thanks do we need "libkwalletbackend5-5" ?
(In reply to Episteme PROMENEUR from comment #12) > I did again > > sudo zypper in --force pam_kwallet6 > > there is no more problem. > > thanks > > do we need "libkwalletbackend5-5" ? It's not necessary to install any lib* packages manually.
You did not understand. This version 5 package remains after intalling kwallet 6. I did not installed anything.
(In reply to Michael Hirmke from comment #7) > (In reply to Michael Hirmke from comment #6) > > > You need to undo those changes and run `zypper in --force pam_kwallet6` to > > > have it properly configured again. > > > > > > *** This bug has been marked as a duplicate of bug 1221371 *** > > > > So, it is still pam_kwallet*5*.so? > > And it doesn't help anyway - Kontact still asks for IMAP passwords. Besides that, I get: systemd[1]: Started Process Core Dump (PID 5023/UID 0). systemd-coredump[5024]: Process 1919 (kwalletmanager5) of user 10000 dumped core. Stack trace of thread 1919: #0 0x00007f4f104949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x00007f4f10441176 raise (libc.so.6 + 0x41176) #2 0x00007f4f12cd8b93 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6b93) #3 0x00007f4f10441240 __restore_rt (libc.so.6 + 0x41240) #4 0x00007f4f104949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #5 0x00007f4f10441176 raise (libc.so.6 + 0x41176) #6 0x00007f4f10428917 abort (libc.so.6 + 0x28917) #7 0x00007f4f104297e8 __libc_message_impl.cold (libc.so.6 + 0x297e8) #8 0x00007f4f1049f3c7 malloc_printerr (libc.so.6 + 0x9f3c7) #9 0x00007f4f1049f6ec munmap_chunk (libc.so.6 + 0x9f6ec) #10 0x00007f4f104a418a free (libc.so.6 + 0xa418a) #11 0x00007f4f10dca6b7 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1ca6b7) #12 0x00007f4f130365b9 _ZN13KXmlGuiWindow5eventEP6QEvent (libKF6XmlGui.so.6 + 0xa95b9) #13 0x00007f4f11fc1aae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c1aae) #14 0x00007f4f10d87498 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x187498) #15 0x00007f4f10d877f7 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1877f7) #16 0x00007f4f10d8b903 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x18b903) #17 0x000055a5f003b26d n/a (kwalletmanager5 + 0x2826d) #18 0x00007f4f1042a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #19 0x00007f4f1042a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #20 0x000055a5f003b375 n/a (kwalletmanager5 + 0x28375) Stack trace of thread 1927: #0 0x00007f4f1050578f __poll (libc.so.6 + 0x10578f) #1 0x00007f4f101cfaff n/a (libglib-2.0.so.0 + 0x5daff) #2 0x00007f4f101d020c g_main_context_iteration (libglib-2.0.so.0 + 0x5e20c) #3 0x00007f4f10fa330c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a330c) #4 0x00007f4f10d91cbb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x191cbb) #5 0x00007f4f10e66a44 _ZN7QThread4execEv (libQt6Core.so.6 + 0x266a44) #6 0x00007f4f125e9cfa n/a (libQt6DBus.so.6 + 0x33cfa) #7 0x00007f4f10ee5779 n/a (libQt6Core.so.6 + 0x2e5779) #8 0x00007f4f10492bb2 start_thread (libc.so.6 + 0x92bb2) #9 0x00007f4f1051400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 1929: #0 0x00007f4f1050578f __poll (libc.so.6 + 0x10578f) #1 0x00007f4f106828aa n/a (libxcb.so.1 + 0xe8aa) #2 0x00007f4f1068441c xcb_wait_for_event (libxcb.so.1 + 0x1041c) #3 0x00007f4f0e30ccc0 n/a (libQt6XcbQpa.so.6 + 0x5dcc0) #4 0x00007f4f10ee5779 n/a (libQt6Core.so.6 + 0x2e5779) #5 0x00007f4f10492bb2 start_thread (libc.so.6 + 0x92bb2) #6 0x00007f4f1051400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 1932: #0 0x00007f4f1048effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007f4f10491d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007f4f0550f41b n/a (iris_dri.so + 0x10f41b) #3 0x00007f4f05504687 n/a (iris_dri.so + 0x104687) #4 0x00007f4f10492bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007f4f1051400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 1933: #0 0x00007f4f1048effe __futex_abstimed_wait_common (libc.so.6 + 0x8effe) #1 0x00007f4f10491d40 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x91d40) #2 0x00007f4f0550f41b n/a (iris_dri.so + 0x10f41b) #3 0x00007f4f05504687 n/a (iris_dri.so + 0x104687) #4 0x00007f4f10492bb2 start_thread (libc.so.6 + 0x92bb2) #5 0x00007f4f1051400c __clone3 (libc.so.6 + 0x11400c) Stack trace of thread 4994: #0 0x00007f4f1050578f __poll (libc.so.6 + 0x10578f) #1 0x00007f4ef8840e71 n/a (libpulse.so.0 + 0x33e71) #2 0x00007f4ef882a854 pa_mainloop_poll (libpulse.so.0 + 0x1d854) #3 0x00007f4ef88350d6 pa_mainloop_iterate (libpulse.so.0 + 0x280d6) #4 0x00007f4ef8835180 pa_mainloop_run (libpulse.so.0 + 0x28180) #5 0x00007f4ef8844e19 n/a (libpulse.so.0 + 0x37e19) #6 0x00007f4ef3f4889f n/a (libpulsecommon-17.0.so + 0x5d89f) #7 0x00007f4f10492bb2 start_thread (libc.so.6 + 0x92bb2) #8 0x00007f4f1051400c __clone3 (libc.so.6 + 0x11400c) ELF object binary architecture: AMD x86-64 systemd[1]: systemd-coredump@2-5023-0.service: Deactivated successfully.
(In reply to Michael Hirmke from comment #7) > (In reply to Michael Hirmke from comment #6) > > > You need to undo those changes and run `zypper in --force pam_kwallet6` to > > > have it properly configured again. > > > > > > *** This bug has been marked as a duplicate of bug 1221371 *** > > > > So, it is still pam_kwallet*5*.so? > > And it doesn't help anyway - Kontact still asks for IMAP passwords. Correction: It does not ask for the IMAP, but for the SIEVE passwords! IMAP passwords are listed in the wallet, SIEVE ones not, although "remember password" was activated.
(In reply to Michael Hirmke from comment #16) > (In reply to Michael Hirmke from comment #7) > > (In reply to Michael Hirmke from comment #6) > > > > You need to undo those changes and run `zypper in --force pam_kwallet6` to > > > > have it properly configured again. > > > > > > > > *** This bug has been marked as a duplicate of bug 1221371 *** > > > > > > So, it is still pam_kwallet*5*.so? > > > > And it doesn't help anyway - Kontact still asks for IMAP passwords. > > Correction: It does not ask for the IMAP, but for the SIEVE passwords! > IMAP passwords are listed in the wallet, SIEVE ones not, although "remember > password" was activated. That's probably unrelated. https://bugs.kde.org/show_bug.cgi?id=478474 affects other distributions