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

[Gabriel Bauman]

Binary package hint: xserver-xorg-video-intel

Not at all sure what triggered this. If I remember right, this first appeared after a resume from hibernate.

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 17 10:41:58 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: madwifi, 0.4119, 2.6.32-16-generic, x86_64: installed
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100223.2)
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard HP Mini 210-1000
Package: xserver-xorg-video-intel 2:2.9.1-1ubuntu13
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-16-generic root=/dev/mapper/system-root ro 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 x86_64
UserGroups:

dmi.bios.date: 12/30/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3660
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 48.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd12/30/2009:svnHewlett-Packard:pnHPMini210-1000:pvr04A4100000202000000300000:rvnHewlett-Packard:rn3660:rvr48.10:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Mini 210-1000
dmi.product.version: 04A4100000202000000300000
dmi.sys.vendor: Hewlett-Packard
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 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.