Christian Stritzke

It started up fine for me after I masked thunar.service ```systemctl --user mask thunar.service``` But damn, what a debug session :D

Rebooted twice and it's working flawlessly. Seems like you have something else that causes a timeout, though. Nothing to mask if there is no thunar installed.

Running ```systemctl --user | grep start``` right after you start sway may help. This should show you services that take a long time to start. My dear thunar service did...

Huh, masking thunar.service didn't work on my other machine. Very niche solution then...

> I thought the file manager API might be involved, especially since there's been mentions of both `nemo` and `thunar` being related. Can confirm. Uninstalling nemo made it work for...