Graphical Environments & Desktops • Gnome errors in Logs

Code:

Mar 06 03:58:27 tux gnome-session[2583]: gnome-session-binary[2583]: WARNING: Could not parse desktop file xapp-sn-watcher.desktop or it references a not found TryExec binaryMar 06 03:58:27 tux gnome-session-binary[2583]: WARNING: Could not parse desktop file xapp-sn-watcher.desktop or it references a not found TryExec binaryMar 06 03:58:27 tux gnome-keyring-daemon[1920]: The PKCS#11 component was already initializedMar 06 03:58:27 tux gnome-keyring-daemon[2592]: discover_other_daemon: 1Mar 06 03:58:27 tux gnome-keyring-pkcs11.desktop[2592]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyringMar 06 03:58:27 tux gnome-keyring-d[1920]: The PKCS#11 component was already initializedMar 06 03:58:27 tux gnome-keyring-daemon[1920]: The Secret Service was already initializedMar 06 03:58:27 tux gnome-keyring-d[1920]: The Secret Service was already initializedMar 06 03:58:27 tux gnome-keyring-daemon[2593]: discover_other_daemon: 1Mar 06 03:58:27 tux gnome-keyring-secrets.desktop[2593]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyringMar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2588.scope: Couldn't move process 2588 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-2588.scope': No such processMar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2588.scope: Failed to add PIDs to scope's control group: No such processMar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2588.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'.Mar 06 03:58:27 tux systemd[1880]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2588.scope - 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 351 and the job result is failed.Mar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dsecrets-2590.scope: Couldn't move process 2590 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-2590.scope': No such processMar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dsecrets-2590.scope: Failed to add PIDs to scope's control group: No such processMar 06 03:58:27 tux systemd[1880]: app-gnome-gnome\x2dkeyring\x2dsecrets-2590.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'.Mar 06 03:58:27 tux systemd[1880]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2590.scope - 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 355 and the job result is failed.Mar 06 03:58:27 tux systemd[1880]: Started app-gnome-gnome\x2dkeyring\x2dssh-2591.scope - Application launched by gnome-session-binary.░░ Subject: A start job for unit UNIT has finished successfully░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ A start job for unit UNIT has finished successfully.░░ ░░ The job identifier is 359.Mar 06 03:58:27 tux gnome-keyring-daemon[2594]: discover_other_daemon: 1Mar 06 03:58:27 tux gnome-keyring-ssh.desktop[2594]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyringMar 06 03:58:27 tux gnome-keyring-ssh.desktop[2594]: SSH_AUTH_SOCK=/run/user/1000/keyring/sshMar 06 03:58:27 tux systemd[1880]: Started gnome-session-manager@gnome.service - GNOME Session Manager (session: gnome).