Bug 504206

Summary: kwalletd6 crashes every time after log out
Product: [Frameworks and Libraries] frameworks-kwallet Reporter: Christian Gruber <christian_gruber>
Component: generalAssignee: Valentin Rusu <valir>
Status: REPORTED ---    
Severity: crash CC: kde, kdelibs-bugs-null, nate
Priority: NOR    
Version First Reported In: 6.13.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: kwalletd6 core dump info
drkonqi core dump info
plasmashell core dump info on Wayland
drkonqi core dump info on Wayland

Description Christian Gruber 2025-05-14 10:57:02 UTC
Created attachment 181286 [details]
kwalletd6 core dump info

SUMMARY

On my system, the kwalletd6 reproducibly crashes on each log out. This does not happen when I shut down my system without explicitly logging out first. I'm not sure if this is an issue with kwalletd6 or with the logout process. I currently assigned this crash report to the Plasma shell due to its relation to the logout process.

The journal contains the following logs related to kwalletd6:
2025-05-13T23:25:14+02:00 kwalletd6[1197]: The X11 connection broke (error 1). Did the X11 server die?
2025-05-13T23:25:14+02:00 systemd-coredump[5819]: Process 1197 (kwalletd6) of user 1026 terminated abnormally with signal 11/SEGV, processing...
2025-05-13T23:25:15+02:00 drkonqi-coredump-processor[5821]: "/usr/bin/kwalletd6" 1197 "/var/lib/systemd/coredump/core.kwalletd6.1026.ee93e255821a4520abd8760421bd3265.1197.1747171514000000.zst"

Presumably, as a result of this crash, drkonqi also crashes directly after kwalletd6. This is reproducible as well.

The journal contains the following logs related to drkonqui:
2025-05-13T23:25:16+02:00 drkonqi[5837]: qt.qpa.xcb: could not connect to display :0
2025-05-13T23:25:16+02:00 drkonqi[5837]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
2025-05-13T23:25:16+02:00 drkonqi[5837]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
2025-05-13T23:25:16+02:00 drkonqi[5837]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, minimal, minimalegl, vkkhrdisplay, wayland-egl, linuxfb, vnc, offscreen, wayland, xcb.
2025-05-13T23:25:16+02:00 systemd-coredump[5848]: Process 5837 (drkonqi) of user 1026 terminated abnormally with signal 6/ABRT, processing...

Due to the file size limit, I added core dump info only at the moment, but I can also provide the core dumps itself on request.

SOFTWARE/OS VERSIONS

KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.12.25-1-MANJARO (64-bit)
Graphics platform: X11
Comment 1 Christian Gruber 2025-05-14 10:57:45 UTC
Created attachment 181287 [details]
drkonqi core dump info
Comment 2 Nate Graham 2025-05-14 16:42:27 UTC
Can you check to see if this happens in a Wayland session as well? Or does it only happen on X11?
Comment 3 Christian Gruber 2025-05-16 07:22:48 UTC
On Wayland, the Plasma shell crashes instead of kwalletd6.

The journal contains the following logs related to the Plasma shell:
2025-05-15T23:47:55+02:00 systemd-coredump[6105]: Process 1505 (plasmashell) of user 1026 terminated abnormally with signal 11/SEGV, processing...
2025-05-15T23:47:56+02:00 systemd[1138]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
2025-05-15T23:47:57+02:00 drkonqi-coredump-processor[6107]: "/usr/bin/plasmashell" 1505 "/var/lib/systemd/coredump/core.plasmashell.1026.67f57d4e4acd4904946e9d69baf4c418.1505.1747345675000000.zst"
2025-05-15T23:47:56+02:00 systemd[1138]: plasma-plasmashell.service: Failed with result 'core-dump'.

Still, there are some logs related to kwalletd6 in the journal:
2025-05-15T23:47:56+02:00 kwalletd6[1237]: The Wayland connection broke. Did the Wayland compositor die?
2025-05-15T23:47:56+02:00 kwalletd6[1237]: qt.qpa.wayland: Attempting wayland reconnect
2025-05-15T23:47:56+02:00 kwalletd6[1237]: Failed to write to the pipe: Ungültiger Dateideskriptor.
2025-05-15T23:47:56+02:00 kwalletd6[1237]: qt.qpa.wayland: There are no outputs - creating placeholder screen

Once again, as on X11, drkonqi crashes after plasmashell with the following journal logs:
2025-05-15T23:47:57+02:00 drkonqi[6146]: qt.qpa.xcb: could not connect to display
2025-05-15T23:47:57+02:00 drkonqi[6146]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
2025-05-15T23:47:57+02:00 drkonqi[6146]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
2025-05-15T23:47:57+02:00 drkonqi[6146]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, minimal, minimalegl, vkkhrdisplay, wayland-egl, linuxfb, vnc, offscreen, wayland, xcb.
2025-05-15T23:47:57+02:00 hull systemd-coredump[6150]: Process 6146 (drkonqi) of user 1026 terminated abnormally with signal 6/ABRT, processing...

I'll add the core dump infos of the crashes for plasmashell and drkonqi on Wayland.
Comment 4 Christian Gruber 2025-05-16 07:23:45 UTC
Created attachment 181366 [details]
plasmashell core dump info on Wayland
Comment 5 Christian Gruber 2025-05-16 07:24:35 UTC
Created attachment 181367 [details]
drkonqi core dump info on Wayland
Comment 6 Nate Graham 2025-05-16 19:27:41 UTC
Hmm, that looks unrelated. Does that normally happen on Wayland? Or is this your first time using it?
Comment 7 Christian Gruber 2025-05-20 07:04:10 UTC
This may be the first time I've used Wayland on this system. At least I can't remember the last time. I tried to reproduce this crash, but it didn't happen again. So, it is probably unrelated, as you already suspected.
This means that the originally reported crash only occurs on X11.
Comment 8 Bug Janitor Service 2025-06-04 03:48:04 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!