Connection of external display (TV) forces/crashes back to login screen

English Install/Boot/Login
,
1

AMD CPU and dGPU.

Today I’ve been forced to use X11 (ew) because I’m suddenly – after an update yesterday I presume – unable to log into a Wayland session with an external display connected. In fact, I only definitely made this connection after disconnecting the HDMI cable and then being able to use Wayland without issue, only to be forced back/crash back into the login screen after connecting the cable again.

I did find the following in /home/user/.local/share/sddm/wayland-session.log:

Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
1 Like
2

There’s this for now 494941 – Cannot enter the Wayland session (kde.org)

Maybe you can register and set it as you’re affected too

1 Like
3

Hi again,

While waiting for someone or any divine creature to help, do you have a laptop or a normal PC?

For laptops, I’ve found out that GNU/Linux handles differently the situation depending on the port. While I’m certain that something is wrong in KDE or on Tumbleweed (because on any other Windows or Linux distro, with Plasma, everything works), I’ve managed to workaround the issue by plugging the DisplayPort cable to another port of my laptop.

However, performance are much worse while browsing for unclear reasons.

4

It’s a gaming laptop, but since I connect to a TV my only option is HDMI, and there’s only one port.

Since I see some updates now, I’m going to reboot, and if it still doesn’t work I’ll attach logs to the bug report.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.