I was running updates and after that I could not logon to my sway “desktop” anymore. Worked fine with i3 and bspwm. Using lightdm.
Today I changed to sddm and now I can login to my sway “desktop” again. I havent testie this more than just replicating the same problem on another laptop aswell.
? You’re saying you can’t switch to TTY with Ctrl+Alt+F2 for example?
There is some ugly workaround to get it working by delaying the startup of sway with lightdm.
(I had to use this nasty trick to get external keyboard and mouse working properly: https://github.com/canonical/lightdm/issues/63#issuecomment-671046962).
Apparently it also helps for the “fallback to lightdm login screen issue”
#!/bin/sh
# btw, here is also a good place if you also use other DE/WM's next to sway
# and you want to set specific env vars that are only needed for sway / wayland sessions
# e.g. "export MOZ_ENABLE_WAYLAND=1" and things like that...
sleep 2
exec /usr/bin/sway
Make it executable: sudo chmod +x /usr/local/bin/start-sway
Create another wayland session file pointing to the script: /usr/share/wayland-sessions/sway-fix.desktop
Content
[Desktop Entry]
Name=Sway (start-fix)
Comment=An i3-compatible Wayland compositor
Exec=/usr/local/bin/start-sway
Type=Application
this login ligthdm access error still persists in EOS Apollo sway community edition… I can prove it. Please consider change display manager to correct it