kpackagekit crashes X on startup

[pkannan]

KPackageKit hangs the whole system on startup. This happens either by double clicking on the notification icon in the system tray or when you startup kpackagekit from command line. However, when you install a pre-downloaded debian, this works fine.

$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
$ apt-cache policy kpackagekit
kpackagekit:
  Installed: 0.4-0ubuntu8
  Candidate: 0.4-0ubuntu8
  Version table:
 *** 0.4-0ubuntu8 0
        500 http://gb.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

[lspci]
00:00.0 RAM memory [0500]: nVidia Corporation MCP78S [GeForce 8200] Memory Controller [10de:0754] (rev a2)
     Subsystem: Hewlett-Packard Company Device [103c:360a]
02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8200M G [10de:0845] (rev a2)
     Subsystem: Hewlett-Packard Company Device [103c:360a]

[Jonathan Thomas (echidnaman)]

Could you attach a copy of your /var/log/Xorg.0.log, /var/log/Xorg.0.log.old, and the output of lspci -vvnn (two v's, not a w)?
Thanks.

[pkannan (pkannan)]

Here is the Xorg.0.log file

[pkannan (pkannan)]

Here is the Xorg.0.log.old

[pkannan (pkannan)]

Here is the output from the lspci -vvnn.

I also want to add that is crash is not just seen in kpackagekit. Sometimes, this is seen when I open any tool that is running on the system tray bar. I am suspecting this to be something related to composite in kwin. I am not sure.

[Jonathan Thomas (echidnaman)]

X crashes are either xserver bugs or driver bugs.

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

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.