Red Hat Bugzilla – Bug 170868
gnome-keyring-manager starts with an error dialog
Last modified: 2007-11-30 17:11:15 EST
Which says "No such keyring".
a) It should give a hint which keyring it was trying to open. (From the
window title "default Keyring" one can guess that it tries to open
the keyring named "default").
b) If you turn on the Keyrings panel (why is that not on by default ?)
you see that there actually are 2 keyrings, one of which is named
"Default". So maybe it just tries to open the wrong keyring initially ?
Upstream bug is http://bugzilla.gnome.org/show_bug.cgi?id=317037
This interface for this is rather bad. We should probably <Exclude> it from the
menus by deafult.
ray: It has been through multiple UI reviews...
Without it there is really no way to manage your keyrings though.
Lets just list the major UI problems:
- error dialog at startup
- list of keyrings not visible at startup
- Lock on idle checkbox inoperable
- Lock timeout fixed at 0
- The key tab is just empty when no key is selected
- The applications tab displays a cryptic /path/to/application
when no key is selected
- When a key is selected, it displays the path of the binary,
which is not much better
- What does Read/Write/Delete mean there ?
- The "More Options" tab shows information that nobody can understand
without documentation. Unfortunately, there is no documentation...
- The type column in the key list is not explained any further. What do
the icons mean ?
- "Delete key" should be a context menu item on the key list
- The key/application tabs display stale information when I switch to a
- Doesn't monitor keyrings, and no refresh menuitem
- If I initially deny it to see a key, the key gets shown with an empty
name in the list, and the name is not updated, if I later unlock the key
- "Unlock" should be in the context menu of locked keys
The long list has been filed upstream, the original issue in this bug has been
fixed in rawhide.