nvidia 173.x drivers caused a crash

[Triplejolt]

Unable to install nVidia drivers for my nVidia Quadro NVS 140M onboard GPU. 173.x crashes under installation and the 180.x only gives me a black screen. I have to reset the xorg.conf and use the default VESA driver to be able to see anytning on screen.

Ubuntu 9.04
Lenovo T61

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-removal script returned error exit status 2
NonfreeKernelModules: nvidia
Package: nvidia-glx-180 180.44-0ubuntu1
ProcVersion: Linux version 2.6.28-15-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #52-Ubuntu SMP Wed Sep 9 10:49:34 UTC 2009
SourcePackage: nvidia-graphics-drivers-180
Title: package nvidia-glx-180 180.44-0ubuntu1 failed to install/upgrade: subprocess post-removal script returned error exit status 2
Uname: Linux 2.6.28-15-generic i686

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
     Subsystem: Lenovo Device [17aa:20b1]
01:00.0 VGA compatible controller [0300]: nVidia Corporation Quadro NVS 140M [10de:0429] (rev a1)
     Subsystem: Lenovo Device [17aa:20d8]

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[izar (izar00)]

i have a similar bug.
i tried installing 173 driver on natty because of another bug. https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144.
x didnt start. had to use vesa to change the driver back.
i think the same thing was reported by someone else in the spoken bug. (https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144/comments/39 and https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/753144/comments/55)

i think this bug isnt "fixed" but simply too old and it doesnt interest most people anymore.