Bug 586421 - screensaver never saves if any menu open
Summary: screensaver never saves if any menu open
Keywords:
Status: CLOSED DUPLICATE of bug 247653
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-screensaver
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: jmccann
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-27 14:23 UTC by Ted X Toth
Modified: 2015-01-14 23:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-27 14:22:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ted X Toth 2010-04-27 14:23:32 UTC
Description of problem:
The screensaver will not lock/save the screen if a window menu is open.

Version-Release number of selected component (if applicable):
gnome-screensaver-2.28.0-11

How reproducible:
very

Steps to Reproduce:
1. Select the 'System' menu, leave it popped down and do nothing else except wait for the screen to lock/save.

Actual results:
Screen never locks.

Expected results:
Screen should lock/save due to the inactivity regardless of whether a menu has be selected.

Additional info:

Comment 2 RHEL Program Management 2010-04-27 15:57:51 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Ted X Toth 2010-04-27 18:32:32 UTC
Well it did eventually save/lock but it took much longer than the 1 minute I have configured. So close this bug, sorry for the bother.

Comment 4 ritz 2010-04-28 09:49:30 UTC
known issues -https://bugzilla.redhat.com/show_bug.cgi?id=247653

Comment 5 jmccann 2010-05-27 14:22:23 UTC

*** This bug has been marked as a duplicate of bug 247653 ***


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