https://bugs.kde.org/show_bug.cgi?id=514326
--- Comment #8 from Christian Hacker <[email protected]> --- It appears that the X11 display :0 was not accessible to drkonqi and kded6 at the time(s) when ksecretd had it's corefile dumped. The drkonqi and kded6 log messages from the times of the SIGABRT coredumps below are given here. The Kde desktop screen was locked by the user at that time; with the external display switched off. The Kde user was already logged out, or may have been in the process of logging out of the desktop, at the times of the other instances of this problem. However, shouldn't specifically in the case of the locked Kde desktop a X11 display :0 be available for applications? If this is a security issue in connection with the crashed ksecretd, can drkonqi be made to safely recover it's operation? What is the policy for drkonqi for the cases when the user is either logged out, or when the Kde screen is locked (for a longer timespan)? Would it make sense to have drkonqi generate some desktop Notifications for later use? See Bug 514443 (drkonqi writes SIGABRT corefile after ksecretd crashes) Like chris@suse8:~/tmp $> coredumpctl --reverse TIME PID UID GID SIG COREFILE EXE SIZE Wed 2026-01-07 23:12:10 CET 47957 1000 1000 SIGABRT present /usr/bin/kded6 493.8K Wed 2026-01-07 23:12:08 CET 47846 1000 1000 SIGABRT present /usr/libexec/drkonqi 937.4K Wed 2026-01-07 23:12:08 CET 6673 1000 1000 SIGSEGV present /usr/bin/ksecretd 4.4M Like 7 Jan 2026 23:12:08 drkonqi could not connect to display :0 7 Jan 2026 23:12:08 drkonqi From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. 7 Jan 2026 23:12:08 drkonqi Could not load the Qt platform plugin "xcb" in "" even though it was found. 7 Jan 2026 23:12:08 drkonqi 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, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb. Like 7 Jan 2026 23:12:10 kded6 Authorization required, but no authorization protocol specified 7 Jan 2026 23:12:10 kded6 Authorization required, but no authorization protocol specified 7 Jan 2026 23:12:10 kded6 could not connect to display :0 7 Jan 2026 23:12:10 kded6 From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. 7 Jan 2026 23:12:10 kded6 Could not load the Qt platform plugin "xcb" in "" even though it was found. 7 Jan 2026 23:12:10 kded6 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, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb. Bye -- You are receiving this mail because: You are watching all bug changes.
