Ubuntu
dahdi-linux package

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

Bug #1132798 reported by doblejdominguez on 2013-02-25

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

When it is upgrading stop saying Configurin Kernel and don continue upgrading and systems go unstable

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
Uname: Linux 3.5.0-24-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
DKMSKernelVersion: 3.5.0-24-generic
Date: Mon Feb 25 14:33:45 2013
InstallationDate: Installed on 2012-09-26 (151 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
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-10-19 (129 days ago)

Tags:

Revision history for this message

doblejdominguez (doblejdominguez) wrote on 2013-02-25:

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

Apport retracing service (apport) on 2013-02-25

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-03-01:

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.