kanshi profiles don't get applied on first load

[SoumyaRanjanPatnaik]

kanshi fails to apply output profiles at the start of the session if it is executed from the sway configuration. This creates the illusion that the display settings don't persist and require reconfiguration to restore expected behaviour. For context, regolith-displayd generates kanshi profiles that automatically configure displays based on the connected outputs on hotplug.

Killing and restarting 'kanshi` leads to the successful application of the profiles. Reloading the configurations for the sway session already does this and can be used as a temporary workaround until this issue is resolved. regolith-linux/sway-regolith/issues/26 also describes the same problem.

Looking into the logs, I see the following error.

 failed to apply configuration for profile.

I looked at the code for kanshi; this error only happens when the Wayland server fails to apply the configurations requested.

Starting kanshi manually AFTER sway starts applies the profiles correctly.

My initial thought was sway v1.9 might have introduced some changes that led to a race condition between config parsing and the Wayland server startup. However, delaying the startup of kanshi by adding a timeout using sleep doesn't fix the issue so I'm not too sure.

@kgilmer let me know if you have any thoughts. This is most certainly a blocker for the stabilisation of the sway session with this release.

[kgilmer]

Hmm, not having looked in detail, I don't have anything off the top of my head.

Starting kanshi manually AFTER sway starts applies the profiles correctly.

Could we just do some systemd configuration such that this happens, or is there a downside?