Plasma not staring under wayland (but it does in X11)

Help
, ,
1

From a prior update I lost the ability to start plasma in wayland mode.
The login manager works, and I can log in to a X11 session, but if I choose wayland the screen goes black, and then it returns to the login manager.

I hoped that it would fix itself with the update to 6.4, but it hasn’t been the case.

I’m running a KDE slimbook, with KDE Neon, and the only information I’ve been able to get related to this issue is the following segfault:

[  198.678569] kwin_wayland[4267]: segfault at 0 ip 00007bbcf4cda465 sp 00007ffc04c82fa0 error 4 in libQt6Gui.so.6.9.0[2d9465,7bbcf4c51000+62f000] likely on CPU 0 (core 0, socket 0)
[  198.678579] Code: 89 e5 41 54 53 48 8d 5d c0 48 89 df 48 83 ec 30 4c 8b 25 be fb 5b 00 64 48 8b 04 25 28 00 00 00 48 89 45 e8 31 c0 49 8b 34 24 <48> 8b 06 ff 50 60 31 f6 48 89 df e8 9b 90 f7 ff 48 89 df 89 05 be

any help would be much appreciated
Best regards

Asier

2

Can you post (or create a bug report) with the backtrace ( Guidelines and HOWTOs/Debugging/How to create useful crash reports - KDE Community Wiki)

What GPU do you have?

Does Wayland start using a new user?

3

I can’t create the backtrace, if I use coredumpctl --reverse it says that there is no coredump.
And as it happens in the login screen, I don’t know how to get the information. The one I got was from dmesg.

It happens with a new user too.

The GPU is an intel integrated one:
VGA compatible controller: Intel Corporation HD Graphics 620

4

Hi! I’m new to Linux,but I’ve fighting this problem all day and I think I ended up fixing it. I had the same problem in a Lenovo Z50-70 with an Intel Graphics+Nvidia card and Arch.

Do you have an Nvidia card also? Can you log in with another TTY instead of your usual login screen and try $ startplasma-wayland?

5

Hello,

The GPU is an intel integrated one:
VGA compatible controller: Intel Corporation HD Graphics 620

I’ve tried startplasma-wayland on another TTY, but id doesn’t work. I presume that it has something to do with having the login screen in the other TTY

$ startplasma-wayland
Error: could not determine $DISPLAY
Error: Can not contact kdeinit5!
org.kde.startup: "deinit5_shutdown" QList() exited with code 255

In fact, It doesn’t work with startplasma-x11 either.

$ startplasma-x11
$DISPLAY is not set or cannot connect to the x server
6

Hello,

I’ve been trying different things with no success.
I run from a tty (while having the X11 session in other):
sudo dbus-run-session startplasma-wayland

And I got:

dbus-daemon[11520]: [session uid=1000 pid=11520] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[11520]: [session uid=1000 pid=11520] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.4' (uid=1000 pid=11555 comm="/usr/bin/kcminit_startup" label="unconfined")
dbus-daemon[11520]: [session uid=1000 pid=11520] Activating service name='org.freedesktop.portal.Documents' requested by ':1.5' (uid=1000 pid=11558 comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
dbus-daemon[11520]: [session uid=1000 pid=11520] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.6' (uid=1000 pid=11564 comm="/usr/libexec/xdg-document-portal" label="unconfined")
dbus-daemon[11520]: [session uid=1000 pid=11520] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
dbus-daemon[11520]: [session uid=1000 pid=11520] Successfully activated service 'org.freedesktop.portal.Documents'
fusermount3: failed to access mountpoint /run/user/1000/doc: Permission denied
error: fuse init failed: Can't mount path /run/user/1000/doc

(/usr/libexec/xdg-desktop-portal:11558): xdg-desktop-portal-WARNING **: 13:31:07.936: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback

(/usr/libexec/xdg-desktop-portal:11558): xdg-desktop-portal-WARNING **: 13:31:07.936: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
dbus-daemon[11520]: [session uid=1000 pid=11520] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.5' (uid=1000 pid=11558 comm="/usr/libexec/xdg-desktop-portal" label="unconfined")

(xdg-desktop-portal-gtk:11580): Gtk-WARNING **: 13:31:08.937: cannot open display: :1
qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
qt.qpa.wayland: Loading shell integration failed.
qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
dbus-daemon[11520]: [session uid=1000 pid=11520] Activated service 'org.freedesktop.impl.portal.desktop.gtk' failed: Process org.freedesktop.impl.portal.desktop.gtk exited with status 1
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
dbus-daemon[11520]: [session uid=1000 pid=11520] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=11521 comm="startplasma-wayland" label="unconfined")
dbus-daemon[11520]: [session uid=1000 pid=11520] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.

Maybe it has something to do with the shells, but I don’t know how to fix that.
Also, it confuses me having some GTK related warnings.