apport-gpu-error-intel.py crashed with KeyError in __getitem__()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xserver-
X crashes when I dock or undock my laptop.
Steps to reproduce:
1. Boot laptop while removed from docking station
2. Log in to the desktop
3. Put laptop to sleep and close lid
4. Put laptop with closed lid on docking station
5. Boot laptop
Result: Laptop wakes up and presents you with login screen.
Expected result: the running desktop should display on the new monitor.
I've also had the problem happen when I close the lid and put the laptop on the docking station without putting the system to sleep (I have sleep on lid close disabled).
ProblemType: Crash
Architecture: amd64
Date: Tue Mar 16 16:28:51 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
MachineType: Hewlett-Packard HP EliteBook 6930p
Package: xserver-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: xserver-
Title: apport-
Uname: Linux 2.6.32-16-generic x86_64
UserGroups:
dmi.bios.date: 12/08/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCU Ver. F.16
dmi.board.name: 30DB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.2A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP EliteBook 6930p
dmi.product.
dmi.sys.vendor: Hewlett-Packard
system:
distro: Ubuntu
codename: lucid
architecture: x86_64
kernel: 2.6.32-16-generic
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.