Two errors after starting the GNOME desktop

inoton · September 7, 2020, 12:54am

Ｈi all
When the system boot is complete, there are two important error messages in ‘gome logs’.

“Failed to start Application launched by gnome-session-binary.”

Desktop environment and version.

OS:Fedora 32 x86-64

$ gnome-shell --version
GNOME Shell 3.36.6

$ echo $XDG_SESSION_TYPE
x11

Journalctl
error I：

...
systemd[878]: Reached target GNOME Color management.
systemd[878]: Reached target GNOME Accessibility settings.
systemd[878]: Failed to start Application launched by gnome-session-binary.
systemd[878]: gnome-launched-user-dirs-update-gtk.desktop-1240.scope: Failed with result 'resources'.
systemd[878]: gnome-launched-user-dirs-update-gtk.desktop-1240.scope: Failed to add PIDs to scope's control group: No such process
systemd[878]: Started Application launched by gnome-session-binary.
...

error II：

...
systemd[878]: gnome-launched-gnome-keyring-ssh.desktop-1051.scope: Succeeded.
systemd[878]: gnome-launched-gnome-keyring-secrets.desktop-1049.scope: Succeeded.
systemd[878]: Failed to start Application launched by gnome-session-binary.
systemd[878]: gnome-launched-xdg-user-dirs.desktop-1056.scope: Failed with result 'resources'.
systemd[878]: gnome-launched-xdg-user-dirs.desktop-1056.scope: Failed to add PIDs to scope's control group: No such process
...

Two errors point to: “xdg-user-dirs” and “xdg-user-dirs-gtk”.
The purpose of the two packages is presumably to automatically change user folders in response to changes in the relevant configuration files.

I’m not clear why the above error message occurs.
For example, logging in again after a language change, the system will automatically pop up a folder renaming window and everything seems fine, or some dependency is missing?

Please help me with this. Thank you.

mershl · September 10, 2020, 7:32pm

I’m seeing exactly the same errors on Fedora Silverblue 32. Seems to be an upstream issue. Haven’t found an issue id yet.

inoton · September 19, 2020, 1:15am

Thank you for your help＠ Mershl

mershl · October 21, 2020, 11:17am

The issue was fixed in Gnome 3.38+. I’m no longer seeing the errors on Fedora 33.

inoton · October 21, 2020, 9:58pm

Thanks for telling me this good news!

inoton · October 28, 2020, 8:13am

The new Fedora 33 release still has similar error messages.
https://pastebin.com/gF9TmfLv

ND8801 · January 20, 2021, 8:32am

confirm Failed to start Application launched by gnome-session-binary.

gnome-shell --version
GNOME Shell 3.38.3

GnomeDesktop-WARNING: Could not create transient scope

GnomeDesktop-WARNING: Could not create transient scope for PID 3986: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3986 does not exist

Process org.freedesktop.systemd1 exited with status 1

systemctl --state=failed --all
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

tronde · May 25, 2021, 11:30am

Hello there,
I’d like to confirm this issue for Fedora 34 on x86_64 hardware. System-Info:

$ gnome-shell --version
GNOME Shell 40.1

$ uname -r
5.12.5-300.fc34.x86_64

$ echo $XDG_SESSION_TYPE
wayland

And here is an excerpt from my journal:

Mai 25 13:05:01 systemd[2137]: Reached target GNOME Session Manager is ready.
Mai 25 13:05:01 systemd[2137]: Starting GNOME Shell on Wayland...
Mai 25 13:05:01 systemd[2137]: Starting GNOME Shell on X11...
Mai 25 13:05:01 systemd[2137]: app-gnome-gnome\x2dkeyring\x2dssh-2258.scope: Deactivated successfully.
Mai 25 13:05:01 systemd[2137]: app-gnome-gnome\x2dkeyring\x2dsecrets-2254.scope: Deactivated successfully.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Mai 25 13:05:01 systemd[2137]: Condition check resulted in GNOME Shell on X11 being skipped.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Mai 25 13:05:01 systemd[2137]: app-glib-liveinst\x2dsetup-2267.scope: Failed to add PIDs to scope's control group: No such process
Mai 25 13:05:01 systemd[2137]: app-glib-liveinst\x2dsetup-2267.scope: Failed with result 'resources'.
Mai 25 13:05:01 systemd[2137]: Failed to start Application launched by gnome-session-binary.
Mai 25 13:05:01 systemd[2137]: app-glib-xdg\x2duser\x2ddirs-2264.scope: Failed to add PIDs to scope's control group: No such process
Mai 25 13:05:01 systemd[2137]: app-glib-xdg\x2duser\x2ddirs-2264.scope: Failed with result 'resources'.
Mai 25 13:05:01 systemd[2137]: Failed to start Application launched by gnome-session-binary.
Mai 25 13:05:01 systemd[2137]: Stopped GNOME Shell on X11.
Mai 25 13:05:01 systemd[2137]: Starting GNOME Shell on X11...
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Mai 25 13:05:01 systemd[2137]: Condition check resulted in GNOME Shell on X11 being skipped.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2.
Mai 25 13:05:01 systemd[2137]: Stopped GNOME Shell on X11.
Mai 25 13:05:01 systemd[2137]: Starting GNOME Shell on X11...
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Mai 25 13:05:01 systemd[2137]: Condition check resulted in GNOME Shell on X11 being skipped.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 3.
Mai 25 13:05:01 systemd[2137]: Stopped GNOME Shell on X11.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Start request repeated too quickly.
Mai 25 13:05:01 systemd[2137]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Mai 25 13:05:01 systemd[2137]: Started GNOME Shell on X11.

I don’t have an idea what’s wrong here. I’d expect that a system under normal circumstences shouldn’t show these errors. But I’m not even sure if it is a bug or a configuraiton issue and my own fault. Does anyone have an idea how to hunt this down?

Regards,
Tronde

bond · July 15, 2021, 5:47am

It looks this is a forever problem. Systemd crashing under GNOME. With or without enabling any third-party gnome extension. What the main reason for it to crash is still confusing to me. Does it have to be not proper integration of Gnome-shell and Systemd? Is GNOME is involved in this issue to began with?

Jul 15 11:20:55 fedora systemd[1545]: Started GNOME Session Manager (session: gnome).
Jul 15 11:20:55 fedora systemd[1545]: Reached target GNOME Session Manager is ready.
Jul 15 11:20:55 fedora systemd[1545]: Starting GNOME Shell on Wayland...
Jul 15 11:20:55 fedora systemd[1545]: Starting GNOME Shell on X11...
Jul 15 11:20:55 fedora systemd[1545]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Jul 15 11:20:55 fedora systemd[1545]: Condition check resulted in GNOME Shell on X11 being skipped.
Jul 15 11:20:55 fedora systemd[1545]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Jul 15 11:20:55 fedora gnome-session[1630]: gnome-session-binary[1630]: GnomeDesktop-WARNING: Could not create transient scope for PID 1653: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1653 does not exist.
Jul 15 11:20:55 fedora gnome-session-binary[1630]: GnomeDesktop-WARNING: Could not create transient scope for PID 1653: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1653 does not exist.
Jul 15 11:20:55 fedora systemd[1545]: app-glib-liveinst\x2dsetup-1653.scope: Couldn't move process 1653 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-glib-liveinst\x2dsetup-1653.scope': No such process
Jul 15 11:20:55 fedora systemd[1545]: app-glib-liveinst\x2dsetup-1653.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 11:20:55 fedora systemd[1545]: app-glib-liveinst\x2dsetup-1653.scope: Failed with result 'resources'.
Jul 15 11:20:55 fedora systemd[1545]: Failed to start Application launched by gnome-session-binary.
Jul 15 11:20:55 fedora systemd[1545]: app-glib-xdg\x2duser\x2ddirs-1652.scope: Couldn't move process 1652 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-glib-xdg\x2duser\x2ddirs-1652.scope': No such process
Jul 15 11:20:55 fedora systemd[1545]: app-glib-xdg\x2duser\x2ddirs-1652.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 11:20:55 fedora systemd[1545]: app-glib-xdg\x2duser\x2ddirs-1652.scope: Failed with result 'resources'.
Jul 15 11:20:55 fedora systemd[1545]: Failed to start Application launched by gnome-session-binary.
Jul 15 11:20:55 fedora systemd[1545]: app-gnome-xdg\x2duser\x2ddirs-1652.scope: Couldn't move process 1652 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-xdg\x2duser\x2ddirs-1652.scope': No such process
Jul 15 11:20:55 fedora systemd[1545]: app-gnome-xdg\x2duser\x2ddirs-1652.scope: Failed to add PIDs to scope's control group: No such process
Jul 15 11:20:55 fedora systemd[1545]: app-gnome-xdg\x2duser\x2ddirs-1652.scope: Failed with result 'resources'.
Jul 15 11:20:55 fedora systemd[1545]: Failed to start Application launched by gnome-session-binary.
Jul 15 11:20:55 fedora systemd[1545]: Stopped GNOME Shell on X11.
Jul 15 11:20:55 fedora systemd[1545]: Starting GNOME Shell on X11...
Jul 15 11:20:55 fedora systemd[1545]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
Jul 15 11:20:55 fedora systemd[1545]: Condition check resulted in GNOME Shell on X11 being skipped.

Gnome-shell: 40.2
Distro: Feodra 34 Workstation

grumpey · July 15, 2021, 10:37am

May want to reference: https://bugzilla.redhat.com/show_bug.cgi?id=1973058

Thanks

nippur · December 8, 2022, 11:43am

Still here at Gnome 42.4 F36 running on X11. Lot’s of:

systemd[xxxx]: Failed to start xxxxxxxx.scope - Application launched by gnome-session-binary.

Reference of Joe doesn’t explain it at all - it is just a suggestion.
Really annoying i can’t find anything on how gnome-session-binary is starting these processes (config file? hard coded?). How to stop gnome-session-binary starting these (and hence systemd)? I really don’t want these annoying errors in my journals, albeit non-critical.
Therefor bumping this topic to the present day.

nippur · February 7, 2023, 4:42pm

Still present in Fedora 37 Gnome 43 running on X11

computersavvy · February 7, 2023, 7:22pm

You are posting on an error that was discussed more than 18 months ago and with fedora 32 which was running gnome 3 and gnome 40+ is a complete new rewrite of gnome.

Please open your own thread since you are running a totally different version of gnome and 5 releases later with fedora…

Topic		Replies	Views
Failed to start Application launched by gnome-session-binary Project Discussion silverblue-team	0	2629	September 2, 2020
Help fix so many errors in system logs Ask Fedora f36 , pipewire , wayland , amd , nvidia	3	554	May 19, 2022
Failed to start xdg-desktop-portal-gnome.service and xdg-desktop-portal-gtk.service error messages after my system froze Ask Fedora f36 , wayland , amd	1	2111	October 10, 2022
Upgrade to 41 beta failed - unable to start Gnome Shell (wayland) Ask Fedora wayland , mutter , beta , gnome , f41	15	770	February 11, 2025
Error message when booting Fedora 36 with Gnome 42, after upgrade Ask Fedora f36	8	2395	July 7, 2022

Two errors after starting the GNOME desktop

Related topics