Broken after dist-upgrade Daedalus

Devarch · 2022-10-03 17:27:41

Please help.
The system is broken after dist-upgrade just an hour ago:

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.

Last edited by Devarch (2022-10-03 17:32:29)

Devarch · 2022-10-03 19:31:10

It is strange. The package gnome-keyring has not been updated. Some packages which names starts with gnome- where updated.
I do not understand, gnome creates so much problem!
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.

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}]

Last edited by Devarch (2022-10-03 19:31:35)

JesterOfSorts · 2022-10-12 16:57:23

Has this issue been addressed anywhere? I'm having to manually terminate "gnome-keyring-daemon" each time...

Head_on_a_Stick · 2022-10-14 15:33:33

Devarch wrote:

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.

xinomilo · 2022-10-14 17:24:08

no issues here, but not running gnome or vmware nor virtualbox.

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.

pcalvert · 2022-10-14 19:26:25

Monitoring this forum may be helpful for Ceres users:

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.

GlennW · 2022-10-15 00:20:23

+1 "no issues here, but not running gnome or vmware nor virtualbox."

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

I am running Plasma/kde

fred43 · 2022-10-26 02:18:25

I am on Daedalus (with lightdm + elogind + xfce4) and there is an issue with gnome-keyring. Googling does reveal that this '100% of CPU' does appear from time also in so-called stable distros and branches. gnome-keyring is certainly a bit fragile, it goes belly-up for too many reasons.

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.

nixer · 2022-10-26 19:32:04

I too had this problem, so I uninstalled gnome-keyring. Nothing much was removed maybe a dependency or two and I can't find anything that is not working, yet. It no longer locks the cpu at 100% usage.

Devarch · 2022-10-30 23:38:51

I did almost the same, decapitate gnome-keyring-daemon :

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

But it means that it's broken.

The officially official Devuan Forum!

#1 2022-10-03 17:27:41

Broken after dist-upgrade Daedalus

#2 2022-10-03 19:31:10

Re: Broken after dist-upgrade Daedalus

#3 2022-10-12 16:57:23

Re: Broken after dist-upgrade Daedalus

#4 2022-10-14 15:33:33

Re: Broken after dist-upgrade Daedalus

#5 2022-10-14 17:24:08

Re: Broken after dist-upgrade Daedalus

#6 2022-10-14 19:26:25

Re: Broken after dist-upgrade Daedalus

#7 2022-10-15 00:20:23

Re: Broken after dist-upgrade Daedalus

#8 2022-10-26 02:18:25

Re: Broken after dist-upgrade Daedalus

#9 2022-10-26 19:32:04

Re: Broken after dist-upgrade Daedalus

#10 2022-10-30 23:38:51

Re: Broken after dist-upgrade Daedalus

Board footer