Seahorse – No Longer Provides Passwords for Skype, Enigmail, and Nextcloud

enigmailnextcloudseahorseskype

I am using Ubuntu 16.04. I am using Skype, Thunderbird with Enigmail and Nextcloud. This three applications have passwords stored by Seahorse and when you enter them once, you don't have to reenter them.

But I don't know why, one morning these three applications were asking me again passwords. And they do each time that I restart now.

Do you have an idea why? It is boring to reenter passwords at each restart, do you know a way to debug this? I'll be glad to provide more information, but right now, I don't know which ones.

EDIT:

Details about the packages:

nextcloud-client from this ppa: ppa:nextcloud-devs/client
Skype for Linux Beta 5.2.0.1
Enigmail version 1.9.7 integrated to Thunderird 52.2.1 (Using gpg executable /usr/bin/gpg2 to encrypt and decrypt)

The current version of Seahorse is 3.18.0. When I open it there is no password section, that's maybe a hint. I don't know.

EDIT 2:

pgrep -afu "$USER" 'keyring|agent'

1602 /usr/bin/gnome-keyring-daemon --daemonize --login
5235 /usr/bin/gnome-keyring-daemon --daemonize --login
5379 gpg-agent --homedir /home/paul/.gnupg --use-standard-socket --daemon
5621 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1

printenv | grep -e KEYRING -e AGENT

GPG_AGENT_INFO=/home/paul/.gnupg/S.gpg-agent:0:1
GNOME_KEYRING_CONTROL=
GNOME_KEYRING_PID=

Thank you very much.

Best Answer

I have found the solution, the question is related to this bug: bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825.

The fix is to execute sudo apt autoremove --purge dbus-user-session.

dbus-user-session is installed automatically with flatpak.

Related Solutions

Seahorse – Where Does GNOME Keyring Store Its Keyrings

In Ubuntu 17.10, this is found under ~/.local/share/keyrings

Ubuntu – Is it possible to use secret-tool to lookup existing seahorse passwords

I made a utility, lssecret, that lists all items using libsecret, including all GNOME Keyring items. It looks like libsecret automatically adds a key value pair for every item, but Seahorse doesn't show them in the GUI. Here's some example output from lssecret:

Collection: Login

Item:   Test Password
Secret: Tr0ub4dor&3
Key:    xdg:schema
Value:  org.gnome.keyring.Note

Item:   secret-tool item
Secret: s3cret-t00l
Key:    my key
Value:  my value
Key:    xdg:schema
Value:  org.freedesktop.Secret.Generic

Item:   Unlock password for: cueball@xkcd.com
Secret: correct horse battery staple
Key:    unique
Value:  ssh-store:/home/cueball/.ssh/id_rsa
Key:    xdg:schema
Value:  org.freedesktop.Secret.Generic

Item:   Network secret for GenericSSID/802-1x/password
Secret: S3cureW1f1Passw0rd
Key:    setting-name
Value:  802-1x
Key:    connection-uuid
Value:  6a762552-04b3-cd05-45ba-586688e0a029 
Key:    xdg:schema
Value:  org.freedesktop.NetworkManager.Connection
Key:    setting-key
Value:  password

GNOME Keyring stores each keyring as a collection in the secret service. You can see the default keyring, Login, in the output. The items represent:

A password added to the keyring using seahorse. The description is "Test Password" and the actual password is "Tr0ub4dor&3".
An item added using the command secret-tool store --label="secret-tool item" "my key" "my value", then typing "s3cret-t00l" into the prompt.
A password for an ssh key so it can be automatically unlocked by gnome keyring. It was added using ssh-add from the command line, then checking the "Automatically unlock this key at login" box when it was first used.
A wifi network password added by selecting "Store the password only for this user" in the NetworkManager connection editor.

As you can see, passwords added to a keyring using Seahorse have a key value pair of "xdg:schema" and "org.gnome.keyring.Note". You can list them all using secret-tool search --all xdg:schema org.gnome.keyring.Note.

Related Question