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 779428 - No keyrings are mentioned in UI
No keyrings are mentioned in UI
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
3.20.x
Other Linux
: Normal major
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2017-03-01 17:08 UTC by Andrei Dziahel
Modified: 2018-08-03 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
missing keyrings section (28.04 KB, image/png)
2017-03-01 17:08 UTC, Andrei Dziahel
Details

Description Andrei Dziahel 2017-03-01 17:08:49 UTC
Created attachment 346982 [details]
missing keyrings section

Seahorse UI shows no mentions of keyrings 

Repro: 

1. run seahorse
2. (optional) create new keyring 

Expected behavior: a "Keyrings" subsection shows up on the left, with at least one item named "Login".

What happens instead: "Keyrings" section in a treeview on the left is missing, not to mention any particular keyring or it's content (see attached screenshot). Also couldn't find related secrets with search. 

Q&A

Q: How do you know keyring is there?
A: The file login.keyring does exist, has reasonable size and is updated tens of minutes ago (my bugzilla.gnome.org account's password was saved by Google Chrome which does sync passwords with keyring): 

> $  env LC_ALL=C ls -lh ~/.local/share/keyrings/
> total 7.3M
> -rw------- 1 develop7 users 1.3K Nov  4 10:53 6C551E801BE3A373191AA9EF36F3FF51BE383865.pkcs8
> -rw------- 1 develop7 users 7.3M Mar  1 19:03 login.keyring
> -rw------- 1 develop7 users  389 Feb  7 17:18 user.keystore

Q: How do you know (some) secrets are there?
A: There is saved backups' password — Deja Dup does not ask it doing daily backup; there most certainly are Google Chrome passwords and retrieving them takes tens of seconds of gnome-keyring-daemon consuming ~110% CPU. Sure, these are circumstantial, but still.
Comment 1 Andrei Dziahel 2018-03-21 08:52:14 UTC
One year later, no signs of life. Would a donation help moving this forward? Pretty sure $25 won't be enough, would a $100 do the job?
Comment 2 GNOME Infrastructure Team 2018-08-03 19:52:56 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/157.