Can't Start Sway Twice

[ibrokemypie]

The first time after booting my system I am able to log in to sway just fine through lemurs.
After I exit sway and then attempt to log back in through lemurs it now doesn't work.
If I switch to another tty and attempt to run sway it now also doesn't work, however if I unset DISPLAY and WAYLAND_DISPLAY first, then I can launch sway again.

I have scoured my config and the internet for any reason why DISPLAY and WAYLAND_DISPLAY get set at first launch of sway and not un-set at logout, since it appears that they prevent sway from launching when they are present, and haven't been able to find anything other than arch's 50-systemd-user.conf file provided with the sway package, which imports DISPLAY and WAYLAND_DISPLAY (among others) into the systemd environment (https://gitlab.archlinux.org/archlinux/packaging/packages/sway/-/blob/main/50-systemd-user.conf?ref_type=heads)

Not sure if this is a lemurs issue not handling this situation, or an arch one for not unsetting them on exit, so I am opening an issue here to start the process of finding out where it needs to be fixed.

[coastalwhite]

Heya!

Thank you for the issue report and doing some the investigate work already.

Currently, lemurs doesn't really handle the WAYLAND_DISPLAY environment variable. We unset the DISPLAY variable. We don't yet do the same with WAYLAND_DISPLAY.

Overal, this issue seems very similar to fairyglade/ly#205. That issue also talks about some other environment variables.

[ibrokemypie]

Hmm well I am definitely not running sway as a systemd service as they are over in that ly issue, so those suggestions unfortunately don't work for me. Should lemurs handle WAYLAND_DISPLAY as well then if it is already handling DISPLAY?

[JeromeSchmied]

same here