Bug 547210

Summary:	IDELCOUNTER/DPMS bug in X11 server
Product:	[Fedora] Fedora	Reporter:	Bojan Smojver <bojan>
Component:	gnome-power-manager	Assignee:	Richard Hughes <richard>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12	CC:	mcepl, richard, xgl-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-04 01:41:59 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:

Description Bojan Smojver 2009-12-14 01:27:31 UTC

Description of problem:
When running a gnome session, gnome-power-manager puts an icon in the toolbar with a hover over message which reads:

"Session active, not inhibited, screen idle. If you can see this text, your display server is broken and you should notify your distributor. Please see http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/ for more information"

If you go to: 

http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/

This is a straight up X server, running on Intel hardware (Dell Inspiron 6400), with compiz (i.e. not VNC).

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.7.1-7.fc12.i686

How reproducible:
Sometimes.

Steps to Reproduce:
1. Start a gnome session.
2. Use it, sometime for days with hibernate/thaw in between.
3. This message comes up, screen starts being dimmed randomly etc.
  
Actual results:
Message pops up, screen being dimmed randomly.

Expected results:
Brightness should remain as it was set.

Additional info:

Comment 1 Bojan Smojver 2010-03-08 07:31:10 UTC

Still a problem with:

kernel-2.6.32.9-67.fc12.i686
xorg-x11-server-Xorg-1.7.5-5.fc12.i686

Just FYI.

Comment 2 Matěj Cepl 2010-03-11 23:05:42 UTC

That message is slander and should be removed a long time ago. Reassigning to g-p-m.

Comment 3 Bojan Smojver 2010-03-11 23:37:11 UTC

(In reply to comment #2)
> That message is slander

:-))

Comment 4 Bug Zapper 2010-11-04 03:25:42 UTC

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 5 Bug Zapper 2010-12-04 01:41:59 UTC

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.