This bug was fixed in the package dkms - 2.3-3
---
dkms (2.3-3) unstable; urgency=medium
* Upstream post-2.3 cherry-picks for apport (LP: #1661843)
-- Aron Xu Tue, 07 Feb 2017 23:27:25 +0800
** Changed in: dkms (Ubuntu Zesty)
Status: Triaged => Fix
There are 3 patches missing, they are committed to upstream HEAD, though:
https://github.com/dell/dkms/commit/3247bd12399a9500d5caa32ac55f071996514024
https://github.com/dell/dkms/commit/b7a8dcb84e36d8037a1a8a92f7e5262f769ce13b
Specifically, at least this change was lost.
https://launchpadlibrarian.net/219224401/dkms_2.2.0.3-1.1ubuntu5.14.04.4_2.2.0.3-1.1ubuntu5.14.04.5.diff.gz
There may have been more changes to dkms_apport.py that disappeared too
though.
--
You received this bug notification because you are a
This is a regression of the fix for bug 1499842, the merge from debian
overwrote dkms_apport.py and now it is back to its state from before bug
1499842 was fixed.
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Aron Xu (happyaron)
** Changed in: dkms (Ubuntu)
Status: New =>
This crash has the same stack trace characteristics as bug #1499842.
However, the latter was already fixed in an earlier package version than
the one in this report. This might be a regression or because the
problem is in a dependent package.
** Tags removed: need-duplicate-check
** Changed in: