package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Bug: summary (auto-generated) ...
package nvidia-current 195.36.
System info:
`uname -r` says ..
2.6.32-24-generic
`lsb_release -rd` says ..
Description: Ubuntu 10.04.1 LTS
Release: 10.04
OS is i386 32-bit
Acer T180 with nvidia 6100GS and LG L226WT
Both nvidia installed packages are the latest ..
- nvidia-current 195.36.
- nvidia-settings 195.36.08-0ubuntu2.
GNOME is at 2.30.2 build date 10-06-25.
What happened?
- Not sure why it's trying to do a compile.
- I had just used the nvidia utility from System/
- Then it showed me the new "Alarm" applet and went into bug report and apport collection.
- Along the way there was some fleeting message about a missing file.
Over to you.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-current 195.36.
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelMo
Architecture: i386
Date: Tue Sep 21 01:40:08 2010
ErrorMessage: nvidia-current kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Acer Aspire T180
PackageVersion: 195.36.
ProcCmdLine: BOOT_IMAGE=
SourcePackage: nvidia-
Title: package nvidia-current 195.36.
dmi.bios.date: 04/27/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-B3
dmi.board.name: EM61SM/EM61PM
dmi.board.vendor: Acer
dmi.chassis.
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire T180
dmi.product.
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: lucid
architecture: i686
kernel: 2.6.32-24-generic
xkbcomp:
Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
Reason for the recompile was likely that while checking my refresh rate, I also saved a new xorg.conf from the Nvidia utility. I was on the other side of my KVM while it was digesting that so maybe I missed something. It all seems to be OK now.