nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed

Bug #335879 reported by Mark Greenwood
108
This bug affects 10 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Medium
Alberto Milone
Nominated for Jaunty by 3vi1

Bug Description

After installing the nvidia driver version 180.35, I can no longer log out of KDE.

If I look in the process list I can see a long list of defunct processes that are all children of ksmserver. The only workaround seems to be to log in with an empty session (i.e disable 'Restore Previous session').

It seems that somehow the nvidia driver is causing this problem. There's a long thread on the nvnews forum here :
http://www.nvnews.net/vbulletin/showthread.php?t=128992

The cure seems to be to revert back to 180.29, but it's far from obvious how to do this.

Needs Package Created for: nvidia driver 180.37
nVidia Driver URL: ftp://download.nvidia.com/XFree86/

Revision history for this message
Ben Crisford (bencrisford) wrote :

Firstly, thank you for reporting this bug.

However, this bug report is incomplete. Please specify which distrobution you are using.

Thanks,
Ben

Revision history for this message
Sel Goona (alieneye) wrote :

> The only workaround seems to be to log in with an empty session ...

THX, this "fix" at least the logout / reboot issue, but the zombie processes remains!

System: Kubuntu Jaunty Alpha 5 with nvidia-180.35 (GeForce7300GT/AGP)

Revision history for this message
Mark Greenwood (fatgerman) wrote :

My apologies, I was too hasty in hitting the submit button..

I am running Kubuntu Jaunty Alpha 4, kept fully updated up to 28 Feb 2009.

My workaround does allow me to log in and out but as Sel says above, the zombie processes remain an issue in that if, once logged in, I try to start Klipper (from "Run Command") it immediately zombifies. The problem seems to affect anything that runs in the system tray except for KMix - i.e. klipper, kopete, nepomuk.

Revision history for this message
Sel Goona (alieneye) wrote :

There was no driver update, but it seems that the problem slowly dissolves here on my PC. If I finish a Qt4 program, it result still in a zombie process, but now this prozess quit independent after a short time.

Curious, maybe this is not only a Nvidia issue?

Revision history for this message
Sel Goona (alieneye) wrote :

Addendum: The improvement sadly occurs only, when I start with a empty session.

Revision history for this message
Norberto Bensa (nbensa) wrote :

Hello,

This is happening to me too after Friday update on Kubuntu/Jaunty.

I can't logout/shutdown/restart. I need to press the power button on my laptop.

I can't use CTRL+C in konsole/yakuake. It does nothing.

I can't use CTRL+D in konsole/yakuake. Doing so results in a new zombie (bash)

I have many zombie processes:

zoolook@melnitz:~$ ps ax | grep defun
 4408 ? Z 0:00 [nepomukserver] <defunct>
 4412 ? Z 0:00 [nepomukservices] <defunct>
 4413 ? Z 0:00 [nepomukservices] <defunct>
 4414 ? Z 0:00 [nepomukservices] <defunct>
 4415 ? Z 0:00 [nepomukservices] <defunct>
 4416 ? Z 0:00 [kopete] <defunct>
 4418 ? Z 0:00 [yakuake] <defunct>
 4420 ? Z 0:00 [kmix] <defunct>
 4429 ? Z 0:00 [kde4] <defunct>
 4445 ? Z 0:00 [python] <defunct>
 4449 ? Z 0:00 [python] <defunct>
 4450 ? Z 0:00 [amarok] <defunct>

zoolook@melnitz:~$ dpkg -l | grep nvidia
ii nvidia-173-modaliases 173.14.16-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-180-kernel-source 180.35-0ubuntu1 NVIDIA binary kernel module source
ii nvidia-180-libvdpau 180.35-0ubuntu1 Video Decode and Presentation API for Unix
ii nvidia-180-modaliases 180.35-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-71-modaliases 71.86.08-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-96-modaliases 96.43.10-0ubuntu1 Modaliases for the NVIDIA binary X.Org drive
ii nvidia-common 0.2.9 Find obsolete NVIDIA drivers
ii nvidia-glx-180 180.35-0ubuntu1 NVIDIA binary Xorg driver
ii nvidia-settings 180.25-0ubuntu1 Tool of configuring the NVIDIA graphics driv

How do I revert to nvidia-180.29? Is there any way to specify a package version with "apt*" or should I use "dpkg -i"?

Thanks
Norberto

Revision history for this message
Mark Greenwood (fatgerman) wrote :

I found the 180.29 versions of the following packages in var/apt/cache and downgraded:

nvidia-180-glx
nvidia-180-kernel-source
nvidia-180-libdvpau
nvidia-180-modaliases

The problem is cured now I've done this.

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

I'm seeing similar problems since the 180.35 update. Particularly the defunct processes, and the inability to use Ctrl-C in yakuake. Logging in now takes a lot longer sometimes now results in a blank screen and I have to restart compiz to get everything running.

I think I'm going to see if I still have the 180.29 packages in cache and downgrade like Mark.

Linux mars 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux

Revision history for this message
getaceres (getaceres) wrote :

I'm having this problem also. I hope NVidia will have a fix soon...

Revision history for this message
Søren Holm (sgh) wrote :

I bet it is not a nVidia issue. It also happenens with with the vesa-driver. But then again on the pc I'm loggently logged in on it does not happen. It run with the intel-driver.

Revision history for this message
getaceres (getaceres) wrote :

I've downgraded to 180.29 and it seems to be fixed. I'll wait until next NVidia release.

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

I can confirm the problem on 64-bit Jaunty Kubuntu and an Asus EN9800GTX+.

After the 180.35 update, login would occasionally leave me at a black screen until I restarted KWin or Compiz via yakuake (processes were loading, the desktop just wasn't showing). I also began noticing lots of defunct unkillable processes (wget, for instance) that didn't seem related to any recent updates and yakuake would not let me exit a shell or use ctrl+c/ctrl+z in any of the sessions. This was 100% recreate-able on every login.

Backleveling to 180.29 causes the issues to go away completely.

Linux mars 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:27:53 UTC 2009 x86_64 GNU/Linux

Revision history for this message
Søren Holm (sgh) wrote :

I take my comment back. It's the nvidia driver allright. real strange.

Revision history for this message
Fabien Meinnier (xenon341) wrote :

Same problem, Kubuntu Jaunty Alpha4 daily updated...
Can someone post the 189.29 for AMD64 arch please ?

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

This problem doesn't seem to be restricted to KDE4. People using Gnome are complaining as well: http://www.nvnews.net/vbulletin/showthread.php?t=129284

I did a test and upgraded another 32-bit system and see the same problems, so it's not specific to architecture either. If I'm two-for-two on broken systems, then this must be pretty common, no?

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

Confirming due to numerous reports.

Changed in nvidia-graphics-drivers-180:
status: New → Confirmed
Revision history for this message
HumpBack (humpback) wrote :

Could any one with the 180.29 drivers please post the files somewhere?

Revision history for this message
Søren Holm (sgh) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

it has been posted in an earlier post.

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote : Re: nvidia driver 180.35 breaks KDE 4

Looks like nVidia has tracked down the problem and is promising a fix in the next release. No idea when that will be, though.

http://www.nvnews.net/vbulletin/showthread.php?p=1946545#post1946545

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

Bugs reports for other symptoms caused by 180.35 are still being filed. Would it be possible for someone in charge to mark 180.35 as held back and put 180.29 back in place?

Revision history for this message
SRElysian (srelysian) wrote :

first, I'd like to thank getaceres for providing the 180.29 packages, they fixed all the bugs I currently have with jaunty. Second, I agree with 3vil, they should put .29 back until nvidia fixes the problem because the current drivers break numerous parts of kde4.

Revision history for this message
Jo Shields (directhex) wrote :
Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

As mentioned in my earlier post with the link to the same thread, there's no telling when they will release the next driver. It could be two weeks or two months.

My suggestion to hold back 180.35 was thinking about the worst case scenario: Jaunty goes live and 180.35 is still the latest package. In the meantime, I suggest everyone who wants to continue testing the other parts of Jaunty should work around this by pinning the nvidia packages.

Adding the following to your /etc/apt/preferences (may need to be created) file will let you get the other updates without worrying about 180.29 getting overwritten by 180.35:

Package: nvidia-glx-180
Pin: release
Pin-Priority: 999

Package: nvidia-180-kernel-source
Pin: release
Pin-Priority: 999

Package: nvidia-glx-180-dev
Pin: release
Pin-Priority: 999

Revision history for this message
Norberto Bensa (nbensa) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

On Thu, Mar 5, 2009 at 11:41 AM, 3vi1 <email address hidden> wrote:
> Package: nvidia-glx-180
> Pin: release
> Pin-Priority: 999
>
> Package: nvidia-180-kernel-source
> Pin: release
> Pin-Priority: 999
>
> Package: nvidia-glx-180-dev
> Pin: release
> Pin-Priority: 999

What's the difference between "pinning" with this file and "aptitude
hold ..." ?

Thanks,
Norberto

Revision history for this message
getaceres (getaceres) wrote : Re: nvidia driver 180.35 breaks KDE 4

I think also that 180.35 drivers must be removed from the repository. There is no guarantee that the newer drivers will come out before Jaunty release. 180.29 should be the drivers by default unless a new version comes out before April.

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

I also added this one since it was in the collection of packages provided
here, didn't want anything to get screwed up with mismatched versions:

Package: nvidia-180-libvdpau
Pin: release
Pin-Priority: 999

On Thu, Mar 5, 2009 at 8:41 AM, 3vi1 <email address hidden> wrote:

> As mentioned in my earlier post with the link to the same thread,
> there's no telling when they will release the next driver. It could be
> two weeks or two months.
>
> My suggestion to hold back 180.35 was thinking about the worst case
> scenario: Jaunty goes live and 180.35 is still the latest package. In
> the meantime, I suggest everyone who wants to continue testing the other
> parts of Jaunty should work around this by pinning the nvidia packages.
>
> Adding the following to your /etc/apt/preferences (may need to be
> created) file will let you get the other updates without worrying about
> 180.29 getting overwritten by 180.35:
>
> Package: nvidia-glx-180
> Pin: release
> Pin-Priority: 999
>
> Package: nvidia-180-kernel-source
> Pin: release
> Pin-Priority: 999
>
> Package: nvidia-glx-180-dev
> Pin: release
> Pin-Priority: 999
>
> --
> nvidia driver 180.35 breaks KDE 4
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see a long list of defunct processes
> that are all children of ksmserver. The only workaround seems to be to log
> in with an empty session (i.e disable 'Restore Previous session').
>
> It seems that somehow the nvidia driver is causing this problem. There's a
> long thread on the nvnews forum here :
> http://www.nvnews.net/vbulletin/showthread.php?t=128992
>
> The cure seems to be to revert back to 180.29, but it's far from obvious
> how to do this.
>

Revision history for this message
Aaron Plattner (aplattner) wrote : Re: nvidia driver 180.35 breaks KDE 4

Please give 180.37 a try.

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

As soon as the packages pop up I'd be more than happy to test. I don't like
manually installing drivers because I don't think they work with dkms, and
with all the kernel upgrades kubuntu likes to push out, it's much easier for
me to let it do the work itself. My laptop's video is very tempermental, NV
drivers don't even work on it.. and my laptop becomes near-unusable unless I
custom my xorg file and force it into vesa (hell my ctrl-alt-F? consoles
still don't work on multiple distros). So once I see the packages come up, I
will be sure to try them out.

On Fri, Mar 6, 2009 at 4:25 PM, Aaron Plattner <email address hidden> wrote:

> Please give 180.37 a try.
>
> --
> nvidia driver 180.35 breaks KDE 4
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see a long list of defunct processes
> that are all children of ksmserver. The only workaround seems to be to log
> in with an empty session (i.e disable 'Restore Previous session').
>
> It seems that somehow the nvidia driver is causing this problem. There's a
> long thread on the nvnews forum here :
> http://www.nvnews.net/vbulletin/showthread.php?t=128992
>
> The cure seems to be to revert back to 180.29, but it's far from obvious
> how to do this.
>

Revision history for this message
Mark Greenwood (fatgerman) wrote : Re: nvidia driver 180.35 breaks KDE 4

Me too I'm afraid. I'm more than happy to test packages, but I don't want to go installing proprietary drivers in any other way. I've done that before and nearly destroyed a graphics card through overheating. Recent nvidia hardware simply needs correctly-functioning nvidia drivers and gets very temperamental otherwise. The lesson I've learned here is to buy laptops with Intel graphics chips :D

Revision history for this message
Tuomas Aavikko (taavikko) wrote :

Can't reproduce behaviour on up-to-date jaunty, while using 180.35 drivers.
Geforce 6800 GO...

Revision history for this message
getaceres (getaceres) wrote :

According to NVNews forums, the 180.37 drivers seems to fix the problems with signals. If you don't want to update the repositories with the new drivers without testing (although I doubt they will be worse than the 180.35 drivers), please, post here the updated packages and we will test it.
Installing the drivers trough the NVidia installer usually prevents further installations from packages to work correctly so to better test the drivers we need some packages.

Revision history for this message
Mark Greenwood (fatgerman) wrote :

Why not create some packages just for Jaunty, it's still in Alpha? I'll test them - so long as you notify this bug report (I've Pinned my packages to 180.29).

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

I agree, Jaunty is still in alpha anyway... they should pop them in untested
or something so we can have a crack at them. I doubt they could be any worse
than 180.35 anyway.

On Sat, Mar 7, 2009 at 12:20 PM, Mark Greenwood <email address hidden>wrote:

> Why not create some packages just for Jaunty, it's still in Alpha? I'll
> test them - so long as you notify this bug report (I've Pinned my
> packages to 180.29).
>
> --
> nvidia driver 180.35 breaks KDE 4
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see a long list of defunct processes
> that are all children of ksmserver. The only workaround seems to be to log
> in with an empty session (i.e disable 'Restore Previous session').
>
> It seems that somehow the nvidia driver is causing this problem. There's a
> long thread on the nvnews forum here :
> http://www.nvnews.net/vbulletin/showthread.php?t=128992
>
> The cure seems to be to revert back to 180.29, but it's far from obvious
> how to do this.
>

Revision history for this message
Noel J. Bergman (noeljb) wrote : Re: nvidia driver 180.35 breaks KDE 4

On Fri, Mar 6, 2009 at 4:25 PM, Aaron Plattner <email address hidden> wrote:

> Please give 180.37 a try.

Why don't you start to maintain test copies of the drivers and nvidia-settings in your PPA (https://bugs.launchpad.net/~aplattner/+archive/ppa)? You'll get faster feedback that way.

Revision history for this message
Norberto Bensa (nbensa) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

On Fri, Mar 6, 2009 at 7:25 PM, Aaron Plattner <email address hidden> wrote:
> Please give 180.37 a try.

Link?

I have no problems doing my own .debs, but all I get when I go to
nvidia.com is 180.29. Where's this 180.37 you're talking about?

Thanks

Revision history for this message
SRElysian (srelysian) wrote : Re: nvidia driver 180.35 breaks KDE 4

I added the tag "needs-packaging" in the hopes it will bring this particular problem to attention.

Jaunty really should have this driver updated, while we have a location to retrieve older driver packages and the means to lock them I don't believe that should be considered a "triage" or fix. To anyone with the means and interested in making the packages themselves:

FTP URL: ftp://download.nvidia.com/XFree86/

description: updated
Revision history for this message
Norberto Bensa (nbensa) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

On Sun, Mar 8, 2009 at 12:38 PM, SRElysian <email address hidden> wrote:
> FTP URL: ftp://download.nvidia.com/XFree86/

Thanks. I can confirm that 180.37 (amd64) fixes the zombies problem
(and ctrl+c, ctrl+d too.)

Revision history for this message
Norberto Bensa (nbensa) wrote : Re: nvidia driver 180.35 breaks KDE 4

I'm uploading debs I made for amd64.

Revision history for this message
Norberto Bensa (nbensa) wrote :
Revision history for this message
Norberto Bensa (nbensa) wrote :
Revision history for this message
Norberto Bensa (nbensa) wrote :
Revision history for this message
Norberto Bensa (nbensa) wrote :

Done. All you need to do to test this version is download the four files and then:

sudo dpkg -i *
sudo reboot

Revision history for this message
Michael Marley (mamarley) wrote :

There are also builds in my PPA for Jaunty and Intrepid. I always try to keep these up-to-date.

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

Thanks michael, I've been been using the drivers from your repos for about
an hour now, and so far they seem to fix the problem .35 produced. Hopefully
these will make it into the jaunty repos soon. Until then I think I will be
keeping your repos` in my sources list. :)

On Sun, Mar 8, 2009 at 12:43 PM, Michael Marley
<email address hidden>wrote:

> There are also builds in my PPA for Jaunty and Intrepid. I always try
> to keep these up-to-date.
>
> --
> nvidia driver 180.35 breaks KDE 4
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see a long list of defunct processes
> that are all children of ksmserver. The only workaround seems to be to log
> in with an empty session (i.e disable 'Restore Previous session').
>
> It seems that somehow the nvidia driver is causing this problem. There's a
> long thread on the nvnews forum here :
> http://www.nvnews.net/vbulletin/showthread.php?t=128992
>
> The cure seems to be to revert back to 180.29, but it's far from obvious
> how to do this.
>
> Needs Package Created for: nvidia driver 180.37
> nVidia Driver URL: ftp://download.nvidia.com/XFree86/
>

Revision history for this message
Blackpaw (blackpaw) wrote : Re: nvidia driver 180.35 breaks KDE 4

I can confirm 180.37 fixes the bug as well.

Had a clean Jaunty A5 install with no problems
Activated 180.35 via Jockey, and the zombies bug immediately surfaced
Deactivated 180.35 via jockey and manually installed 180.37
Zombie problem was fixed.

Revision history for this message
Mark Greenwood (fatgerman) wrote :

I can confirm the fix in 180.37 too. I used zoolook's packages. No zombies and I can log in and out. Thanks for creating those packages zoolook!

Revision history for this message
Norberto Bensa (nbensa) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4

On Sun, Mar 8, 2009 at 9:04 PM, Mark Greenwood <email address hidden>wrote:

> I can confirm the fix in 180.37 too. I used zoolook's packages. No
> zombies and I can log in and out. Thanks for creating those packages
> zoolook!
>

You're welcome. These are in fact my first packages for Ubuntu. It's nice to
know they worked :-)

Revision history for this message
Brian Murray (brian-murray) wrote : Re: nvidia driver 180.35 breaks KDE 4

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

Changed in nvidia-graphics-drivers-180:
importance: Undecided → Wishlist
Revision history for this message
Ciso (cisoprogressivo) wrote : Re: [needs-packaging] nvidia driver 180.35 breaks KDE 4

Solved for me with the PPA packages ;)

Revision history for this message
Michael Marley (mamarley) wrote :

I am glad that the PPA packages work, but this bug really needs to be fixed in Jaunty. Otherwise, it is going to get alot of trashy reviews and disgruntled users who (not knowing about the Nvidia problem) just think Jaunty stinks and they will go back to Intrepid.

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: [needs-packaging] nvidia driver 180.35 breaks KDE 4

Maybe someone should change the importance of this to something more than
"wishlist". While we all "wish" this would be fixed, I think it's a bit more
important than that since it effects pretty much everyone with an nvidia
card.

On Mon, Mar 9, 2009 at 6:18 AM, Michael Marley <email address hidden>wrote:

> I am glad that the PPA packages work, but this bug really needs to be
> fixed in Jaunty. Otherwise, it is going to get alot of trashy reviews
> and disgruntled users who (not knowing about the Nvidia problem) just
> think Jaunty stinks and they will go back to Intrepid.
>
> --
> [needs-packaging] nvidia driver 180.35 breaks KDE 4
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Confirmed
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see a long list of defunct processes
> that are all children of ksmserver. The only workaround seems to be to log
> in with an empty session (i.e disable 'Restore Previous session').
>
> It seems that somehow the nvidia driver is causing this problem. There's a
> long thread on the nvnews forum here :
> http://www.nvnews.net/vbulletin/showthread.php?t=128992
>
> The cure seems to be to revert back to 180.29, but it's far from obvious
> how to do this.
>
> Needs Package Created for: nvidia driver 180.37
> nVidia Driver URL: ftp://download.nvidia.com/XFree86/
>

Revision history for this message
Sel Goona (alieneye) wrote : Re: [needs-packaging] nvidia driver 180.35 breaks KDE 4

@Michael Marley:

THX U very much for 180.37. The driver in your ppa solves all the issues which have plagued me.

Revision history for this message
foox (fooxland) wrote :

thank you, it made my day....

Revision history for this message
Giuseppe Pennisi (giupenni78) wrote :

When in Jaunty Repository?

gp

Revision history for this message
Michael Marley (mamarley) wrote :

I think we should remove the needs-packaging tag and upgrade the importance to at least medium.

Revision history for this message
Giuseppe Pennisi (giupenni78) wrote :

Sure. This is not a request but a bug to be fixed.

gp

Revision history for this message
Michael Marley (mamarley) wrote :

I removed the tag and updated the title, but I do not have privileges to change the importance, so that will need to be done by someone else.

Changed in nvidia-graphics-drivers-180:
assignee: nobody → albertomilone
importance: Wishlist → Medium
status: Confirmed → In Progress
Revision history for this message
Alberto Milone (albertomilone) wrote :

FFE request: update the Nvidia driver to 180.37

Usecase: the driver is a bugfix prerelease of the stable driver. Furthermore I managed to add some fixes for other bugs too:

Here is the changelog:
  * New upstream release (LP: #335879).
    - Fixed a problem that caused signals to be blocked in some applications.
    - Fixed a problem that could cause Xid errors and display corruption in
      certain cases when OpenGL is used to render to redirected windows, for
      example when Java2D is used with the -Dsun.java2d.opengl=true option.
    - glGetStringi(GL_EXTENSIONS, i) no longer returns NULL in OpenGL 3.0
      preview contexts.
    - Fixed a problem that caused the screen to flicker momentarily when
      OpenGL applications exit unexpectedly on GeForce 6 and 7 series GPUs.
    - Fixed an X server crash when an X client attempts to draw trapezoids
      and RenderAccel is disabled.
    - Improved recovery from certain types of errors.
    - VDPAU updates:
      o Fixed corruption on some H.264 clips.
      o Update documentation.
      o Fixed VC-1 decoding on 64-bit platforms.
      o Improved handling of invalid H.264 streams.
      o Fixed a problem that caused surfaces to be marked as visible too
        early when the blit presentation queue is in use.
  * nvidia-glx-VER.preinst:
    - Remove diversion on /usr/lib32/libGL.so.1.2 to
      /usr/lib32/nvidia/libGL.so.1.2.xlibmesa instead of
      /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core (LP: #333550).
  * debian.binary/patches/nvidia-rt-compat.patch:
    - Restore compatibility with -rt kernels. Thanks to Alessio Igor Bogani
      for the patch.
  * debian/dkms.conf.in:
    - Make sure that the patch for -rt kernels is applied only to 2.6.28.x
      kernels.

Revision history for this message
Alberto Milone (albertomilone) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Nothing to approve here, it's a bug fix release. I'll unsubscribe -release and subscribe sponsors.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-180 - 180.37-0ubuntu1

---------------
nvidia-graphics-drivers-180 (180.37-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #335879).
    - Fixed a problem that caused signals to be blocked in some applications.
    - Fixed a problem that could cause Xid errors and display corruption in
      certain cases when OpenGL is used to render to redirected windows, for
      example when Java2D is used with the -Dsun.java2d.opengl=true option.
    - glGetStringi(GL_EXTENSIONS, i) no longer returns NULL in OpenGL 3.0
      preview contexts.
    - Fixed a problem that caused the screen to flicker momentarily when
      OpenGL applications exit unexpectedly on GeForce 6 and 7 series GPUs.
    - Fixed an X server crash when an X client attempts to draw trapezoids
      and RenderAccel is disabled.
    - Improved recovery from certain types of errors.
    - VDPAU updates:
      o Fixed corruption on some H.264 clips.
      o Update documentation.
      o Fixed VC-1 decoding on 64-bit platforms.
      o Improved handling of invalid H.264 streams.
      o Fixed a problem that caused surfaces to be marked as visible too
        early when the blit presentation queue is in use.
  * nvidia-glx-VER.preinst:
    - Remove diversion on /usr/lib32/libGL.so.1.2 to
      /usr/lib32/nvidia/libGL.so.1.2.xlibmesa instead of
      /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core (LP: #333550).
  * debian.binary/patches/nvidia-rt-compat.patch:
    - Restore compatibility with -rt kernels. Thanks to Alessio Igor Bogani
      for the patch.
  * debian/dkms.conf.in:
    - Make sure that the patch for -rt kernels is applied only to 2.6.28.x
      kernels.

 -- Alberto Milone <email address hidden> Fri, 13 Mar 2009 09:27:20 +0100

Changed in nvidia-graphics-drivers-180:
status: In Progress → Fix Released
Revision history for this message
Schmirrwurst (schmirrwurst) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed

when the update is going to be available in the repositories ?
----- Mail Original -----
De: "Launchpad Bug Tracker" <email address hidden>
À: <email address hidden>
Envoyé: Vendredi 13 Mars 2009 20h40:07 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed

This bug was fixed in the package nvidia-graphics-drivers-180 -
180.37-0ubuntu1

---------------
nvidia-graphics-drivers-180 (180.37-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #335879).
    - Fixed a problem that caused signals to be blocked in some applications.
    - Fixed a problem that could cause Xid errors and display corruption in
      certain cases when OpenGL is used to render to redirected windows, for
      example when Java2D is used with the -Dsun.java2d.opengl=true option.
    - glGetStringi(GL_EXTENSIONS, i) no longer returns NULL in OpenGL 3.0
      preview contexts.
    - Fixed a problem that caused the screen to flicker momentarily when
      OpenGL applications exit unexpectedly on GeForce 6 and 7 series GPUs.
    - Fixed an X server crash when an X client attempts to draw trapezoids
      and RenderAccel is disabled.
    - Improved recovery from certain types of errors.
    - VDPAU updates:
      o Fixed corruption on some H.264 clips.
      o Update documentation.
      o Fixed VC-1 decoding on 64-bit platforms.
      o Improved handling of invalid H.264 streams.
      o Fixed a problem that caused surfaces to be marked as visible too
        early when the blit presentation queue is in use.
  * nvidia-glx-VER.preinst:
    - Remove diversion on /usr/lib32/libGL.so.1.2 to
      /usr/lib32/nvidia/libGL.so.1.2.xlibmesa instead of
      /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core (LP: #333550).
  * debian.binary/patches/nvidia-rt-compat.patch:
    - Restore compatibility with -rt kernels. Thanks to Alessio Igor Bogani
      for the patch.
  * debian/dkms.conf.in:
    - Make sure that the patch for -rt kernels is applied only to 2.6.28.x
      kernels.

 -- Alberto Milone <email address hidden> Fri, 13 Mar 2009
09:27:20 +0100

** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
       Status: In Progress => Fix Released

--
nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed
https://bugs.launchpad.net/bugs/335879
You received this bug notification because you are a direct subscriber
of a duplicate bug.

Revision history for this message
SRElysian (srelysian) wrote : Re: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed
Download full text (3.7 KiB)

I just updated my jaunty release to ensure i got all of alpha 6, and the new
drivers were in there.. I have proposed and backports enabled though.

On Fri, Mar 13, 2009 at 3:51 PM, Schmirrwurst <email address hidden> wrote:

> when the update is going to be available in the repositories ?
> ----- Mail Original -----
> De: "Launchpad Bug Tracker" <email address hidden>
> À: <email address hidden>
> Envoyé: Vendredi 13 Mars 2009 20h40:07 GMT +01:00 Amsterdam / Berlin /
> Berne / Rome / Stockholm / Vienne
> Objet: [Bug 335879] Re: nvidia driver 180.35 breaks KDE 4, upgrade to
> 180.37 is needed
>
> This bug was fixed in the package nvidia-graphics-drivers-180 -
> 180.37-0ubuntu1
>
> ---------------
> nvidia-graphics-drivers-180 (180.37-0ubuntu1) jaunty; urgency=low
>
> * New upstream release (LP: #335879).
> - Fixed a problem that caused signals to be blocked in some
> applications.
> - Fixed a problem that could cause Xid errors and display corruption in
> certain cases when OpenGL is used to render to redirected windows, for
> example when Java2D is used with the -Dsun.java2d.opengl=true option.
> - glGetStringi(GL_EXTENSIONS, i) no longer returns NULL in OpenGL 3.0
> preview contexts.
> - Fixed a problem that caused the screen to flicker momentarily when
> OpenGL applications exit unexpectedly on GeForce 6 and 7 series GPUs.
> - Fixed an X server crash when an X client attempts to draw trapezoids
> and RenderAccel is disabled.
> - Improved recovery from certain types of errors.
> - VDPAU updates:
> o Fixed corruption on some H.264 clips.
> o Update documentation.
> o Fixed VC-1 decoding on 64-bit platforms.
> o Improved handling of invalid H.264 streams.
> o Fixed a problem that caused surfaces to be marked as visible too
> early when the blit presentation queue is in use.
> * nvidia-glx-VER.preinst:
> - Remove diversion on /usr/lib32/libGL.so.1.2 to
> /usr/lib32/nvidia/libGL.so.1.2.xlibmesa instead of
> /usr/lib32/nvidia/libGL.so.1.2.xserver-xorg-core (LP: #333550).
> * debian.binary/patches/nvidia-rt-compat.patch:
> - Restore compatibility with -rt kernels. Thanks to Alessio Igor Bogani
> for the patch.
> * debian/dkms.conf.in:
> - Make sure that the patch for -rt kernels is applied only to 2.6.28.x
> kernels.
>
> -- Alberto Milone <email address hidden> Fri, 13 Mar 2009
> 09:27:20 +0100
>
> ** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
> Status: In Progress => Fix Released
>
> --
> nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> --
> nvidia driver 180.35 breaks KDE 4, upgrade to 180.37 is needed
> https://bugs.launchpad.net/bugs/335879
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” source package in Ubuntu: Fix
> Released
>
> Bug description:
> After installing the nvidia driver version 180.35, I can no longer log out
> of KDE.
>
> If I look in the process list I can see...

Read more...

Revision history for this message
3vi1 (launchpad-net-eternaldusk) wrote :

Packages are in the standard repos, and confirmed working.

But, the packages still require you to remove /usr/lib/libGL.so first (bug 335621 - present since the .29 packages).

Revision history for this message
Inukaze (inukaze-otaku) wrote :

Hi there , well i had NVIDIA 5700LE 256MB AGP4X (Package nvidia-173.14.20)

I dont have bug fix ,
 i had installed KDM
Under Ubuntu Karmic Koala 9.10 AMD64
With Kernel 2.6.31-16-generic

Im using GNOME Desktop , just for 2 Reasons ( Better and Faster FlashPlayer in websites like youtube ) and the another reason , the notifications have "SHOW" button , in GDM with libnotify dont have SHOW Button yet animation

Well i had install KDM , i configure it with SystemSettings > Advance > Logon Manager well when i reboot my pc

Appear an error "Ubuntu its running in low graphics mode" well i select "Run ubuntu in low graphics mode just for this session" , but the exit of xorg , and dont enter again , just i see the "_" in the part supeior left of my monitor blinking , but i try ALT+F1 , ALT+F2 to change betweens terminals , but nothing happened

Someone know how to fix under Ubuntu Karmic Koala 9.10 AMD64 with drivers nvidia-173.14.20 and kernel 2.6.31-16-generic ???

Revision history for this message
Michael Marley (mamarley) wrote :

You should probably go to the "Answers" function of Launchpad and ask there. Your problem is not related to this bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.