1

If you check the error log it comes to that .scope unit is not found - No such process. I got similar error 4 times.

I would like to understand what is going on during the boot process. Why these errors appear? How to debug it to find even more details?

The full log

First three errors appear in this part

...
Jan 05 13:42:51 magnetron systemd[2284]: Starting GNOME Session Manager (session: gnome)...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has begun execution.
░░ 
░░ The job identifier is 393.
Jan 05 13:42:51 magnetron gnome-keyring-daemon[2337]: The PKCS#11 component was already initialized
Jan 05 13:42:51 magnetron gnome-keyring-d[2337]: The PKCS#11 component was already initialized
Jan 05 13:42:51 magnetron gnome-keyring-daemon[2337]: The Secret Service was already initialized
Jan 05 13:42:51 magnetron gnome-keyring-secrets.desktop[2746]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 05 13:42:51 magnetron gnome-keyring-secrets.desktop[2746]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 05 13:42:51 magnetron gnome-keyring-pkcs11.desktop[2745]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 05 13:42:51 magnetron gnome-keyring-pkcs11.desktop[2745]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 05 13:42:51 magnetron gnome-keyring-ssh.desktop[2744]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Jan 05 13:42:51 magnetron gnome-keyring-ssh.desktop[2744]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Jan 05 13:42:51 magnetron gnome-keyring-d[2337]: The Secret Service was already initialized
Jan 05 13:42:51 magnetron gnome-keyring-daemon[2744]: discover_other_daemon: 1
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2742.scope: Couldn't move process 2742 to requested cgroup '/user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-gnome\x2
dkeyring\x2dpkcs11-2742.scope': No such process
Jan 05 13:42:51 magnetron gnome-keyring-daemon[2746]: discover_other_daemon: 1
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2742.scope: Failed to add PIDs to scope's control group: No such process
Jan 05 13:42:51 magnetron gnome-keyring-daemon[2745]: discover_other_daemon: 1
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2742.scope: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jan 05 13:42:51 magnetron systemd[2284]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 450 and the job result is failed.
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dsecrets-2743.scope: Couldn't move process 2743 to requested cgroup '/user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-2743.scope': No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dsecrets-2743.scope: Failed to add PIDs to scope's control group: No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dsecrets-2743.scope: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jan 05 13:42:51 magnetron systemd[2284]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 454 and the job result is failed.
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dssh-2740.scope: Couldn't move process 2740 to requested cgroup '/user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-2740.scope': No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dssh-2740.scope: Failed to add PIDs to scope's control group: No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-gnome\x2dkeyring\x2dssh-2740.scope: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jan 05 13:42:51 magnetron systemd[2284]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
...

The last error is at different place in the log:

Jan 05 13:42:51 magnetron gnome-session[2735]: gnome-session-binary[2735]: GnomeDesktop-WARNING: Could not create transient scope for PID 2747: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2747 does not exist.
Jan 05 13:42:51 magnetron gnome-session-binary[2735]: GnomeDesktop-WARNING: Could not create transient scope for PID 2747: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2747 does not exist.
Jan 05 13:42:51 magnetron gnome-session[2735]: gnome-session-binary[2735]: GnomeDesktop-WARNING: Could not create transient scope for PID 2749: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2749 does not exist.
Jan 05 13:42:51 magnetron gnome-session-binary[2735]: GnomeDesktop-WARNING: Could not create transient scope for PID 2749: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2749 does not exist.
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-at\x2dspi\x2ddbus\x2dbus-2752.scope: Couldn't move process 2752 to requested cgroup '/user.slice/user-1000.slice/[email protected]/app.slice/app-gnome-at\x2dspi\x2ddbus\x2dbus-2752.scope': No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-at\x2dspi\x2ddbus\x2dbus-2752.scope: Failed to add PIDs to scope's control group: No such process
Jan 05 13:42:51 magnetron systemd[2284]: app-gnome-at\x2dspi\x2ddbus\x2dbus-2752.scope: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'resources'.
Jan 05 13:42:51 magnetron systemd[2284]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 

My system is Debian Bookworm:

uname -a

Linux magnetron 6.0.0-6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1 (2022-12-09) x86_64 GNU/Linux

1 Answer 1

0

My guess is that there is some error in the "GNOME Session Manager (session: gnome)" service unit. Because no sane systemd-unit is named "UNIT" 😉 Most likely a typo in there...

Jan 05 13:42:51 magnetron gnome-keyring-secrets.desktop[2746]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring

Also this line looks strange to me also, because of the 1 and GNOME_KEYRING_CONTROL=/run/user/1000/keyring being concatenated.
So the problem could also be in the gnome-keyring-secrets.desktop file or the automatically generated unit file for it...🤷

1
  • While I would like to accept the answer it does not help. I still don't know here the error is :(.
    – tukan
    Sep 7, 2023 at 14:32

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .