Don't update to nVidia 180.35!

[3vi1]

If you haven't already learned the hard way, you may not want to update to 180.35 just yet:

https://bugs.launchpad.net/ubuntu/+s...80/+bug/335879

Lots of people are having issues. I put up with them for a couple of days, but finally resorted to backing down to 180.29 to fix things.

[Aries K]

Re: Don't update to nVidia 180.35!

See my thread here as well. http://kubuntuforums.net/forums/inde...opic=3102038.0

The workaround is like you said sticking with 180.29. For those of you who already have the 180.35 version and do not feel like downgrading, you can just wait until the next version of the Nvidia driver and reboot and shutdown by using the terminal which does not bother most people as long they do not have to use the power button (which is annoying). This seems to be effecting a wide range of KDE distros (not just Kubuntu) so maybe with all of this noise Nvidia will quickly release the next reliable version of the Nvidia driver soon.

To restart:
Code:

sudo reboot

To shutdown:
Code:

sudo shutdown -h now

[3vi1]

Re: Don't update to nVidia 180.35!

Actually, to shutdown, all you need to do is "sudo halt".

I never had shutdown problems. The main irritation for me is that it was causing Compiz to hang sometimes on startup, and things wouldn't exit properly so I'd get a lot of defunct processes. If I left the screensaver going for a few hours and came back, sometimes the KDE panel would be totally messed up, or the plasmoids on the desktop would stop updating. Add that to ctrl-c/ctrl-z being completely broken in my (yakuake) terminal, and it's pretty much unbearable.

I had the exact same symptoms on two systems, one 64-bit and one 32-bit (one with a 7800GT and one with a 9800GTX+).

As long as people haven't cleaned out their apt cache, they can downgrade with something like:

cd /var/cache/apt/archives
sudo dpkg -i nvidia-glx-180_180.29-0ubuntu2_amd64.deb nvidia-180-kernel-source_180.29-0ubuntu2_amd64.deb nvidia-glx-180-dev_180.29-0ubuntu2_amd64.deb

(You only need to include the last one if you have the dev libraries installed). 32-bit systems will need to change the package names to the 32-bit equivalents.

[3vi1]

Re: Don't update to nVidia 180.35!

nVidia's acknowledged and found the problem. They're promising a fix in the next release.

http://www.nvnews.net/vbulletin/show...5&postcount=46

[Aries K]

Re: Don't update to nVidia 180.35!

nVidia's acknowledged and found the problem. They're promising a fix in the next release.

http://www.nvnews.net/vbulletin/show...5&postcount=46

Glad to hear, I'll just stick with the .35 one until the next update. Thanks for the heads up.

[dibl]

Re: Don't update to nVidia 180.35!

Confirm the problem. Oddly, it doesn't seem to impair the performance of the system in any way, except for the inability to log out. It doesn't appear to happen in kde 3.5 either (on my sidux system), just KDE 4.

[musta ruhtinas]

Re: Don't update to nVidia 180.35!

Same case here. Lots of zombie processes, no performance decrease. Haven't experienced so far the logout issues.

[Aries K]

Re: Don't update to nVidia 180.35!

Same case here. Lots of zombie processes, no performance decrease. Haven't experienced so far the logout issues.

Getting a lot of zombie processes as well. Glad to hear I am not the only one. Hopefully the zombie processes go away after the next Nvidia release.

[DERG]

Re: Don't update to nVidia 180.35!

Here's another log in the trials & tribulations of a newbie;

http://kubuntuforums.net/forums/inde...opic=3102143.0

Thankfully, I was bailed out once again! But, with each mis-step there's valuable knowledge learned.
Had I been able to find v180.11, like I use on the Ubuntu 8.10 partition, I wouldn't of tried that in the first place. This might be because alpha 5 is a new install for me. As suggested above, it's probably best to wait until the fix is made.