Bug 1708788 - Unable to clean-up stale keyring entries: Failed to delete credentials from the keyring
Summary: Unable to clean-up stale keyring entries: Failed to delete credentials from t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-10 20:53 UTC by Dan
Modified: 2020-05-26 17:42 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:42:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dan 2019-05-10 20:53:30 UTC
Description of problem: 
Evolution Email is asking for credentials every time is opened. The email client is set up with EWS.

How reproducible:
Not sure. After the upgrade to Fedora 30 all my keyring passwords are gone and Evolution is asking for credentials every time I open it. This machine is using Enterprise login.


Running journactl -f i see:

goa-daemon[5594]: secret_password_clear_sync() failed: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
goa-daemon[5594]: Unable to clean-up stale keyring entries: Failed to delete credentials from the keyring
goa-daemon[5594]: secret_password_clear_sync() failed: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
goa-daemon[5594]: Unable to clean-up stale keyring entries: Failed to delete credentials from the keyring
goa-daemon[5594]: secret_password_clear_sync() failed: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
goa-daemon[5594]: Unable to clean-up stale keyring entries: Failed to delete credentials from the keyring
 
$ rpm -qa |grep keyring
gnome-keyring-3.31.91-1.fc30.x86_64
gnome-keyring-pam-3.31.91-1.fc30.x86_64
libgnome-keyring-3.12.0-17.fc30.x86_64
gnome-keyring-sharp-1.0.1-0.28.133722svn.fc30.x86_64

Comment 1 Dan 2019-05-13 15:26:05 UTC
Update: If i replace the running keyring daemon I can see again the login passwords under seahorse and the above errors are gone. 

$gnome-keyring-daemon -r

Comment 2 suffsuccotash 2019-10-31 03:07:34 UTC
I am having a related problem.  I regularly use x2go, and I was having the issue if Evolution asking for credentials every time it was opened through x2go.

It worked fine locally, but it had that problem through x2go(and vnc).

So x2go folks gave me a solution.  Have x2go run  gnome-keyring-daemon --replace –components=secrets
.

That worked great, until I tried to use evolution from my local machine again.  It then has that same issue with getting prompted for passwords.

Even if I log out of X and back in, the local machine's evolution will not work until I actually reboot.  Even if, on the local machine, I do:

 gnome-keyring-daemon --replace –components=secrets

I still have the same issue on the local machine until I reboot.

--

What to do here?

Thanks!

Comment 3 Ben Cotton 2020-04-30 20:50:05 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2020-05-26 17:42:41 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.