https://bugzilla.suse.com/show_bug.cgi?id=1227068 https://bugzilla.suse.com/show_bug.cgi?id=1227068#c12 Tobias Burnus <burnus@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(burnus@gmx.de) | --- Comment #12 from Tobias Burnus <burnus@gmx.de> --- (In reply to Stefan Dirsch from comment #11)
You're not really using X11 and Wayland at the same time, do you? I wouldn't know how to configure this - let a lone support it ...
Well, in terms of user handling – I choose either '<Plasma|GNOME> (Wayland)' or '<Plasma|GNOME> (X11)', i.e. in that sense I only use one at a time. I was using "Plasma (Wayland)" before – and that stopped working → reason for opening this bug report. However, after it failed (eDP screen dark), I started playing around with "(X11)" instead of "(Wayland)" on the login screen and with "GNOME (Wayland)" to see whether it was a KDE/Qt library problem or a more generic one. * * * However: My impression is that the KDM uses X11 – when choosing X11, that virtual screen is also used for that purpose (virtual terminal/screen 2, i.e. what you reach via [Alt][Ctrl][F2]). Whereas when choosing Wayland, the KDM remains waiting on screen 2 state and Wayland is spawn on screen 3 ([Alt][Ctrl][F3]). But I have no idea of the inner workings of KDM/GDM/XDM nor of the current setup. * * * I wrote the following morning but it didn't came through as we had a comment-adding clash and I didn't see it as I moved to a different tab after hitting "Save Changes":
After applying today's updates to MESA (24.1.2-382; Linux kernel 6.9.6, systemd, …):
Wayland now works again. :-)
(plasmashell crashes (+ restarts) when plugging the HDMI cable, segfaulting in some libQt6Wayland*.so file but that's unrelated and doesn't block working.) -- You are receiving this mail because: You are on the CC list for the bug.