Bug 866341

Summary: Regression: Gnome Screensaver Does Not Shutoff Monitor (kernel-3.6.1-1.fc17.x86_64)
Product: [Fedora] Fedora Reporter: Joseph D. Wagner <joe>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 868440 (view as bug list) Environment:
Last Closed: 2012-10-19 17:04:32 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
System Information none

Description Joseph D. Wagner 2012-10-15 02:24:50 EDT 
Description of problem:
On previous versions, the GNOME screensaver would always shutoff the monitor when the idle time had elapsed.  On kernel-3.6.1-1, the screensaver blanks and locks the screen, but it does not shutoff the monitor.

Version-Release number of selected component (if applicable):
kernel-3.6.1-1.fc17.x86_64

How reproducible:
Always, at least on my machine.

Steps to Reproduce:
1. Boot into 3.6.1.
2. Logon.
3. Wait for idle time to elapse.

  
Actual results:
Screensaver blanks and locks screen, but does not shutdown monitor.

Expected results:
Screensaver blanks and locks screen, and shuts down monitor.

Additional info:
The only difference is booting between the two kernel versions. When booting the older kernel-3.5.6-1.fc17.x86_64, it works as expected.  When booting the newer kernel-3.6.1-1.fc17.x86_64, it fails.
Comment 1 Joseph D. Wagner 2012-10-15 02:34:17 EDT 
Created attachment 627214 [details]
System Information

Information about my system.
Comment 2 Joseph D. Wagner 2012-10-19 17:04:32 EDT 

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