Since I had issues with screen tearing on X (had to do full window re-paints to get the tearing to stop - this only started recently…), I am trying out wayland, which appears to be production-ready.
I am running Tumbleweed, fully zypper duped.
At first, I tried the wayland session by logging out of the X plasma session (system default), then choosing “Plasma (Wayland)” in the sddm session selector, typing my password and thus starting plasma in wayland. This worked perfectly fine, so I thought I could set it as my standard-session for autologin.
In the System Settings, I had changed the Startup and Shutdown -> Login Screen (SDDM) -> Advanced -> Auto Login -> Session value from “(System Default)” to “Plasma (Wayland)”.
As I later had issues, I force-reinstalled sddm, blanked the /etc/sddm.conf and added for testing:
[Autologin] Relogin=false Session=plasmawayland.desktop User=myusername
Before reinstalling sddm, I had additional sections which did not seem to matter - so here for completeness:
[General] HaltCommand= RebootCommand= [Theme] Current=breeze-openSUSE CursorTheme=breeze_cursors [Users] MaximumUid=65000 MinimumUid=1000
journalctl -b shows that sddm reads the .desktop file properly:
Dec 26 22:31:30 felinity sddm: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Dec 26 22:31:30 felinity sddm: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "dbus-run-session /usr/bin/startplasmacompositor"
The compositor is started:
Dec 26 22:31:30 felinity sddm-helper: Starting: "/usr/share/sddm/scripts/wayland-session dbus-run-session /usr/bin/startplasmacompositor" Dec 26 22:31:30 felinity sddm: Session started
At this point, iirc I have X running (for sddm afaik) and I have wayland running, which should show my plasma session.
Instead, however, wayland displays a black screen.
If once I hit Ctrl+Alt+F1(or F2-F6) and back to Ctrl+Alt+F7, then a default cursor is added to the previously visible black screen, but nothing more happens. There is no plasma shell, no windows, no background, and no reaction to clicks.
However, I can log into etc tty2 with my username and manually run dbus-run-session /usr/bin/startplasmacompositor.
This causes a perfect and fully-functional plasma desktop to start up within wayland.
So why can I start a plasma wayland session from sddm (via logout from X → change session in sddm → login again), and also from the terminal (startplasmacompositor) – but only for autologin it does not work? Is there any race condition? What is happening / what is missing? It looks like the compositor is starting just fine, but kwin & plasma are missing.
Side Note: when /etc/sddm.conf is entirely blank, then an autologin is done into an X session just fine. Only for wayland I could not find any way to make it work.
Thank you so much for your help!