[gm45] Houdini crashes whenever I try to do anything.

[Sean Simon]

Binary package hint: xserver-xorg-video-intel

Whenever I try to use any of the tools in Houdini, the program crashes, leaving a window that says "fatal Error: Data saved to /tmp/inky.2837.hip

and I get a terminal window that says "(sent by pid -1)~$ 3177: Fatal error: Segmentation Fault"

I imagine it's an issue with the video driver because the only other instance I've ever heard of something like this was on a winXP 64 where it was a driver issue.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAGrxShAAAAAAESAQOQGhB4ClDFmFhSjiclUFQAAAABAQEBAQEBAQEBAQEBAQEB6hoAflAgEDAwIDYABaMQAAAa6hoAflAgEDAwIDYABaMQAAAaAAAA/gBGMzI1RoBCMTIxRVcwAAAAAAAAAAAAAAAAAAEBCiAgAL4=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Thu Oct 28 17:15:01 2010
DkmsStatus:
 bcmwl, 5.60.48.36+bdcom, 2.6.35-19-generic, x86_64: built
 bcmwl, 5.60.48.36+bdcom, 2.6.35-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: Dell Inc. Latitude XT2
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=f8185433-f242-4764-b081-5744204425f9 ro quiet quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel
dmi.bios.date: 05/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd05/07/2009:svnDellInc.:pnLatitudeXT2:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude XT2
dmi.sys.vendor: Dell Inc.
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0252]

[bugbot (bugbot)]

Hey Sean,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.