computer-janitor only deletes old linux headers. Not modules/image.

Bug #420837 reported by mattmill30
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
computer-janitor (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

Binary package hint: computer-janitor

Hi,

I've noticed that when I run computer-janitor after a kernel upgrade, it only detects and removes the old header files.

Not the linux-restricted-modules or linux-image.

It would be useful for computer-janitor to completely remove all traces of old kernels after the user has upgraded and is running a newer version.

Perhaps it would be possible to automate this in the future?

User upgrades kernel, system monitors for unexpected system issues that weren't present prior to upgrade, possibly on next boot test old kernel as one off, to see if problem still persists, proving whether the problem is due to a regression in the new kernel, and then finally remove the old kernel once the system is happy that there have been no regressions.

Revision history for this message
Vikram Dhillon (dhillon-v10) wrote :

Can you check if this issue persists in Karamic...

Thanks

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Vikram, the janitor didn't offer to delete any of the recent kernels (-5 and later). I had to purge them by hand. When should it?

Also, I'd like to see at least a purge option so that it doesn't leave "rc" droppings; what's the point if I have to fix things afterwards?

Revision history for this message
Vikram Dhillon (dhillon-v10) wrote : Re: [Bug 420837] Re: computer-janitor only deletes old linux headers. Not modules/image.

Sorry, I miss understood your questions, I really don't think that there
is a way in computer janitor to accomplish this task, but you can go in
terminal and type

uname -r

and then go to Synaptic Package Manager and type the output of the
command in quick search and you will get the kernel in the search, then
right click and mark for complete removal. This will automatically
update your grub and leave nothing behind, you might have to do a sudo
apt-get autoremove just in case

Hope that solves your problem,
Vikram

On Sat, 2009-08-29 at 00:05 +0000, Noel J. Bergman wrote:
> Vikram, the janitor didn't offer to delete any of the recent kernels (-5
> and later). I had to purge them by hand. When should it?
>
> Also, I'd like to see at least a purge option so that it doesn't leave
> "rc" droppings; what's the point if I have to fix things afterwards?
>

Revision history for this message
to be removed (liw) wrote :

I have recently changed Computer Janitor so that it is rather more careful about what to suggest for removal. The problem was that it was considering all common third-party packages as uninteresting to the user, which caused a lot of people to accidentally remove stuff they care about.

The fix for that unfortunately also means the janitor now doesn't think old kernels should be removed.

Perhaps in karmic+1 we can finally fix things properly so that useless kernels go away, but third-party stuff stays. For now, I am satisfied with the current compromise: it doesn't clean up everything, but it does not clean up too much, either.

Changed in computer-janitor (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Forlong (forlong) wrote :

I just came across this issue while trying to remove the 31-11 kernel.

Revision history for this message
to be removed (liw) wrote :

I can't see this happening, actually. For me, c-j seems to remove modules and image packages as well.

Revision history for this message
shankao (shankao) wrote :

Any advance on this? I have very hard space constraints, old kernels are really large for me and would be great that computer-janitor removes them automatically.

As a suggestion for the third party packages problem, a new command line option could be added that hardens the check for packages that match some expression and also limits the search to those:

$ computer-janitor -x *kernel*

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.