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 647203 - settings of a keyring is in “Unlock” dialog instead of “Properties”
settings of a keyring is in “Unlock” dialog instead of “Properties”
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks: 652459
 
 
Reported: 2011-04-08 18:42 UTC by Matěj Cepl
Modified: 2018-08-03 19:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matěj Cepl 2011-04-08 18:42:51 UTC 
After couple of days looking for a way, how to make my default keyring unlock automatically on login, I have finally in cheer desperation went through all dialogs, buttons, etc. I could find. And to my biggest surprise I found that the only way how to get to the settings of keyring is to lock and then the settings are in the Unlock dialog, which contain also "Automatically unlock on login" setting. But this is really awful UI.

That's IMHO one certain way how to confuse users. Could we get these settings part of the dialog to the Properties dialog (which is almost empty anyway)?
Comment 1 Stef Walter 2011-05-09 09:01:15 UTC 
Agreed, this needs work. So far this is only half done due to ENOTIME :(
Comment 2 freddi34 2017-10-08 12:55:36 UTC 
Redesigning this part of the UI would as a side effect fix a very critical security bug #725641.
But if this one is still blocked due to ENOTIME, I wouldn't mind if someone at least accepts the patch attached to Bbug #725641.
Comment 3 GNOME Infrastructure Team 2018-08-03 19:20:26 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/54.