Bug 699194

Summary: Seahorse Use Unsafe Storage Problem
Product: [Fedora] Fedora Reporter: Nick <suicide_bomber_4_hire>
Component: seahorseAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mclasen, nekohayo, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:22:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A video of the bug in action. Video may be corrupt as I could not cancel the recording and had to reboot. none

Description Nick 2011-04-24 05:29:36 UTC
Created attachment 494488 [details]
A video of the bug in action. Video may be corrupt as I could not cancel the recording and had to reboot.

Description of problem:
When no password is specified for a keyring and the "Use unsafe storage" dialog pops up it is impossible to click either cancel or Use unsafe storage as the window behind it seems to keep the focus.

Version-Release number of selected component (if applicable):
Fedora 15 Beta (all available updates applied)
3.0.0-1.fc15

How reproducible:
Every time unsafe storage is to be used. I can reproduce in gnome shell or in fall-back mode.

Steps to Reproduce:
1. Open seahorse
2. Create a new password keyring and name it
3. Leave the password field blank and click ok
  
Actual results:
On the resulting dialog none of the buttons are clickable

Expected results:
Be able to click cancel or use unsafe storage

Additional info:

Comment 1 Matthias Clasen 2011-04-28 04:02:09 UTC
Fixed in 3.0.1

Comment 2 Jean-François Fortin Tam 2011-06-30 02:45:05 UTC
Hello Matthias, I'm seeing this problem in 3.0.2 (up to date Fedora 15), so this is somehow not fixed, could you reopen?

Comment 3 Matthias Clasen 2011-06-30 17:41:30 UTC
Why don't you reopen it ?

Comment 4 Jean-François Fortin Tam 2011-06-30 19:51:20 UTC
Bugzilla doesn't let me: I am not the reporter and I don't have bug triaging privileges...

Comment 5 Fedora End Of Life 2012-08-07 20:22:34 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping