I have a similar problem on Mint 18/Ubuntu 16:
sudo apt-get purge linux-image-4.4.0-xx-generic linux-headers-4.4.0-xx
and it shows the message: dpkg: warning: while removing linux-
image-4.4.0-xx-generic, directory '/lib/modules/4.4.0-xx-generic' not
empty so not removed
In /lib/modules/
I have this problem on 12.04. The fix has been lost. Should I reopen
this bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/300773
Title:
Removal does not clean up after dkms, l-r-m(?)
This bug was fixed in the package linux - 2.6.28-4.5
---
linux (2.6.28-4.5) jaunty; urgency=low
[ Andy Whitcroft ]
* clean up module dependancy information on package removal/purge
- LP: #300773
[ Tim Gardner ]
* Update iscsitarget to 0.4.17
* Build in ext{234}
*
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
Removal does not clean up after dkms, l-r-m(?)
https://bugs.launchpad.net/bugs/300773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Andy Whitcroft (apw)
Status: Triaged = In Progress
--
Removal does not clean up after dkms, l-r-m(?)
https://bugs.launchpad.net/bugs/300773
You received this bug notification because you are a member of
When you say removed these kernels did that involve removing the kernel-
image and the linux-headers for each? The build link seems to come from
the linux-headers package. So could you confirm which were removed and
in which order.
I have just tried this here, removing the image first and then
Going through some experiments:
Simple install/deinstall:
$ sudo dpkg -i linux-image-2.6.28-1-ub-generic_2.6.28-1.1_amd64.deb
[...]
$ sudo dpkg -r linux-image-2.6.28-1-ub-generic
[...]
$ ls /lib/modules/2.6.28-1-ub-generic
modules.aliasmodules.inputmap modules.pcimapmodules.usbmap
On Thu, Dec 04, 2008 at 02:24:53PM -, Andy Whitcroft wrote:
Put together a patch to clean this lot up (attached).
This patch looks good and fixes several bugs, but not the exact issue I
reported. My apologies for not being clearer in the original report.
In my case, the modules.* files
On Thu, Dec 04, 2008 at 03:01:47PM -, Matt Zimmerman wrote:
The crux of my problem is the updates directory, which contains modules
built by DKMS. Nothing cleans up these files when a kernel is removed, only
when the entire module package (e.g. nvidia-173-kernel-source) is removed.
I
Ok this seems pretty simple to clear up in dkms itself. When removing a
kernel we envoke a dkms remove on every installed dkms package for that
kernel. Once we have done that we can simply remove the the
updates/dkms directory.
With the attached debdiff applied to dkms it will attempt to
Thanks for the patch. I've s/intrepid/jaunty and uploaded it to Jaunty
and added it to git head.
--
Removal does not clean up after dkms, l-r-m(?)
https://bugs.launchpad.net/bugs/300773
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package dkms - 2.0.20.4-0ubuntu3
---
dkms (2.0.20.4-0ubuntu3) jaunty; urgency=low
* Ensure that the /lib/modules/version/updates/dkms directory is
removed if it is empty after a removal. This allows the modules
directory to be removed as it
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
Removal does not clean up after dkms, l-r-m(?)
https://bugs.launchpad.net/bugs/300773
You received this bug notification because
13 matches
Mail list logo
