Ubuntu
dahdi-linux package

dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build

Bug #1295595 reported by linksysds on 2014-03-21

This bug report is a duplicate of: Bug #1014834: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build [fatal error: asm/system.h: no such file or directory]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	dahdi-linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-45.68-generic 3.5.7.26
Uname: Linux 3.5.0-45-generic x86_64
NonfreeKernelModules: wcfxo dahdi
ApportVersion: 2.6.1-0ubuntu13
Architecture: amd64
DKMSKernelVersion: 3.5.0-45-generic
Date: Fri Mar 21 10:47:46 2014
InstallationDate: Installed on 2010-05-12 (1408 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1:2.5.0.1+dfsg-1ubuntu2
SourcePackage: dahdi-linux
Title: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2: dahdi kernel module failed to build
UpgradeStatus: Upgraded to quantal on 2012-12-14 (462 days ago)

Tags:

Revision history for this message

linksysds (linksysds) wrote on 2014-03-21:

DKMSBuildLog.txt Edit (11.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (11.5 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2014-03-21

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-03-24:

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 1014834, 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.