package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

[Volkodav]

* dkms: running auto installation service for kernel 2.6.36-020636rc2-generic
 * nvidia-current (256.44)... [fail]

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: nvidia-current 256.44-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 256.44 Thu Jul 29 01:22:44 PDT 2010
 GCC version: gcc version 4.4.5 20100816 (prerelease) (Ubuntu/Linaro 4.4.4-9ubuntu1)
Architecture: amd64
Date: Mon Aug 30 00:31:06 2010
ErrorMessage: nvidia-current kernel module failed to build
GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
MachineType: System manufacturer System Product Name
PackageVersion: 256.44-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-19-generic root=/dev/sdd3 ro quiet splash
SourcePackage: nvidia-graphics-drivers
Title: package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
dmi.bios.date: 07/20/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0205
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5GC-MX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: Rev 1.xx
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0205:bd07/20/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
dmi.product.name: System Product Name
dmi.product.version: Rev 1.xx
dmi.sys.vendor: System manufacturer
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-19-generic

[bugbot (bugbot)]

Hey Volkodav,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Volkodav (vadimtux)]

Can be closed since currently on Natty and no such bug here

On 02/18/2011 10:28 PM, bugbot wrote:
> Hey Volkodav,
>
>
> Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?
>
> If you've not seen this issue since maverick's release yourself, it may
> have been solved by kernel or X or other updates that occurred late in
> the release; if so, would you mind please closing the bug for us? Go to
> the URL mentioned in this bug report, click the yellow icon(s) in the
> status column and set to 'Fix Released'.
>
> If you no longer have the hardware needed to reproduce the problem, or
> otherwise feel the bug no longer needs tracked in Launchpad, you can set
> the status to 'Invalid'.
>
> If you are the original reporter and still have this issue, just reply
> to this email saying so. (Or set the bug status to Confirmed.) If you
> are able to re-test this against 11.04 Natty Narwhal (our current
> development focus) and find the issue still affects Natty, please also
> run 'apport-collect <bug-number>' while running natty, which will add
> fresh logs and debug data, and flag it for the Ubuntu-X development team
> to look at.
>
>
> ** Changed in: nvidia-graphics-drivers (Ubuntu)
> Status: New => Incomplete
>

[Launchpad Janitor (janitor)]

[Expired for nvidia-graphics-drivers (Ubuntu) because there has been no activity for 60 days.]