I just installed a fresh version of galileo on my laptop and cannot get wayland to work.
When I select wayland in the login screen and try and log in it goes to a blinking curser at the top left for 5 seconds, then it goes straight back to the login screen. When I select X11 it works like normal though.
System specs:
GPD Win Max 2 laptop with 6800u cpu and integrated gpu.
Holidays here. Downloaded the latest ISO, chose KDE offline (as I am about to switch from Gnome anyway) and installed `plasma-wayland-session. The Wayland session can’t be started from SDDM with the exact same behaviour as described by @icedigger
Intel integrated GPU here. Never had issues with Wayland from Gnome or KDE in the past.
If I select a different display manager like GDM, starting the Wayland Plasma session works.
If I CTRL-ALT-F3 into VT3 and run startplasma-wayland the Wayland session also works.
So it’s SDDM which can’t start a Wayland Plasma session.
So two weeks later no update for sddm and still no way to start wayland from sddm. How can I report bugs upstream? I do not even know where the error message as why the session fails to start can be collected.
Hero of the day! I commented out startx and now I can start buttery smooth from sddm without the crutch Ctrl-Alt-F3, login on the terminal and executing startplasma-wayland
Seems like a packaging issue then worth to be tackled? I genuinely wonder why no one else stumbled into that issue.
It has been fixed for the next ISO. The issue was a wrong config file was copied to the target when installing offline. X11 worked OK but wayland didn’t.