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

[Kurt Roeckx]

Package: systemd
Version: 246.6-1

Hi,

After I log in as root on the console, I get the following message
on the console:
[ 75.568505] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gsettings\x2ddata\x2dconvert-autostart.service, startup phases are not supported.
[ 75.568579] systemd-xdg-autostart-generator[1481]: Exec binary '/usr/lib/gnome-volume-manager/gnome-volume-manager' does not exist: No such file or directory
[ 75.568629] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dvolume\x2dmanager-autostart.service, error parsing Exec= line: No such file or directory
[ 75.568693] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported.
[ 75.568828] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported.
[ 75.568883] systemd-xdg-autostart-generator[1481]: Exec binary '/usr/sbin/restorecond' does not exist: No such file or directory
[ 75.568925] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-restorecond-autostart.service, error parsing Exec= line: No such file or directory
[ 75.569013] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported.
[ 75.569078] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-xscreensaver-autostart.service, could not find TryExec= binary xscreensaver: No such file or directory
[ 75.569252] systemd-xdg-autostart-generator[1481]: Exec binary 'gcm-apply' does not exist: No such file or directory
[ 75.569292] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gcm\x2dapply-autostart.service, error parsing Exec= line: No such file or directory
[ 75.569352] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported.
[ 75.569431] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported.

That is, it also got logged by the kernel, is shown on the screen, ans is logged twice. journalctl shows:
Oct 06 18:43:51 intrepid systemd[1]: Created slice User Slice of UID 0.
Oct 06 18:43:51 intrepid systemd[1]: Starting User Runtime Directory /run/user/0...
Oct 06 18:43:51 intrepid systemd-logind[829]: New session 4 of user root.
Oct 06 18:43:51 intrepid systemd[1]: Finished User Runtime Directory /run/user/0.
Oct 06 18:43:51 intrepid systemd[1]: Starting User Manager for UID 0...
Oct 06 18:43:51 intrepid systemd[1468]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gsettings\x2ddata\x2dconvert-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Exec binary '/usr/lib/gnome-volume-manager/gnome-volume-manager' does not exist: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dvolume\x2dmanager-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Exec binary '/usr/sbin/restorecond' does not exist: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-restorecond-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-xscreensaver-autostart.service, could not find TryExec= binary xscreensaver: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Exec binary 'gcm-apply' does not exist: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gcm\x2dapply-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.568505] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gsettings\x2ddata\x2dconvert-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.568579] systemd-xdg-autostart-generator[1481]: Exec binary '/usr/lib/gnome-volume-manager/gnome-volume-manager' does not exist: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <28>[ 75.568629] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dvolume\x2dmanager-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.568693] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.568828] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.568883] systemd-xdg-autostart-generator[1481]: Exec binary '/usr/sbin/restorecond' does not exist: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <28>[ 75.568925] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-restorecond-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.569013] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.569078] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-xscreensaver-autostart.service, could not find TryExec= binary xscreensaver: No such file or direc>
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.569252] systemd-xdg-autostart-generator[1481]: Exec binary 'gcm-apply' does not exist: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <28>[ 75.569292] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gcm\x2dapply-autostart.service, error parsing Exec= line: No such file or directory
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.569352] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported.
Oct 06 18:43:51 intrepid kernel[867]: <30>[ 75.569431] systemd-xdg-autostart-generator[1481]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported.

If I log in as a different user, I do not get those messages, not even in the log file.

I find it weird that something is run when logging in as user root
that doesn't seem to be run as a normal user.


Kurt

[Michael Biebl]

Control: tags -1 + moreinfo

Is this a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968116 ?

[Kurt Roeckx]

Post by Michael Biebl
Control: tags -1 + moreinfo
Is this a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968116 ?

I looked at that, and at first sight it looked like something
else.


Kurt

[Kurt Roeckx]

Post by Kurt Roeckx

Post by Michael Biebl
Control: tags -1 + moreinfo
Is this a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968116 ?

I looked at that, and at first sight it looked like something
else.

Ok, can you tell me, what the expected behaviour is then.
Is this bug report about the log messages, where they end up, something
else?

What I all mentioned in my initial email:
- It gets logged to the kernel and console. It should not do that.
This gives the impression that there is something seriously
wrong.
- It should not behave differently when logging in as root vs an
other user.


Kurt

[Kurt Roeckx]

Post by Kurt Roeckx
- It gets logged to the kernel and console.

I can't reproduce that. Do you have some custom syslog configuration?

Not as far as I know.


Kurt

[Kurt Roeckx]

Post by Kurt Roeckx
- It gets logged to the kernel and console.

I can't reproduce that. Do you have some custom syslog configuration?

I only seem to get it the first time I log in as root.


Kurt

[Kurt Roeckx]

Post by Kurt Roeckx

Post by Kurt Roeckx
- It gets logged to the kernel and console.

I can't reproduce that. Do you have some custom syslog configuration?

I only seem to get it the first time I log in as root.

I still have trouble reproducing the issue of getting those log messages
on the console.
What kind of syslogger are you using? Can you share the complete syslog
config?

I'm using sysklogd.

I've attached /etc/syslog.conf

/etc/default/syslogd contains:
#
# Top configuration file for syslogd
#

#
# Full documentation of possible arguments are found in the manpage
# syslogd(8).
#

#
# For remote UDP logging use SYSLOGD="-r"
#
SYSLOGD=""

[Kurt Roeckx]

Hi Kurt

Post by Kurt Roeckx

Post by Kurt Roeckx

Post by Kurt Roeckx
- It gets logged to the kernel and console.

I can't reproduce that. Do you have some custom syslog
configuration?

I only seem to get it the first time I log in as root.

I still have trouble reproducing the issue of getting those log messages
on the console.
What kind of syslogger are you using? Can you share the complete syslog
config?

I'm using sysklogd.

Given that sysklogd is no longer supported and available in the archive
since a few releases, I'm unable to reproduce the issue concerning the
error messages you get on the console.
The error messages themselves have been tweaked significantly in 246.6-
2. See [1].
Thus closing this issue.
If you still get (unexpected) warning messages on the console with a
default Debian system using rsyslog, please reopen.

I guess I still have sysklogd installed from when that was the
default. I'll switch to rsyslog, and let you know on the next
reboot.


Kurt

[Kurt Roeckx]

reopen 971760
thanks

Post by Kurt Roeckx
I'm using sysklogd.

Given that sysklogd is no longer supported and available in the archive
since a few releases, I'm unable to reproduce the issue concerning the
error messages you get on the console.

So I've changed it to rsyslogd, default configuration.

The error messages themselves have been tweaked significantly in
246.6-
2. See [1].

I've also installed 246.6-2

I still have the same issue:
[ 62.379826] systemd-xdg-autostart-generator[1423]: Exec binary '/usr/lib/gnome-volume-manager/gnome-volume-manager' does not exist: No such file or directory
[ 62.379893] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-gnome\x2dvolume\x2dmanager-autostart.service, error parsing Exec= line: No such file or directory
[ 62.379965] systemd-xdg-autostart-generator[1423]: Exec binary '/usr/sbin/restorecond' does not exist: No such file or directory
[ 62.380008] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-restorecond-autostart.service, error parsing Exec= line: No such file or directory
[ 62.380179] systemd-xdg-autostart-generator[1423]: Exec binary 'gcm-apply' does not exist: No such file or directory
[ 62.380221] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-gcm\x2dapply-autostart.service, error parsing Exec= line: No such file or directory


Kurt

[Michael Biebl]

Post by Kurt Roeckx
reopen 971760
thanks

Post by Kurt Roeckx
I'm using sysklogd.

Given that sysklogd is no longer supported and available in the archive
since a few releases, I'm unable to reproduce the issue concerning the
error messages you get on the console.

So I've changed it to rsyslogd, default configuration.

The error messages themselves have been tweaked significantly in
246.6-
2. See [1].

I've also installed 246.6-2
[ 62.379826] systemd-xdg-autostart-generator[1423]: Exec binary '/usr/lib/gnome-volume-manager/gnome-volume-manager' does not exist: No such file or directory
[ 62.379893] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-gnome\x2dvolume\x2dmanager-autostart.service, error parsing Exec= line: No such file or directory
[ 62.379965] systemd-xdg-autostart-generator[1423]: Exec binary '/usr/sbin/restorecond' does not exist: No such file or directory
[ 62.380008] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-restorecond-autostart.service, error parsing Exec= line: No such file or directory
[ 62.380179] systemd-xdg-autostart-generator[1423]: Exec binary 'gcm-apply' does not exist: No such file or directory
[ 62.380221] systemd-xdg-autostart-generator[1423]: Not generating service for XDG autostart app-gcm\x2dapply-autostart.service, error parsing Exec= line: No such file or directory

Those appear to be valid errors: autostart files which reference
non-existing binaries.

You also mentioned, that this was logged directly to the console,
instead of just ending up in the journal, is this still the case?

[Kurt Roeckx]

You also mentioned, that this was logged directly to the console, instead of
just ending up in the journal, is this still the case?

Yes.


Kurt

[Michael Biebl]

You also mentioned, that this was logged directly to the console, instead of
just ending up in the journal, is this still the case?

Yes.

Can you attach the output of
cat /proc/cmdline
journalctl -alb
reportbug --template systemd
to this bug report please.

[Kurt Roeckx]

Post by Michael Biebl

You also mentioned, that this was logged directly to the console, instead of
just ending up in the journal, is this still the case?

Yes.

Can you attach the output of
cat /proc/cmdline
journalctl -alb
reportbug --template systemd

Those files contain various private information I do not wish to,
send to the bug report, and I do not want to look at all 80K lines
to see what I need to redact.


Kurt

[Michael Biebl]

Post by Michael Biebl

Post by Michael Biebl
You also mentioned, that this was logged directly to the
console, instead of
just ending up in the journal, is this still the case?

Yes.

Can you attach the output of
cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-5.9.0-1-amd64 root=UUID=e79bfc7a-888d-4380-

Post by Michael Biebl
journalctl -alb
reportbug --template systemd

Those files contain various private information I do not wish to,
send to the bug report, and I do not want to look at all 80K lines
to see what I need to redact.

Fair enough.
Unless you can then provide information how this issue can be
reproduced, there is unfortunately nothing that can be done about it
and I'll have to close it again.

[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.

[Michael Biebl]

Post by Kurt Roeckx
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.

That means you regurlarly (every minute?) run systemctl daemon-reload.
You probably shouldn't do that.

[Kurt Roeckx]

Doing so now.
If you feel comfortable sharing the above information via private
email, you can send it to me directly. I'll promise to not disclose any
information without your prior consent.

I can't reproduce it anymore currently.

I now have systemd 247.1-3+deb11u1 installed.


Kurt