apport-gpu-error-intel.py crashed with KeyError in __getitem__()

[Broomer68]

Binary package hint: xserver-xorg-video-intel

reported after restart after failing battery in suspend

ProblemType: Crash
Architecture: i386
Date: Thu Mar 18 05:07:07 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
InterpreterPath: /usr/bin/python2.6
MachineType: MICRO-STAR INTERNATIONAL CO., LTD U-100
Package: xserver-xorg-video-intel 2:2.9.1-1ubuntu13
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=a3cefe7c-8332-49f0-b7b9-6ced91ffebb3 ro splash vga=771 quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/share/apport/apport-gpu-error-intel.py']
SourcePackage: xserver-xorg-video-intel
Title: apport-gpu-error-intel.py crashed with KeyError in __getitem__()
Uname: Linux 2.6.32-16-generic i686
UserGroups:

dmi.bios.date: 01/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: U-100
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: Ver.001
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.version: Ver.001
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd01/16/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:
dmi.product.name: U-100
dmi.product.version: Ver.001
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-16-generic

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #539533, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.