Bug 527964 - "your display server is broken" notification from gnome-power-manager
Summary: "your display server is broken" notification from gnome-power-manager
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL: http://blogs.gnome.org/hughsie/2009/0...
Whiteboard:
: DRIOpenDRMMaster, symbol:, undefined 543877 545481 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-08 12:00 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2018-04-11 14:30 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 07:32:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
sosreport of affected system (1.64 MB, application/x-xz)
2010-03-15 13:33 UTC, J.H.M. Dassen (Ray)
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 423694 0 None None None Never

Description Dominik 'Rathann' Mierzejewski 2009-10-08 12:00:10 UTC
Description of problem:
gnome-power-manager displays an icon in the notification area which, after hovering the cursor over it, says:
"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."

Version-Release number of selected component (if applicable):
1.7.0-1.fc12

How reproducible:
Always

Steps to Reproduce:
1. wait until the idle timeout expires

Comment 1 Matěj Cepl 2009-10-08 13:14:48 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Could we get an output of the command

rpm -qa \*power\* xorg-x11\*server\*

(these are real backslashes and asterisks, not fancy mean of bolding text or anything)

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Dominik 'Rathann' Mierzejewski 2009-10-09 13:08:12 UTC
Here is the requested information:

DeviceKit-power-011-0.1.20090914git.fc12.x86_64
gnome-power-manager-2.28.0-1.fc12.x86_64
xorg-x11-server-common-1.7.0-1.fc12.x86_64
xorg-x11-server-utils-7.4-11.fc12.x86_64
xorg-x11-server-Xorg-1.7.0-1.fc12.x86_64

Comment 3 Matěj Cepl 2009-10-09 15:55:23 UTC
Richard, any thoughts on this?

Comment 4 Matěj Cepl 2009-11-05 17:17:38 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 5 Bug Zapper 2009-11-16 13:24:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 James 2009-11-20 23:02:35 UTC
Just seen it with:

gnome-power-manager-2.28.1-5.fc12.x86_64
xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64

Comment 7 Matěj Cepl 2009-12-04 21:02:22 UTC
*** Bug 543877 has been marked as a duplicate of this bug. ***

Comment 8 Matěj Cepl 2009-12-08 23:24:04 UTC
*** Bug 517299 has been marked as a duplicate of this bug. ***

Comment 9 Matěj Cepl 2009-12-08 23:41:58 UTC
*** Bug 545481 has been marked as a duplicate of this bug. ***

Comment 10 udo 2009-12-09 03:50:17 UTC
Wasn't this an X server issue?

Comment 11 Christopher Beland 2010-02-08 07:07:49 UTC
This happened to me with:

gnome-power-manager-2.28.2-2.fc12.i686
DeviceKit-power-014-1.fc12.i686
xorg-x11-server-common-1.7.4-6.fc12.i686
xorg-x11-server-utils-7.4-13.fc12.i686
xorg-x11-server-Xorg-1.7.4-6.fc12.i686

The display went blank for no apparent reason while I was reading a web page, and when I hit the keyboard or mouse (I don't remember which) I got the icon and the reported error message.

Comment 12 James 2010-02-14 09:14:04 UTC
Unexpected blanking and message from g-p-m continues sporadically with:

xorg-x11-server-Xorg-1.7.4.902-1.fc12.x86_64
gnome-power-manager-2.28.3-1.fc12.x86_64
DeviceKit-power-014-1.fc12.x86_64

(in my case, seen just after resuming from suspend).

Comment 13 Matt McCutchen 2010-03-10 05:08:36 UTC
On several occasions I have seen this icon appear after not using the keyboard or mouse for a few minutes, while the display remains on.  If I move the mouse, the icon immediately disappears.  Today I was lucky enough to have the mouse in the right place so that the tooltip appeared and I learned about the issue.

I'm using a Dell Latitude D620 with the nvidia proprietary driver from RPM Fusion.  Packages:

DeviceKit-power-014-1.fc12.x86_64
gnome-power-manager-2.28.2-2.fc12.x86_64
powertop-1.11-3.fc12.x86_64
xorg-x11-server-Xorg-1.7.5.901-1.fc12.x86_64
xorg-x11-server-common-1.7.5.901-1.fc12.x86_64
xorg-x11-server-utils-7.4-13.fc12.x86_64

Comment 14 J.H.M. Dassen (Ray) 2010-03-15 13:33:09 UTC
Created attachment 400212 [details]
sosreport of affected system

I'm occasionally seeing this issue on a fully updated Fedora 12 system (attaching sosreport).

Comment 15 Michael Convey 2010-03-30 15:08:29 UTC
I'm having the same problem. Here is my info:

gnome-power-manager-2.28.2-2.fc12.i686
xorg-x11-server-utils-7.4-13.fc12.i686
DeviceKit-power-014-1.fc12.i686
xorg-x11-server-common-1.7.6-1.fc12.i686
xorg-x11-server-Xorg-1.7.6-1.fc12.i686

Here is my kernel version:
2.6.32.9-70.fc12.i686

I see a green running man icon in the panel. When I hold my cursor over the icon, a text box shows the following message: 

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.

Comment 16 Joachim Frieben 2010-04-30 05:27:47 UTC
Issue also applies to an ATI X800 (R430) video adapter on a fully updated F12 system including packages:
gnome-power-manager-2.28.2-2.fc12.x86_64
xorg-x11-drv-ati-6.13.0-1.fc12.x86_64
xorg-x11-server-Xorg-1.7.6-4.fc12.x86_64

Comment 17 András Szilárd 2010-05-12 16:22:30 UTC
After restoring from hibernation I experience the same issue.
$ rpm -qa \*power\* xorg-x11\*server\*
xorg-x11-server-Xorg-1.7.6-3.fc12.x86_64
DeviceKit-power-014-1.fc12.x86_64
xorg-x11-server-common-1.7.6-3.fc12.x86_64
xorg-x11-server-utils-7.4-13.fc12.x86_64
gnome-power-manager-2.28.2-2.fc12.x86_64
xorg-x11-server-Xnest-1.7.6-3.fc12.x86_64
powertop-1.11-3.fc12.x86_64

Comment 18 Jasper Siepkes 2010-08-03 21:35:55 UTC
I ran into this for the first time. I have been running F12 (fully updated) for a couple of months now with an ATI Radeon HD 4870. All of a sudden the screen went black for a second and then came back online with the "If you can see this text etc. etc." message.

$ rpm -qa \*power\* xorg-x11\*server\*
xorg-x11-server-utils-7.4-13.fc12.x86_64
DeviceKit-power-014-1.fc12.x86_64
xorg-x11-server-common-1.7.6-4.fc12.x86_64
gnome-power-manager-2.28.2-2.fc12.x86_64
xorg-x11-server-Xorg-1.7.6-4.fc12.x86_64

Comment 19 Robert Story 2010-08-09 13:49:41 UTC
Noticed an odd icon in my panel today which led me to the blog and then to this bug report. Don't know if this is new, or I just never noticed it until today. The machine is a laptop which has been up 15 days and only put to sleep occasionally.

# rpm -qa \*power\* xorg-x11\*server\*
xorg-x11-server-common-1.7.6-4.fc12.ppc
xorg-x11-server-Xorg-1.7.6-4.fc12.ppc
gnome-power-manager-2.28.2-2.fc12.ppc
DeviceKit-power-014-1.fc12.ppc
powerpc-utils-1.2.0-1.fc12.ppc
xorg-x11-server-utils-7.4-13.fc12.ppc

Comment 20 Bug Zapper 2010-11-04 09:34:49 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 21 Bug Zapper 2010-12-04 07:32:05 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.


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