Should I be worried about these?

Desktop
1

Or do I need to report them as an issue?

systemd error:

systemd[1743]: app-gnome-gnome\x2dkeyring\x2dssh-1866.scope: PID 1866 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1866.scope', skipping: No such process
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dssh-1866.scope: No PIDs left to attach to the scope's control group, refusing.
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dssh-1866.scope: Failed with result 'resources'.
systemd[1743]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-1866.scope - Application launched by gnome-session-binary.

systemd[1743]: app-gnome-gnome\x2dkeyring\x2dsecrets-1862.scope: Couldn't move process 1862 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-1862.scope': No such process
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dsecrets-1862.scope: Failed to add PIDs to scope's control group: No such process
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dsecrets-1862.scope: Failed with result 'resources'.
systemd[1743]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-1862.scope - Application launched by gnome-session-binary.

systemd[1743]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1860.scope: PID 1860 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-1860.scope', skipping: No such process
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1860.scope: No PIDs left to attach to the scope's control group, refusing.
systemd[1743]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1860.scope: Failed with result 'resources'.
systemd[1743]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-1860.scope - Application launched by gnome-session-binary.

Fedora 41 Gnome 47

2

It’s 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. Assigning processes to cgroups is inherently racy and is expected to fail. The bug here is we shouldn’t print warning messages when something totally normal happens.

3

It looks like the failing programs seem to be these (/etc/xdg/autostart/gnome-keyring-*.desktop), and I see no gnome-keyring-daemon process present in my user processes. So it may not just be a matter of assigning processes to specific cgroups.
I found these:

Jan 01 12:54:18 gnome-keyring-daemon[1695]: couldn't access control socket: /run/user/42/keyring/control: 没有那个文件或目录
Jan 01 12:54:18 gnome-keyring-daemon[1695]: discover_other_daemon: 0
Jan 01 12:54:18 gnome-keyring-d[1695]: couldn't access control socket: /run/user/42/keyring/control: 没有那个文件或目录
Jan 01 12:54:21 gnome-keyring-daemon[1870]: couldn't access control socket: /run/user/1000/keyring/control: 没有那个文件或目录
Jan 01 12:54:21 gnome-keyring-daemon[1870]: discover_other_daemon: 0
Jan 01 12:54:21 gnome-keyring-d[1870]: couldn't access control socket: /run/user/1000/keyring/control: 没有那个文件或目录
Jan 01 12:54:21 gnome-keyring-daemon[1875]: couldn't access control socket: /run/user/1000/keyring/control: 没有那个文件或目录
Jan 01 12:54:21 gnome-keyring-daemon[1875]: discover_other_daemon: 0
Jan 01 12:54:21 gnome-keyring-d[1875]: couldn't access control socket: /run/user/1000/keyring/control: 没有那个文件或目录
Jan 01 12:54:21 gnome-keyring-pkcs11.desktop[1870]: discover_other_daemon: 0
Jan 01 12:54:21 gnome-keyring-daemon[1878]: discover_other_daemon: 1
Jan 01 12:54:21 gnome-keyring-ssh.desktop[1878]: discover_other_daemon: 1
Jan 01 12:54:21 gnome-keyring-secrets.desktop[1875]: discover_other_daemon: 0

The meaning of the Chinese in the log is: there is no such file or directory.