When booting into linux I use 2 separate autostart entries for my rgb's (openrgb & artemis) which works most of the time with xorg and never on wayland. With this approach the boot sequence is not properly defined and sometimes gets mixed up in a way where artemis starts before the openrgb server is ready.
Managing openrgb directly would also improve usability greatly as openrgb does not handle resuming from sleep/hibernation at all and forces the user to restart both processes.
When booting into linux I use 2 separate autostart entries for my rgb's (openrgb & artemis) which works most of the time with xorg and never on wayland. With this approach the boot sequence is not properly defined and sometimes gets mixed up in a way where artemis starts before the openrgb server is ready.
I could think of 2 approaches to this issue: