chmod -x $(type -p gnome-keyring-daemon)

But it means that it's broken.

I am just a computer user so I kill the process with an autostart script. The side effect is that my gnome login-keyring is locked. If needed, with the password and keys app I can unlock that keyring with my user-password and lo and behold '/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets' is running. In the meantime this is good enough for me.

Somehow '/usr/bin/gnome-keyring-daemon --daemonize --login' gets stuck and is not completing its task. If it is a library or a dbus-* problem i don't know. BTW, /run/user/1002/keyring/control is the *only* entry in my keyring-directory.

pretty sure I have gnome-key and a gtk3 powered login... (I only see it if I log out...)

I am running Plasma/kde

Siduction Forum » Upgrade Warnings (DE / EN)
https://forum.siduction.org/index.php?board=22.0

Of course, that's more applicable to Debian than Devuan, but monitoring that forum is likely be at least somewhat helpful for Ceres users.

anything strange on ~/.xsession-errors  | dmesg | messages ?
you need to check why gnome-keyring is using 100% cpu to locate the issue.
perhaps stop some services that use it (cups, avahi, dnscrypt-proxy, bluetoothd, other?) to see if that helps..

p.s. packages don't install without consent. check your dpkg/apt log to see what happened. something else happened during dist-upgraded, you probably consented without taking much attention...
suggestion : better not dist-upgrade next time. simple `apt upgrade` will save you some ceres trouble next time.

I have to move from ceres to daedalus. After ~ 2 month on cerres the system was broken completely and irreversibly. System update of cause. Now the story repeats with daedalus. It breaks every 2-3 weeks.

Both daedalus & ceres are development branches. They are supposed to break. If you want a stable experience run the stable release.

I also reverted to 5.18 kernel, as vmware does not work correctly with 5.19 So slow even with spectre_v2=off or mitigations=off
I have to use vmware as virtualbox neither work correctly nor KVM where virtfs is partly broken too.

Do you really have no issues after updates?

/usr/bin/gnome-keyring-daemon --daemonize --login   100% CPU

pstree gives this

init─┬─ModemManager───2*[{ModemManager}]
     ├─NetworkManager───2*[{NetworkManager}]
     ├─accounts-daemon───2*[{accounts-daemon}]
     ├─at-spi-bus-laun─┬─dbus-daemon
     │                 └─3*[{at-spi-bus-laun}]
     ├─at-spi2-registr───2*[{at-spi2-registr}]
     ├─avahi-daemon───avahi-daemon
     ├─bluetoothd
     ├─cron
     ├─cups-browsed───2*[{cups-browsed}]
     ├─cupsd
     ├─2*[dbus-daemon]
     ├─dbus-launch
     ├─dconf-service───2*[{dconf-service}]
     ├─dnscrypt-proxy───12*[{dnscrypt-proxy}]
     ├─dnsmasq───dnsmasq
     ├─elogind-daemon
     ├─evolution-addre───5*[{evolution-addre}]
     ├─evolution-calen───8*[{evolution-calen}]
     ├─evolution-sourc───3*[{evolution-sourc}]
     ├─gedit───4*[{gedit}]
     ├─6*[getty]
     ├─gjs───10*[{gjs}]
     ├─gnome-keyring-d───3*[{gnome-keyring-d}]

gnome-keyring now eats 100% CPU

also I had broken (yesterday):
pipewire - replaced by pulseaudio - repaired
budgie desktop - replaced by "half gnome" - repaired
gdm3 has been installed without concent and replaced lightdm - repaired

And finally the system is still unusable - 100% CPU by gnome-keyring
Please help to fix it

Devuan Daedalus.