Arch Linux

stueja

Member

Registered: 2015-10-18

Posts: 47

gnome-keyring-daemon causes high disk writes after 1st login /disable?

On my system (Arch 4.2.4-1, Gnome 3.18.1), after the first login (on a day, see below), gnome-keyring-daemon causes high disk writes. This can go on for hours.

tl;dr
- /usr/share/dbus-1/services/org.gnome.keyring.service,
- /usr/share/dbus-1/services/org.freedesktop.secrets.service, and
- /etc/xdg/autostart/gnome-keyring-secrets.desktop
each start the gnome-keyring-daemon.
Which two of those 3 can be disabled?
/tl;dr

Details:

[jan@one ~]$ sudo iotop
Total DISK READ :    2040.49 B/s | Total DISK WRITE :    1282.08 K/s
Actual DISK READ:    2040.49 B/s | Actual DISK WRITE:      45.03 K/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND                                                                                                                                             
 2619 be/4 jan      2040.49 B/s  197.27 K/s  0.00 %  0.15 % gnome-keyring-daemon --daemonize --login [dispatch]
 2329 be/4 jan         0.00 B/s  161.41 K/s  0.00 %  0.00 % gnome-keyring-daemon --daemonize --login [dispatch]
 2616 be/4 jan         0.00 B/s  227.16 K/s  0.00 %  0.00 % gnome-keyring-daemon --daemonize --login [dispatch]
 2617 be/4 jan         0.00 B/s   55.00 K/s  0.00 %  0.00 % gnome-keyring-daemon --daemonize --login [dispatch]
[...]

Replacing the daemon via gnome-keyring-daemon -r -d restarts the daemon but produces the same high amount of disk writes.

[jan@one ~]$ gnome-keyring-daemon -r -d
** Message: Replacing daemon, using directory: /run/user/1000/keyring
GNOME_KEYRING_CONTROL=/run/user/1000/keyring
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

[jan@one ~]$ journalctl -a | grep key
[...]
Okt 30 05:13:00 one org.gnome.evolution.dataserver.Calendar7[2011]: WARNING: gnome-keyring:: couldn't send data: daemon closed connection
Okt 30 05:13:00 one gnome-keyring-daemon[13833]: Replacing daemon, using directory: /run/user/1000/keyring
Okt 30 05:13:00 one gnome-keyring-daemon[13833]: Unsupported or unknown SSH key algorithm: ssh-ed25519
[...]

After I log out and back in -- or reboot --, gnome-keyring-daemon is listed in iotop, however "normal", only one instance, and not on top of the list any more:

[jan@one ~]$ sudo iotop
[...]
28678 be/4 jan         0.00 B/s    0.00 B/s  0.00 %  0.00 % gnome-keyring-daemon --daemonize --login [dispatch]
[...]

I assume I need gnome-keyring-daemon for Gnome Online Accounts (so that my Google calendar will display if I click the date/time in Gnome's top bar). I read the article about Gnome Keyring (https://wiki.archlinux.org/index.php/GNOME_Keyring) and about disabling one of the components, and Google Calendar does not work if I disable gnome-keyring-daemon, e. g. by uncommenting:

cat /etc/xdg/autostart/gnome-keyring-secrets.desktop
[...]
###Exec=/usr/bin/gnome-keyring-daemon --start --components=secrets
[...]

(I do not need an ssh-agent, btw, so I don't mind if Gnome does not store my SSH passwords. I am using ed25519 anyway, and the keyring cannot store them as of today.)

I found out that gnome-keyring-daemon is being started from .service files in /usr/share/dbus-1/services/ and from .desktop files in /etc/xdg/autostart/

[jan@one ~]$ grep -r gnome-keyring-daemon /usr/share/dbus-1/services/
/usr/share/dbus-1/services/org.gnome.keyring.service:Exec=/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
/usr/share/dbus-1/services/org.freedesktop.secrets.service:Exec=/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
[jan@one ~]$ grep -r gnome-keyring-daemon /etc/xdg/autostart
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop:Exec=/usr/bin/gnome-keyring-daemon --start --components=pkcs11
/etc/xdg/autostart/gnome-keyring-secrets.desktop:Exec=/usr/bin/gnome-keyring-daemon --start --components=secrets
/etc/xdg/autostart/gnome-keyring-ssh.desktop:Exec=/usr/bin/gnome-keyring-daemon --start --components=ssh

So it looks like the "secrets" component is being started 3 times, via
/usr/share/dbus-1/services/org.gnome.keyring.service,
/usr/share/dbus-1/services/org.freedesktop.secrets.service, and
/etc/xdg/autostart/gnome-keyring-secrets.desktop

I understand that the "secrets" component is necessary for, e. g. authenticating Google Calendar.

I don't understand why it looks being autostarted 3 times, and I'd like to know whether I can disable 2 of them. And if so, which of those 3? Which specific difference is there between gnome, freedesktop and xdg?

Last edited by stueja (2015-10-30 05:41:20)

stueja

Member

Registered: 2015-10-18

Posts: 47

Re: gnome-keyring-daemon causes high disk writes after 1st login /disable?

Anyone?

godfuture

Member

Registered: 2015-09-18

Posts: 2

Re: gnome-keyring-daemon causes high disk writes after 1st login /disable?

I have the same issue with Ubuntu Mate 19.10. As I am using a USB stick as root device, I am concerned about unnecessary disk writes. Most times it happens, sometimes not.

Did you solve it?