https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285309
--- Comment #5 from groenv...@acm.org --- (In reply to groenveld from comment #4) $ dbus-launch ck-launch-session startplasma-wayland And below is the stdout and stderr upon KDE logout which corresponds to the core dumps. John groenv...@acm.org org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. qt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: xcb, vnc, offscreen, wayland-egl, minimal, vkkhrdisplay, wayland. kf.baloo: Extractor crashed Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. qt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin. qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: xcb, vnc, offscreen, wayland-egl, minimal, vkkhrdisplay, wayland. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
