GNOME Bugzilla – Bug 769666
Occasional error retrieving secret via Secret Service DBUS API
Last modified: 2017-02-28 11:51:57 UTC
Geary and other gnome-keyring users report that occasionally an error is returned when looking up passwords via dbus. This seems to be due to an error from gnome-keyring, rather than say libsecret. The password is not actually forgotten, it's just that gkd encounters and reports some error. A recent error from gkd, as reported by libsecret, looks like this: > org.freedesktop.DBus.Error.Failed: Couldn't create item: The secret was transferred or encrypted in an invalid way. The latter string is found in daemon/dbus/gdk-secret-objects.c in the cleanup of collection_method_create_item(). For some background, Geary is using libsecret's secret_password_lookup() method to retrieve passwords, using the SECRET_SCHEMA_COMPAT_NETWORK schema. In the case above, this password was possibly the first of three accounts that would have needed password lookups, and the second two accounts were able to lookup their secrets without error. The Geary bug report is here: https://bugzilla.gnome.org/show_bug.cgi?id=714128, and this issue has been reported downstream in both Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1221955 and Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659036, at least.
Also reported in the Red Hat Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1325993
*** Bug 681815 has been marked as a duplicate of this bug. ***
There can be also messages like (for easier searching): > ** Message: received an invalid or unencryptable secret
*** Bug 772290 has been marked as a duplicate of this bug. ***
It don't happen that often but when it happen it's quite annoying :) I hope that can be fixed. Thanks !
[offtopic] (In reply to jeremy9856 from comment #5) > I hope that can be fixed. Thanks ! @jeremy9856: Everybody hopes that everything can be fixed... Please refrain from adding such comments: They create mail notifications that someone has to read and they don't add anything substantial to the ticket. Thank you.
*** This bug has been marked as a duplicate of bug 778357 ***