cachy-update tweak should be enabled via XDG autostart

[eggroll-bot]

In Antiz96/arch-update#599, we see that when using KDE Plasma, there can be a race condition on log out, such that the service is stopped too late, resulting in repeated crashes of arch-update-tray. The workaround is to use XDG autostart to start arch-update-tray on login: Antiz96/arch-update#599 (comment).

CachyOS Hello should be tweaked, such that it uses XDG autostart to enable arch-update-tray, instead of the user service.

[vnepogodin]

usage of autostart entries breaks systemd mechanism

[eggroll-bot]

usage of autostart entries breaks systemd mechanism

I'm not sure I follow. My understanding is that either systemd or autostart entry can be used to enable cachy-update (with only one being allowed at a time). What is the issue with using autostart over systemd here?

[Antiz96]

Hi 👋

Just passing by to give some details and opinions 😄

My understanding is that either systemd or autostart entry can be used to enable cachy-update (with only one being allowed at a time)

Just for precision: technically you can do both at the same time, there's a safeguard which checks if the applet is already started. So whichever runs first will start the systray applet, the second one will fail stating that the systray applet is already started.
For what it's worth, Cachy-Update used to (indirectly) set both the systemd service and XDG autostart for some historical reasons but this was reverted since then.

What is the issue with using autostart over systemd here?

Not every graphical environments are guaranteed to support (or work well with) XDG autostart. It's the case for a fair amount of WM & Wayland compositors, such as Sway for instance, among others (although, one could argue WM users should autostart processes via their conf file I guess 😝). That's why I also offered a systemd service as a fallback option.

That being said, as written above, the systemd service is considered a fallback option for the few cases where XDG autostart is not suitable / supported. From an Arch-Update point of view, XDG Autostart is still documented as the preferred method:

I'm not saying that the issue reported in Antiz96/arch-update#599 should be expected when using the systemd service though, but Arch-Update recommends XDG autostart on that front for a reason (I will update the documentation to emphasize on that) 😅

Ultimately, it kinda depend if CachyOS cares about autostarting the Cachy-Update systray applet by default on every supported graphical environments (including standalone windows managers and Wayland compositors; in case starting it from their respective configuration file is not an option) or if it only cares about the flagship KDE & Gnome options on that front. If the latter, then switching to XDG autostart should be considered IMO 😸