Bug 702777

Summary: Logging in with fingerprint causes the keyring password unlock prompt to be shown twice
Product: [Fedora] Fedora Reporter: Jean-François Fortin Tam <nekohayo>
Component: gnome-keyringAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: marbolangos, tbzatek, tsmetana, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-keyring-3.0.3-1.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-13 09:49:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screencast none

Description Jean-François Fortin Tam 2011-05-07 04:05:55 UTC
Created attachment 497475 [details]
screencast

If using biometric authentification to log in from gdm, I get asked for my password to unlock the keyring twice in a row with the same dialog (see attached screencast).

Comment 1 Fabien Archambault 2011-05-20 08:54:37 UTC
I had nearly the same issue being asked the password after login with my fingerprint. This should unlock the keyring!

Comment 2 Jean-François Fortin Tam 2011-05-20 12:21:17 UTC
Fabien, that's bug #498926
Mine is about it being shown twice instead of once.

Comment 3 Fabien Archambault 2011-05-20 12:26:56 UTC
Sorry. Thanks for the good bug number (I was not able to find it).
Btw I cannot reproduce yours...

Comment 4 Jean-François Fortin Tam 2011-05-20 13:42:13 UTC
Yeah, that's kinda strange... I don't think I have two different keyrings, seahorse shows only one, fwiw...

Comment 5 Tomáš Bžatek 2011-06-03 16:17:02 UTC
Can you please test https://admin.fedoraproject.org/updates/gnome-keyring-3.0.3-1.fc15 ?

Comment 6 Jean-François Fortin Tam 2011-06-11 21:18:43 UTC
That latest update indeed seems to have fixed the problem. The changelog for 3.0.3 seems to indicate that it was indeed resolved by this release.

Comment 7 Tomáš Bžatek 2011-06-13 09:49:47 UTC
Okay, great, thanks for testing that.