Sorry. but rani function not well.
Special if you deactivate a service. Yes, the service is “dead”
But if you take after a look inside /etc/systemd/… the folder/files/ special dead links exists and journal is flooted with “errors.”
Example power profile daemon..“flooded” my journal about this.
Apr 02 22:08:24 garudacomp (s-daemon)[6433]: power-profiles-daemon.service: Unable to locate executable '/usr/libexe>
Apr 02 22:08:24 garudacomp (s-daemon)[6433]: power-profiles-daemon.service: Failed at step EXEC spawning /usr/libexe>
Apr 02 22:08:24 garudacomp systemd[1]: power-profiles-daemon.service: Main process exited, code=exited, status=203/E>
Apr 02 22:08:24 garudacomp systemd[1]: power-profiles-daemon.service: Failed with result 'exit-code'.
Apr 02 22:08:24 garudacomp systemd[1]: Failed to start Power Profiles daemon.
Apr 02 22:08:24 garudacomp plasmashell[5904]: qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to Pr>
Apr 02 22:08:24 garudacomp systemd[5170]: Started Xdg Desktop Portal For KDE.
Apr 02 22:08:24 garudacomp systemd[5170]: Started Portal service.
Apr 02 22:08:24 garudacomp systemd[1]: power-profiles-daemon.service: Scheduled restart job immediately on client re>
Apr 02 22:08:24 garudacomp systemd[1]: power-profiles-daemon.service: Start request repeated too quickly.
Apr 02 22:08:24 garudacomp systemd[1]: power-profiles-daemon.service: Failed with result 'exit-code'.
Apr 02 22:08:24 garudacomp systemd[1]: Failed to start Power Profiles daemon.
i delete by hand inside systemd the “dead” link and all is fine. Perhaps i have only this issue..but, rani ..for me is " under construction "
If i do this all over " Garuda Wellcome… all fine.