The Gnome-Keyring tragedy

Posted on Apr 25, 2020 by Vincent TruchseƟ

To make this short, I am a huge fan of Nextcloud. I think it is a great platform and makes a great contribution to our digital self-empowerment.
That said, I do hate the nextcloud-client for linux. Not that it is not doing what it is intended to do (synching files) but for the decision to completely rely on gnome-keyring to store it’s credentials. Usually, if you happen to use any ready-to-use desktop-environment such as Mate, Gnome or KDE, things will just work (Ok, not if you’re using Gnome because NC is still using the legacy-notification-api only). If you don’t (like us awesome-users) it really becomes a pain in the but to get the gnome-keyring-daemon running properly. Not that it is difficult to get it running but if it doesn’t run you barely find any useful resource on this matter.

This Blogpost is not going into details about how to debug this but just states the thins I did to get it running. Mainly, I just put this up here, so I know where to look if I ever encounter this again.

The Steps

Make sure the following packages are installed (on Arch):

  • gnome-keyring

  • libsecret

  • libgnome-keyring

  • seahorse

In the ~/.xinitrx, add the following lines:

source /etc/X11/xinit/xinitrc.d/50-systemd-user.sh
eval $(/usr/bin/gnome-keyring-daemon --start --components=secrets)

and restart the xsession. Now, open seahorse and create a keyring, giving it no password in my case (Full-disk-encryption, single-user-system). Afterwards, right-click the keyring and set it as default.
Now run nextcloud, grant access and watch the credentials popping up in seahorse.

Tags: linuxkeyring