So, quite frequently at boot up I get a popup notification that says kwallet crashed (I do not remember exactly what it says, but that is the gist of the message). However, kwallet still works fine for applications that require it. I have it set to auto unlock by leaving password blank and calling the wallet “kdewallet” and creating a file at ~/.local/share/dbus-1/services/org.freedesktop.secrets.service.
Again the crash seems to not affect operation in any way (except it needing to start itself back up when starting an application that requires it), as applications that rely on this service still work fine, and when opening them kwallet opens right back up (I used lsof to check the differences and kwallet6 is indeed running and working fine).
Additional information about my system:
packages:
Name : kwallet-pam
Version : 6.4.3-1
Name : kwallet
Version : 6.16.0-1
Name : plasma-desktop
Version : 6.4.3-1
Name : plasma-x11-session
Version : 6.4.3-1
My .xinitrc:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
# start some nice programs
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?* ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
export XDG_CURRENT_DESKTOP=KDE
export XDG_SESSION_TYPE=x11
export DESKTOP_SESSION=plasma
exec startplasma-x11
/etc/pam.d/login:
auth requisite pam_nologin.so
auth include system-local-login
auth optional pam_kwallet5.so
account include system-local-login
session include system-local-login
session optional pam_kwallet5.so auto_start force_run
password include system-local-login
~/.local/share/dbus-1/services/org.freedesktop.secrets.service:
[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/kwalletd6
~/.zprofile:
if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then
exec startx
fi
/etc/systemd/system/getty@tty1.service.d/override.conf:
[Service]
ExecStart=
ExecStart=-/usr/bin/agetty --autologin username --noclear %I $TERM
That is all there is to my startup as far as I know.
As a workaround, I’ve disabled “Application Crash” in the “System Notifications” setting in the kde settings app. I am unsure of whether that worked or not yet though as it did not crash this boot. The issue itself is actually intermittent and I am unsure of the cause (I usually just open a browser (or 2 browsers) and maybe a file manager when I startup my machine and that’s really it). I checked the log from last boot with “sudo journalctl -b -1 --no-pager -p err” and that produced this (which is probably related?, not sure as I’m not really a dev):
Jul 17 16:01:25 username systemd-coredump[237979]: Process 164477 (ksecretd) of user 1000 dumped core.
Stack trace of thread 164477:
#0 0x000079ea2e6a774c n/a (libc.so.6 + 0x9774c)
#1 0x000079ea2e64ddc0 raise (libc.so.6 + 0x3ddc0)
#2 0x000079ea309f8e97 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x7e97)
#3 0x000079ea2e64def0 n/a (libc.so.6 + 0x3def0)
#4 0x000079ea3091ad6e n/a (libqca-qt6.so.2 + 0x6ed6e)
#5 0x000079ea3091b3a1 _ZN3QCA12MemoryRegionD1Ev (libqca-qt6.so.2 + 0x6f3a1)
#6 0x00005dbd7c836bc5 n/a (/usr/bin/ksecretd + 0x47bc5)
#7 0x00005dbd7c836cf2 n/a (/usr/bin/ksecretd + 0x47cf2)
#8 0x00005dbd7c834083 n/a (/usr/bin/ksecretd + 0x45083)
#9 0x00005dbd7c8294a6 n/a (/usr/bin/ksecretd + 0x3a4a6)
#10 0x00005dbd7c813d50 n/a (/usr/bin/ksecretd + 0x24d50)
#11 0x00005dbd7c80ceae n/a (/usr/bin/ksecretd + 0x1deae)
#12 0x000079ea2e6376b5 n/a (libc.so.6 + 0x276b5)
#13 0x000079ea2e637769 __libc_start_main (libc.so.6 + 0x27769)
#14 0x00005dbd7c80d945 n/a (/usr/bin/ksecretd + 0x1e945)
Stack trace of thread 164478:
#0 0x000079ea2e726eed syscall (libc.so.6 + 0x116eed)
#1 0x000079ea2edb8c12 _ZN14QMetaCallEventD1Ev (libQt6Core.so.6 + 0x1b8c12)
#2 0x000079ea2edb8c35 _ZN14QMetaCallEventD0Ev (libQt6Core.so.6 + 0x1b8c35)
#3 0x000079ea2ed68505 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x168505)
#4 0x000079ea2f03fcf8 n/a (libQt6Core.so.6 + 0x43fcf8)
#5 0x000079ea2e32c87d n/a (libglib-2.0.so.0 + 0x5e87d)
#6 0x000079ea2e32dcd7 n/a (libglib-2.0.so.0 + 0x5fcd7)
#7 0x000079ea2e32dee5 g_main_context_iteration (libglib-2.0.so.0 + 0x5fee5)
#8 0x000079ea2f03c5e2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x43c5e2)
#9 0x000079ea2ed744b6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1744b6)
#10 0x000079ea2ee873c6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2873c6)
#11 0x000079ea2fe17dae n/a (libQt6DBus.so.6 + 0x37dae)
#12 0x000079ea2ef1ee69 n/a (libQt6Core.so.6 + 0x31ee69)
#13 0x000079ea2e6a57eb n/a (libc.so.6 + 0x957eb)
#14 0x000079ea2e72918c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 164481:
#0 0x000079ea2e6ade22 n/a (libc.so.6 + 0x9de22)
#1 0x000079ea2e6a1fda n/a (libc.so.6 + 0x91fda)
#2 0x000079ea2e6a264c n/a (libc.so.6 + 0x9264c)
#3 0x000079ea2e6a4d1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x000079ea19b5fc5e n/a (libgallium-25.1.5-arch1.1.so + 0x55fc5e)
#5 0x000079ea19b1a23d n/a (libgallium-25.1.5-arch1.1.so + 0x51a23d)
#6 0x000079ea19b5fb8d n/a (libgallium-25.1.5-arch1.1.so + 0x55fb8d)
#7 0x000079ea2e6a57eb n/a (libc.so.6 + 0x957eb)
#8 0x000079ea2e72918c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 164479:
#0 0x000079ea2e6ade22 n/a (libc.so.6 + 0x9de22)
#1 0x000079ea2e6a1fda n/a (libc.so.6 + 0x91fda)
#2 0x000079ea2e6a2024 n/a (libc.so.6 + 0x92024)
#3 0x000079ea2e71c05e __poll (libc.so.6 + 0x10c05e)
#4 0x000079ea2fd6b20b n/a (libxcb.so.1 + 0xd20b)
#5 0x000079ea2fd6cf3d xcb_wait_for_event (libxcb.so.1 + 0xef3d)
#6 0x000079ea2d31e6e9 n/a (libQt6XcbQpa.so.6 + 0x566e9)
#7 0x000079ea2ef1ee69 n/a (libQt6Core.so.6 + 0x31ee69)
#8 0x000079ea2e6a57eb n/a (libc.so.6 + 0x957eb)
#9 0x000079ea2e72918c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 164480:
#0 0x000079ea2e6ade22 n/a (libc.so.6 + 0x9de22)
#1 0x000079ea2e6a1fda n/a (libc.so.6 + 0x91fda)
#2 0x000079ea2e6a264c n/a (libc.so.6 + 0x9264c)
#3 0x000079ea2e6a4d1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x000079ea19b5fc5e n/a (libgallium-25.1.5-arch1.1.so + 0x55fc5e)
#5 0x000079ea19b1a23d n/a (libgallium-25.1.5-arch1.1.so + 0x51a23d)
#6 0x000079ea19b5fb8d n/a (libgallium-25.1.5-arch1.1.so + 0x55fb8d)
#7 0x000079ea2e6a57eb n/a (libc.so.6 + 0x957eb)
#8 0x000079ea2e72918c n/a (libc.so.6 + 0x11918c)
ELF object binary architecture: AMD x86-64
Jul 17 16:01:27 username sudo[238405]: pam_systemd_home(sudo:account): Failed to query user record: Refusing activation, D-Bus is shutting down.
Jul 17 16:01:28 username sudo[238430]: pam_systemd_home(sudo:account): Failed to query user record: Refusing activation, D-Bus is shutting down.
Just wanted to share this in case it is a bug with plasma or kwallet and/or this is effecting other users (could just be that have something setup something wrong somewhere, I transferred to kde from another DE (Budgie) a few years ago so there may be residual dbus files laying round somewhere mucking things up? Not really sure. If there are any additional files or ideas on where to look please share. Also, I wanted to see what other people here thought/whether they have been experiencing something similar. Okay, thanks. 
