Date: Wed, 22 Sep 2021 09:45:43 +0200 From: Leon Christopher Dietrich <doralitze@chaotikum.org> To: freebsd-questions@freebsd.org Subject: Gnome-keyring not unlocking Message-ID: <c72bea2d-9a26-9fe6-1068-a7dd751ba73a@chaotikum.org> In-Reply-To: <mailman.39.1631448001.34738.freebsd-questions@freebsd.org> References: <mailman.39.1631448001.34738.freebsd-questions@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there, I recently switched from running i3 on Xorg to running sway (Wayland) due to issues that I encountered with a new version of a software I really need to use when running Xorg. Everything went well except for the Nextcloud desktop synchronization tool which refuses to log in due to not being able to read/write to a locked key ring. Trying to unlock the key ring manually fails (seahorse simply does nothing when clicking on "unlock"). The deamon is running. Issuing `ps -aux | grep keyring` proves so. The strange ting is that my /tmp/xdgdir/keyring directory only lists sockets for control and pkcs11 while the daemon was started with ``` eval $(/usr/local/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets) export GNOME_KEYRING_CONTROL=/tmp/xdgdir/keyring ``` This is my content of the .local/share/keyrings directory: ``` ➜ l .local/share/keyrings total 18 drwx------ 2 doralitze doralitze 4B Sep 22 09:14 . drwx------ 10 doralitze doralitze 12B Sep 22 09:39 .. -rw------- 1 doralitze doralitze 1.1K Sep 21 15:00 login.keyring -rw-r--r-- 1 doralitze doralitze 207B Sep 22 09:13 user.keystore ``` I'm not having any clue left on what's going on and would appreciate any help. Thanks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c72bea2d-9a26-9fe6-1068-a7dd751ba73a>