After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596598 - password listbox is not updated without restarting seahorse
password listbox is not updated without restarting seahorse
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
2.26.x
Other All
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 608193 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-28 12:54 UTC by Sam Morris
Modified: 2018-08-03 19:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Morris 2009-09-28 12:54:51 UTC 
I stored a password in evolution, while seahorse was open. I typed the password incorrectly and, since evolution does not provide a way to change web calendar passwords, switched to seahorse to remove it. But the password did not show up in seahorse until I restarted it.
Comment 1 Stef Walter 2009-10-09 01:52:00 UTC 
The current gnome-keyring API doesn't allow us to monitor for changes in the keyring. A new API is under development which has that feature.
Comment 2 Pablo Castellano (IRC: pablog) 2010-02-20 19:13:59 UTC 
*** Bug 608193 has been marked as a duplicate of this bug. ***
Comment 3 Vitezslav Humpa 2011-05-12 17:41:23 UTC 
I run into a connected issue:
When I have only the single "Login" keyring (that was created by default on first password storage attempt) and I choose to delete this keyring, it doesn't disappear from the list afterwards. If I attempt to delete the keyring again, messagebox pops out saying that the keyring doesn't exist. After restaring seahorse, keyring is no longer present.

Interestingly enough, this happens only with the default "Login" keyring.
Comment 4 Vitezslav Humpa 2011-05-12 17:42:45 UTC 
Oh, I have seahorse-3.0.1-1 and gnome-keyring-3.0.1-2 on Fedora 15
Comment 5 GNOME Infrastructure Team 2018-08-03 19:16:19 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/39.