Ubuntu
ndiswrapper package

ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build

Bug #1210795 reported by Paul Read on 2013-08-10

This bug report is a duplicate of: Bug #1023645: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build [error: ‘struct kernel_stat’ has no member named ‘cpustat’]. Edit Remove

This bug affects 1 person

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

Bug Description

Appeared on performing an upgrade from 12.04 LTS to 12.10

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic i686
ApportVersion: 2.6.1-0ubuntu12
Architecture: i386
DKMSKernelVersion: 3.5.0-37-generic
Date: Sat Aug 10 15:00:11 2013
InstallationDate: Installed on 2013-06-08 (62 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1.57-1ubuntu1
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
UpgradeStatus: Upgraded to quantal on 2013-08-10 (0 days ago)

Tags:

Revision history for this message

Paul Read (paul-read) wrote on 2013-08-10:

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

Apport retracing service (apport) on 2013-08-10

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-08-12:

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