*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY After an upgrade from KDE 6.4.X to KDE 6.5.0 plasmashell crashed and no panels are available STEPS TO REPRODUCE 1. Use i3 wm as a window manager 2. 3. OBSERVED RESULT plasma shell crashes and I cannot even collect bug report as reported also crashes. When I try to run plasmashell -v , I get this plasmashell -v qt.qpa.xcb: could not connect to display 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: offscreen, vnc, xcb, minimal, wayland-brcm, wayland-egl, wayland, minimalegl, linuxfb, eglfs, vkkhrdisplay. [1] 7249 IOT instruction (core dumped) plasmashell -v EXPECTED RESULT All panels should be working and available SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch/KDE+i3wm KDE Plasma Version: 6.5.0 KDE Frameworks Version: Qt Version: qmake --version; QMake version 3.1; Using Qt version 5.15.17 in /usr/lib ADDITIONAL INFORMATION
Your setup is unfortunately not supported. The error means that Qt failed to find the xserver though, so probably something is wrong with your environment.
*** Bug 511428 has been marked as a duplicate of this bug. ***
(In reply to Harald Sitter from comment #1) > Your setup is unfortunately not supported. The error means that Qt failed to > find the xserver though, so probably something is wrong with your > environment. How is not supported? Plama has supported using a different WM for ages. The two bugs are unrelated as the underlying cause for bug is a different one. Yes both happen to be when using i3 but the crash is different.