Bug#971760: systemd: Error messages about XDG autostart after logging in as root

[Ma Wo]

Package: systemd
Followup-For: Bug #971760



I just like to add a kind of workaround or solution.
I got 10 error messages per minute because of a check_mk ssh agent monitoring the server.

Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Exec binary 'orca' does not exist: No such file or directory
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Not generating service for XDG autostart app-orca\x2dautostart-autostart.service, error parsing Exec= line: No such file or>
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Exec binary '/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd' does not exist: No such file or directory
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Not generating service for XDG autostart app-kdeconnectd-autostart.service, error parsing Exec= line: No such file or direc>
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Exec binary 'mate-volume-control-applet' does not exist: No such file or directory
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Not generating service for XDG autostart app-mate\x2dvolume\x2dcontrol\x2dapplet-autostart.service, error parsing Exec= lin>
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Exec binary 'displaycal-apply-profiles' does not exist: No such file or directory
Dez 05 19:08:10 hotspot systemd-xdg-autostart-generator[126966]: Not generating service for XDG autostart app-z\x2ddisplaycal\x2dapply\x2dprofiles-autostart.service, error parsing Exec= li>

Currently there are 1,154,537 systemd-xdg-autostart-generator lines in my journal db.

It turned out that the autostart files were leftovers from uninstalled packages, which I removed.
I got rid of the messages by additional purging the packages, which generated the above errors.