Removal does not clean up after dkms, l-r-m(?)
Bug #300773 reported by
Matt Zimmerman
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkms (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Andy Whitcroft |
Bug Description
I just removed a bunch of obsolete kernels from my system, and noted that for each one, I saw this error:
rmdir: failed to remove `/lib/modules/
The contents which remain are:
/lib/modules/
updates volatile
/lib/modules/
build updates volatile
/lib/modules/
build updates
/lib/modules/
build updates
/lib/modules/
build updates
/lib/modules/
build updates
/lib/modules/
build updates
Related branches
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux: | |
assignee: | ubuntu-kernel-team → apw |
status: | Triaged → In Progress |
Changed in linux: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
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 the headers:
apw@dm$ sudo dpkg -r linux-image- 2.6.28- 1-ub-generic 2.6.28- 1-ub-generic 2.6.28- 1-ub-generic ... 2.6.28- 1-ub-generic, directory `/lib/modules/ 2.6.28- 1-ub-generic' not empty so not removed.
[...]
apw@dm$ sudo dpkg -r linux-headers-
(Reading database ... 171800 files and directories currently installed.)
Removing linux-headers-
dpkg - warning: while removing linux-headers-
In my case I have a bunch of module files:
apw@dm$ ls /lib/modules/ 2.6.28- 1-ub-generic/
modules.alias modules.inputmap modules.pcimap modules.usbmap
modules.ccwmap modules.isapnpmap modules.seriomap
modules.ieee1394map modules.ofmap modules.symbols
It does appear that the kernel postrm script is not cleaning out all of the depmod generated files. That would not explain the files reported by Matt, as he does not have these files too I assume this kernel was never booted?