Systemd security warning Failed to start Application launched by gnome-session-binary

Ask Fedora
,
1

Hi, I’m getting back in touch to work through my other log warnings that I’ve had since I got Fedora 34 on my laptop.
The current package with nine security warnings from the log.

17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2424.scope: Failed with result 'resources'.
17:54:42 systemd: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2424.scope: Failed to add PIDs to scope's control group: No such process
17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-glib-vmware\x2duser-2434.scope: Failed with result 'resources'.
17:54:42 systemd: app-glib-vmware\x2duser-2434.scope: Failed to add PIDs to scope's control group: No such process
17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-glib-vboxclient-2447.scope: Failed with result 'resources'.
17:54:42 systemd: app-glib-vboxclient-2447.scope: Failed to add PIDs to scope's control group: No such process
17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-glib-user\x2ddirs\x2dupdate\x2dgtk-2424.scope: Failed with result 'resources'.
17:54:42 systemd: app-glib-user\x2ddirs\x2dupdate\x2dgtk-2424.scope: Failed to add PIDs to scope's control group: No such process
17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-glib-gnome\x2dshell\x2doverrides\x2dmigration-2433.scope: Failed with result 'resources'.
17:54:42 systemd: app-glib-gnome\x2dshell\x2doverrides\x2dmigration-2433.scope: Failed to add PIDs to scope's control group: No such process
17:54:42 systemd: Failed to start Application launched by gnome-session-binary.
17:54:42 systemd: app-gnome-spice\x2dvdagent-2342.scope: Failed with result 'resources'.
17:54:42 systemd: app-gnome-spice\x2dvdagent-2342.scope: Failed to add PIDs to scope's control group: No such process
17:54:40 systemd: Failed to start Application launched by gnome-session-binary.
17:54:40 systemd: app-glib-xdg\x2duser\x2ddirs-2013.scope: Failed with result 'resources'.
17:54:40 systemd: app-glib-xdg\x2duser\x2ddirs-2013.scope: Failed to add PIDs to scope's control group: No such process
17:54:40 systemd: Failed to start Application launched by gnome-session-binary.
17:54:40 systemd: app-glib-liveinst\x2dsetup-2015.scope: Failed with result 'resources'.
17:54:40 systemd: app-glib-liveinst\x2dsetup-2015.scope: Failed to add PIDs to scope's control group: No such process
17:54:40 systemd: Failed to start Application launched by gnome-session-binary.
17:54:40 systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Failed with result 'resources'.
17:54:40 systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Failed to add PIDs to scope's control group: No such process

Since I am not really familiar with it I would like to direct my question to the specialists, if someone can help me with it.

Many greetings

3 Likes
2

I too get this similar message by systemd ever since I upgraded from F35 to F36.
I wonder what this is really about!

Sender: systems
Time: (basically in each boot)
Messsage: Failed to start app-glib-gnome\x2dshell\x2doverrides\x2dmigration-2503.scope - Application launched by gnome-session-binary.
Audit session: 3
Priority: 3
...
3

Still present in Fedora 41

And by the way, RH is offering a solution for a subscription with them … It is a bit a shame.

And yes, i should not respond on old topics … but I do it anyway.

1973058 – Many "Failed to start Application launched by gnome-session-binary" errors on boot

4

Added bug-reported

5

RHEL Bug …
https://bugzilla.redhat.com/show_bug.cgi?id=2150212

gnome-desktop bug is here, GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 7883 does not exist. (#160) · Issues · GNOME / GNOME Utility Library · GitLab

The RHEL bug was closed as won’t fix so there is not an available solution …

7

And why does RH for RHEL 9 write it has a ?! :
Solution Verified - Updated April 17 2024 at 9:32 AM

Screenshot from 2024-09-02 19-14-40
Screenshot from 2024-09-02 19-14-401079×384 41.9 KB

I meant opensource projects should be “Open” also in debugging, and release such solutions upstream.