Closing lid on kernels 2.6.30-9+ results in blank display on open

[Mike Kaplinskiy]

Binary package hint: xserver-xorg

After closing the lid of my display, when I open it again, nothing shows up. On -10 it takes a few tries but happens relatively quickly. Also I can only reproduce once I log into xorg, and only while in xorg.

ProblemType: Bug
Architecture: i386
Date: Sun Jun 28 22:50:07 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=9766054e-2138-42de-82d4-87cd243f6d58
MachineType: FUJITSU LifeBook T4215
Package: linux-image (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.30-8-generic root=UUID=cd5909b1-b49c-42a2-9baa-912b638d66d8 ro quiet splash crashkernel=384M-2G:64M,2G-:128M
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
RelatedPackageVersions:

SourcePackage: linux-meta
Uname: Linux 2.6.30-8-generic i686
dmi.bios.date: 08/21/2007
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNB1B9
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: AE5CJ1E526550000
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd08/21/2007:svnFUJITSU:pnLifeBookT4215:pvr:rvnFUJITSU:rnFJNB1B9:rvr:cvnAE5CJ1E526550000:ct10:cvr:
dmi.product.name: LifeBook T4215
dmi.sys.vendor: FUJITSU

[Robert Hooker (sarvatt)]

A drop-in replacement for the intel driver in karmic that contains the fix is available in this PPA. If it works for you, please mention it so we can get it updated in karmic.

https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates

[Mike Kaplinskiy (mike-kaplinskiy)]

Just tested - yes, this fixes the problem. The screen sometimes flashes white when you open/close too quickly, but at least it no longer freezes/whatever it did.

No errors in xorg/kernel logs as far as I could see either.

My opengl test (pixel city: http://code.google.com/p/pixelcity/, through wine) yielded no actual buildings, which is slightly weird, but I have not tested this behavior on the original driver. Should I open another bug for that?

[Bryce Harrington (bryce)]

Hi Mike, yes open a new bug on that, but only if you can reproduce the behavior on Karmic.

Since the version of driver in x-updates is already in karmic, I think we can close this bug as resolved now.