I think I've found a race condition issue. When using the systemd service config provided in the README, occasionally some apps autostarted by Plasma (instead of i3) fail to start (or hang for a while) due to expecting certain things to be available which were not available when initialized. For example, Carla has trouble opening one of my sound cards with the specified configuration. Every time this happens, I notice that some taskbar icons are on my Polybar, rather than being on the Plasma bar that I keep on my main monitor. I changed the i3 service to use After=plasma-workspace.target instead of Before=plasma-workspace.target and this issue has since disappeared. I sometimes need to restart i3 once with Mod+Shift+R after boot to get Polybar to behave as expected, but otherwise this has been a massive improvement for my daily use.
So, I'm curious why Before was chosen and if there are any objective reasons why one should be used over the other in this case.
I think I've found a race condition issue. When using the systemd service config provided in the README, occasionally some apps autostarted by Plasma (instead of i3) fail to start (or hang for a while) due to expecting certain things to be available which were not available when initialized. For example, Carla has trouble opening one of my sound cards with the specified configuration. Every time this happens, I notice that some taskbar icons are on my Polybar, rather than being on the Plasma bar that I keep on my main monitor. I changed the i3 service to use
After=plasma-workspace.targetinstead ofBefore=plasma-workspace.targetand this issue has since disappeared. I sometimes need to restart i3 once with Mod+Shift+R after boot to get Polybar to behave as expected, but otherwise this has been a massive improvement for my daily use.So, I'm curious why
Beforewas chosen and if there are any objective reasons why one should be used over the other in this case.