Bug 459938 - MyPasswordSafe sometimes doesn't show up in Window List
Summary: MyPasswordSafe sometimes doesn't show up in Window List
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: MyPasswordSafe
Version: 10
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ralf Ertzinger
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-24 22:56 UTC by Andre Robatino
Modified: 2009-11-15 23:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-15 23:41:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andre Robatino 2008-08-24 22:56:32 UTC
Description of problem:
If MyPasswordSafe is covered by another application, then when it times out and changes to the "What's your pass-phrase?" window, that window doesn't appear in the Window List (at least until the covering application is moved away).

Version-Release number of selected component (if applicable):
MyPasswordSafe-0.6.7-4.20061216.fc9.i386

How reproducible:
always

Steps to Reproduce:
1. Start MyPasswordSafe.
2. Cover the MyPasswordSafe window with another application.
3. Wait for it to time out and change to the "What's your pass-phrase" window.
  
Actual results:
"What's your pass-phrase" window doesn't appear in Window List, until the covering application is moved.

Expected results:
"What's your pass-phrase" window should appear in Window List, regardless of whether it's covered or not.

Additional info:

Comment 1 Andre Robatino 2008-08-25 08:34:47 UTC
I also found that if I click on "Lock MyPasswordSafe", the same thing happens, even though in this case the "What's your pass-phrase" window is visible.

Comment 2 Andre Robatino 2009-06-27 15:30:38 UTC
This appears to be fixed in Fedora 11.  I can no longer test it in Fedora 10 since all my machines are running F11 now.

Comment 3 Andre Robatino 2009-11-15 23:41:27 UTC
Also appears fixed in Fedora 12.  Closing as CURRENTRELEASE.


Note You need to log in before you can comment on or make changes to this bug.