[gm45] gnome-power-manager reports a broken display server after random screen blanking

[ais523]

Binary package hint: xorg

My laptop screen (I'm using a Toshiba Satellite, I'm not sure which version) randomly went blank for around half a second, then turned back on again; a message was displayed in the notification area from gnome-power-manager, as follows:
"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." (Expected behavior is no screen blanking, and no notification message.) The blog post listed implies that the message in question appears immediately after gnome-power-manager has worked around a known X bug, and that the error should be reported upstream. However, the comments to the blog also imply that the patches in question have been applied to Ubuntu's X server already (I'm running X version 1.6.4); so it's also possible the bug is in gnome-power-manager causing a spurious notification (although that doesn't explain the screen going blank), or maybe even somewhere else affecting both components. This problem's happened exactly twice to me, seemingly for no reason (ugh intermittent bugs); the only unusual thing I was doing restoring from hibernation, rather than rebooting as usual. Sorry I don't really have much more of an idea of what's going on; if more information's needed, ask and I'll try to provide it.

ProblemType: Bug
Architecture: i386
Date: Mon Jan 11 09:54:21 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: TOSHIBA SATELLITE T110
Package: xorg 1:7.4+3ubuntu10
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=ce6fddb1-91cd-4100-b7d6-8daa69e7ffd8 ro quiet splash
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.31-17-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 09/29/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.70
dmi.board.name: SATELLITE T110
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/29/2009:svnTOSHIBA:pnSATELLITET110:pvrPST1AE-00K00GEN:rvnTOSHIBA:rnSATELLITET110:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: SATELLITE T110
dmi.product.version: PST1AE-00K00GEN
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-17-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Toshiba America Info Systems Device [1179:ffe1]

[Gergely Csépány (cheoppy)]

It just happened on my Lenovo Y450 laptop with Intel Mobile 4 graphics. My screen blanked once, I didn't notice anything else, nothing in the dmesg or Xorg log.

[ais523 (ais523)]

Hibernation appears to be irrelevant; it happened again to me on a clean boot. Additionally, there was a longer wait before the screen unblanked this time (until I moved the mouse; it's probable that it lasts until either any input, or anything that would dismiss a screensaver/unblank a screen). As with the last time it happened, and with cheoppy's report, there's nothing at all relevant in any of the logs I checked, just the screen blanking and unblanking, and the notification area warning of a bug.

[Vikram Dhillon (dhillon-v10)]

This issue was reported against karmic, so can you confirm if this issue exists with the most recent Lucid Lynx 10.04 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/lucid/ . Thanks in advance.

[ais523 (ais523)]

I can't confirm in any direction, as this hasn't happened to me even on karmic for over a month. I'm not sure if the bug's fixed tiself or if it just isn't being triggered, though. Possibly it's best to mark it as WORKSFORME or whatever until or unless it recurs.

[Vikram Dhillon (dhillon-v10)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/24/2010 10:22 PM, ais523 wrote:
> I can't confirm in any direction, as this hasn't happened to me even on
> karmic for over a month. I'm not sure if the bug's fixed tiself or if it
> just isn't being triggered, though. Possibly it's best to mark it as
> WORKSFORME or whatever until or unless it recurs.
>

Since you are the original bug reporter and seems to you that the bug
was fixed, I'd say it was only a temporary problem, so marking it
invalid, if the problem comes up again, please change the status back to
new. Thanks.

 status invalid

- --
Regards,
Vikram Dhillon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuIsoEACgkQcoBavQdRHcy/NQCg3PS9m6m8wpX6znJB35Ih1LyC
LxoAoNetpEvstP0sKMo2W6X5oQN3U3yD
=qeai
-----END PGP SIGNATURE-----

[VF (fviktor)]

I also had this exact issue and my error log has been recorded for another bug already, so just adding the link to that:

http://launchpadlibrarian.net/43198861/XsessionErrors.txt

[bugbot (bugbot)]

Kernel bug perhaps. Do you still see this problem in natty? If so,
please run apport-collect <bug-number> to update with natty log files.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.