SUMMARY Running on Neon (jammy stable) rebooting the system after a couple of weeks with no reboot, and with Plasma fully up to date on Neon stable, at 6.1.5, after a reboot cannot log in to Plasma on Wayland - after logging in the screen blinks a few times and we are left with a black screen and a mouse cursor. There is no "KDE neon is loading" animation. Looking at the logs from the plasma-plasmashell user service, we get this: Sep 13 23:27:25 thunderbird systemd[898]: Starting KDE Plasma Workspace... Sep 13 23:27:25 thunderbird plasmashell[1374]: warning: queue 0x57ebb8fe2820 destroyed while proxies still attached: Sep 13 23:27:25 thunderbird plasmashell[1374]: wl_registry@34 still attached Sep 13 23:27:25 thunderbird systemd[898]: Started KDE Plasma Workspace. Sep 13 23:27:25 thunderbird plasmashell[1374]: kf.plasma.quick: Applet preload policy set to 1 Sep 13 23:27:25 thunderbird plasmashell[1374]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:195:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" Sep 13 23:27:25 thunderbird plasmashell[1374]: Toolbox not loading, toolbox package is either invalid or disabled. Sep 13 23:27:26 thunderbird kwin_wayland_wrapper[952]: error in client communication (pid 1374) Sep 13 23:27:26 thunderbird plasmashell[1374]: [destroyed object]: error 7: importing the supplied dmabufs failed Sep 13 23:27:26 thunderbird plasmashell[1374]: The Wayland connection broke. Did the Wayland compositor die? Sep 13 23:27:26 thunderbird kioworker[1385]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError Sep 13 23:27:26 thunderbird kioworker[1385]: kf.kio.core: An error occurred during write. The worker terminates now. Sep 13 23:27:26 thunderbird systemd[898]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION Sep 13 23:27:26 thunderbird systemd[898]: plasma-plasmashell.service: Failed with result 'exit-code'. Restarting the shell in X11 works fine. SOFTWARE/OS VERSIONS This is kinfo report from the X11 session: Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION This is a Nvidia Optimus device with the nvidia proprietary drivers installed: $ lspci -k ... 01:00.0 3D controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2) Subsystem: Dell GM107GLM [Quadro M1200 Mobile] Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia ... I'm not sure if this is related, but IIUC the "dmabuf" suggests so.
There were no DrKonqi alerts at any point. I can run any test that you think is relevant.
"error 7: importing the supplied dmabufs failed" seems very relevant. As well as "The Wayland connection broke. Did the Wayland compositor die?" My guess is that KWin exited with a Wayland protocol error or something and this blocked plasmashell's launch when it tried to connect to the compositor.
I've seen this before; it happens when plasmashell gets started on the NVidia GPU - and the driver creates buffers that are incompatible with the internal GPU that KWin is using (or plasmashell on the integrated, KWin on the dedicated one). It's a driver bug that indeed kills the app. Do you have any driver related environment variables set that might be causing plasmashell to run on the non-default GPU?
(In reply to Zamundaaa from comment #3) > Do you have any driver related environment variables set that might be > causing plasmashell to run on the non-default GPU? Not that I know of - how would I check? The system environment files (/etc/environment*) do not have any of the __NV_PRIME_RENDER_OFFLOAD or its adjacent environment variables. This used to work and stopped working after a Plasma update and reboot.
🐛🧹 ⚠️ 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!
I'm not entirely sure, but afaict eglinfo shows which GPU a Wayland app would use
After rebooting the installation on new hardware - also a Dell XPS Optimus setup (the installation was temporarily on the i7-7820HQ setup while the original hardware was in the shop for a keyboard replacement), we can no longer reproduce the issue on Neon stable w/ Plasma Wayland 6.1.5. The i7-7820HQ hardware is now running Neon unstable Plasma 6.2 beta - also without issues. 🤷