https://bugs.kde.org/show_bug.cgi?id=504539
--- Comment #9 from ledo.k...@gmail.com --- (In reply to michaelk83 from comment #8) > As I said earlier, we'll need a (good) backtrace, which shows the exact > source code location where the crash occurs, and the sequence of calls up to > that point. You've already provided the trace that you have, but it doesn't > show any usable info. > > Btw, there are a few other bug reports of a crash in kwallet. Maybe one of > them is the same as yours. Can you get anything useful from this output maybe? journalctl -b | grep kwallet May 22 02:01:55 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: pam_sm_authenticate May 22 02:01:55 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get password (it is empty) May 22 02:01:55 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Empty or missing password, doing nothing May 22 02:01:55 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred May 22 02:01:56 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session May 22 02:01:56 0000 sddm-helper[605]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key May 22 02:02:00 0000 systemd[616]: Started Unlock kwallet from pam credentials. May 22 02:02:04 0000 systemd[616]: Created slice Slice /app/dbus-:1.1-org.kde.kwalletd6. May 22 02:02:04 0000 systemd[616]: Started dbus-:1.1-org.kde.kwalletd6@0.service. May 22 02:02:05 0000 kwalletd6[950]: g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed May 22 02:02:05 0000 kwalletd6[950]: qt.dbus.integration: QDBusConnection: name 'org.kde.secretservicecompat' had owner '' but we thought it was ':1.38' May 22 02:02:05 0000 kwalletd6[950]: Secret Service availability changed: Available May 22 12:17:45 0000 drkonqi-coredump-processor[782]: "/usr/bin/kwalletmanager5" 1755 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.1755.1747086516000000.zst" May 22 12:17:45 0000 drkonqi-coredump-launcher[1524]: Unable to find file for pid 1755 expected at "kcrash-metadata/kwalletmanager5.9e276e744cd343688b91e4f6fd796803.1755.ini" May 22 12:17:45 0000 drkonqi-coredump-processor[782]: "/usr/bin/kwalletmanager5" 1922 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.1922.1747086587000000.zst" May 22 12:17:45 0000 drkonqi-coredump-processor[782]: "/usr/bin/kwalletmanager5" 2175 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.2175.1747086624000000.zst" May 22 12:17:45 0000 drkonqi-coredump-launcher[1529]: Unable to find file for pid 1922 expected at "kcrash-metadata/kwalletmanager5.9e276e744cd343688b91e4f6fd796803.1922.ini" May 22 12:17:45 0000 drkonqi-coredump-processor[782]: "/usr/bin/kwalletmanager5" 2355 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.2355.1747087101000000.zst" May 22 12:17:45 0000 drkonqi-coredump-launcher[1534]: Unable to find file for pid 2175 expected at "kcrash-metadata/kwalletmanager5.9e276e744cd343688b91e4f6fd796803.2175.ini" May 22 12:17:45 0000 drkonqi-coredump-launcher[1535]: Unable to find file for pid 2355 expected at "kcrash-metadata/kwalletmanager5.9e276e744cd343688b91e4f6fd796803.2355.ini" May 22 12:18:16 0000 drkonqi-coredump-gui[1693]: "/usr/bin/kwalletmanager5" 1755 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.1755.1747086516000000.zst" May 22 12:18:16 0000 drkonqi-coredump-gui[1693]: "/usr/bin/kwalletmanager5" 1922 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.1922.1747086587000000.zst" May 22 12:18:16 0000 drkonqi-coredump-gui[1693]: "/usr/bin/kwalletmanager5" 2175 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.9e276e744cd343688b91e4f6fd796803.2175.1747086624000000.zst" May 22 12:18:16 0000 drkonqi-coredump-gui[1693]: "/usr/bin/kwalletmanager5" 2355 "/ -- You are receiving this mail because: You are watching all bug changes.
