nvidia-310 310.32-0ubuntu2: nvidia-310 kernel module failed to build

[Stuart Bishop]

Got this crash while software updater was doing its updates.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: nvidia-310 310.32-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.8.0-17-generic
Date: Tue Apr 9 14:42:54 2013
InstallationDate: Installed on 2013-02-26 (42 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
MarkForUpload: True
PackageVersion: 310.32-0ubuntu2
SourcePackage: nvidia-graphics-drivers-310
Title: nvidia-310 310.32-0ubuntu2: nvidia-310 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia.310.hybrid.conf: [deleted]

[Stuart Bishop (stub)]

Setting up linux-headers-3.8.0-17 (3.8.0-17.27) ...
Setting up linux-headers-3.8.0-17-generic (3.8.0-17.27) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.8.0-17-generic /boot/v
mlinuz-3.8.0-17-generic
Error! Bad return status for module build on kernel: 3.8.0-17-generic (x86_64)
Consult /var/lib/dkms/nvidia-310/310.32/build/make.log for more information.
Setting up linux-headers-generic (3.8.0.17.32) ...
Setting up linux-libc-dev:amd64 (3.8.0-17.27) ...

[Stuart Bishop (stub)]

DKMS make.log for nvidia-310-310.32 for kernel 3.8.0-17-generic (x86_64)
Tue Apr 9 14:42:50 ICT 2013
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Error 1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jerry Stringer (toycrawler81)]

Setting up linux-image-generic (3.8.0.17.33) ...
Setting up linux-headers-3.8.0-17 (3.8.0-17.27) ...
Setting up linux-headers-3.8.0-17-generic (3.8.0-17.27) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.8.0-17-generic /boot/vmlinuz-3.8.0-17-generic
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.8.0-17-generic (x86_64)
Consult /var/lib/dkms/nvidia-310/310.32/build/make.log for more information.
Setting up linux-headers-generic (3.8.0.17.33) ...
Setting up linux-generic (3.8.0.17.33) ...
Setting up qtdeclarative5-accounts-plugin (0.0bzr13.03.08-0ubuntu1) ...
Setting up qtdeclarative5-friends-plugin (0.1.0bzr13.04.02-0ubuntu1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 576648, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvidia-graphics-drivers-310 - 310.44-0ubuntu1

---------------
nvidia-graphics-drivers-310 (310.44-0ubuntu1) raring; urgency=low

  * debian/dkms/patches/allow_sublevel_greater_than_5.patch,
    debian/templates/dkms.conf.in:
    - Allow SUBLEVEL variables greater than 5 in the
      kernel Makefile (LP: #1166639).
  * New upstream release:
    - Fixed CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB
      Cursor Buffer Overflow in "NoScanout" Mode. This
      buffer overflow, which occurred when an X client
      installed a large ARGB cursor on an X server
      running in NoScanout mode, could cause a denial
      of service (e.g., an X server segmentation fault),
      or could be exploited to achieve arbitrary code
      execution.
 -- Alberto Milone <email address hidden> Tue, 09 Apr 2013 16:54:04 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvidia-graphics-drivers-304 - 304.88-0ubuntu1

---------------
nvidia-graphics-drivers-304 (304.88-0ubuntu1) raring; urgency=low

  * debian/templates/control.in:
    - Conflict/replace/provide nvidia-driver-binary
      which is specific to modern nvidia drivers.
  * debian/dkms/patches/allow_sublevel_greater_than_5.patch,
    debian/templates/dkms.conf.in:
    - Allow SUBLEVEL variables greater than 5 in the
      kernel Makefile (LP: #1166639).
  * New upstream release:
    - Fixed CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB
      Cursor Buffer Overflow in "NoScanout" Mode. This
      buffer overflow, which occurred when an X client
      installed a large ARGB cursor on an X server
      running in NoScanout mode, could cause a denial
      of service (e.g., an X server segmentation fault),
      or could be exploited to achieve arbitrary code
      execution.
 -- Alberto Milone <email address hidden> Tue, 09 Apr 2013 17:20:04 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvidia-graphics-drivers-304-updates - 304.88-0ubuntu1

---------------
nvidia-graphics-drivers-304-updates (304.88-0ubuntu1) raring; urgency=low

  * debian/templates/control.in:
    - Conflict/replace/provide nvidia-driver-binary
      which is specific to modern nvidia drivers.
  * debian/dkms/patches/allow_sublevel_greater_than_5.patch,
    debian/templates/dkms.conf.in:
    - Allow SUBLEVEL variables greater than 5 in the
      kernel Makefile (LP: #1166639).
  * New upstream release:
    - Fixed CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB
      Cursor Buffer Overflow in "NoScanout" Mode. This
      buffer overflow, which occurred when an X client
      installed a large ARGB cursor on an X server
      running in NoScanout mode, could cause a denial
      of service (e.g., an X server segmentation fault),
      or could be exploited to achieve arbitrary code
      execution.
 -- Alberto Milone <email address hidden> Tue, 09 Apr 2013 17:23:25 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvidia-graphics-drivers-310-updates - 310.44-0ubuntu1

---------------
nvidia-graphics-drivers-310-updates (310.44-0ubuntu1) raring; urgency=low

  * debian/dkms/patches/allow_sublevel_greater_than_5.patch,
    debian/templates/dkms.conf.in:
    - Allow SUBLEVEL variables greater than 5 in the
      kernel Makefile (LP: #1166639).
  * New upstream release:
    - Fixed CVE-2013-0131: NVIDIA UNIX GPU Driver ARGB
      Cursor Buffer Overflow in "NoScanout" Mode. This
      buffer overflow, which occurred when an X client
      installed a large ARGB cursor on an X server
      running in NoScanout mode, could cause a denial
      of service (e.g., an X server segmentation fault),
      or could be exploited to achieve arbitrary code
      execution.
 -- Alberto Milone <email address hidden> Tue, 09 Apr 2013 17:04:04 +0200