Ubuntu
blcr package

package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed to build

Bug #1000617 reported by Enrico Macchiavelli on 2012-05-17

This bug report is a duplicate of: Bug #762996: package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed to build [configure: error: Failed to locate kernel symbol table. Try using --with-system-map or --with-vmlinux.]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	blcr (Ubuntu)	New	Undecided	Unassigned

Bug Description

I dont know. The system signal to me that this installation fail. I dont know why and how...
bye

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: blcr-dkms 0.8.2-10
ProcVersionSignature: Ubuntu 2.6.32-41.88-generic-pae 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-generic-pae i686
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia
Architecture: i386
Date: Thu May 17 07:38:24 2012
ErrorMessage: blcr kernel module failed to build
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2)
PackageArchitecture: all
PackageVersion: 0.8.2-10
SourcePackage: blcr
Title: package blcr-dkms 0.8.2-10 failed to install/upgrade: blcr kernel module failed to build

Tags:

Revision history for this message

Enrico Macchiavelli (enrico-macchiavelli) wrote on 2012-05-17:

DKMSBuildLog.txt Edit (7.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (836 bytes, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-05-17:

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 762996, 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. Please continue to report any other bugs you may find.