purging beagle doesn't clean up everything
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
beagle (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: beagle
Hello! I'm using Ubuntu Gutsy, and I noticed that the beagle package doesn't clean-up after itself even after a purge.
I'm trying to switch to tracker for a while, and I tried to remove beagle. (libbeagle can't be removed because Nautilus depends on it, but that's another issue).
So I did an "aptitude purge beagle", and I noticed it left quite some stuff behind (see below). I think all of those should have been removed, too. (And the cache is big enough to matter.)
bogdanb@cimer:~$ sudo aptitude purge python-beagle beagle
[snip]
(Reading database ... 226673 files and directories currently installed.)
Removing beagle ...
Purging configuration files for beagle ...
Looking for files to backup/remove ...
Not backing up/removing `/var/cache/
Removing user `beagleindex' ...
Done.
dpkg - warning: while removing beagle, directory `/etc/beagle' not empty so not removed.
Reading package lists... Done
[snip]
bogdanb@cimer:~$ ls -la /var/cache/beagle
total 1
drwxr-xr-x 6 112 nogroup 152 2007-09-20 22:18 .
drwxr-xr-x 27 root root 760 2007-08-17 18:09 ..
drwx------ 2 112 nogroup 48 2007-09-20 00:55 .gconf
drwx------ 2 112 nogroup 80 2007-09-20 00:56 .gconfd
drwx------ 2 112 nogroup 48 2007-01-18 07:37 .gnome2
drwxr-xr-x 2 112 nogroup 88 2007-09-20 00:55 .gstreamer-0.10
bogdanb@cimer:~$ ls -la /etc/beagle/
total 13
drwxr-xr-x 2 root root 88 2007-09-20 22:18 .
drwxr-xr-x 157 root root 9224 2007-09-20 22:18 ..
-rw-r--r-- 1 root root 1353 2007-01-12 21:51 external-
bogdanb@cimer:~$ du -sh ~/.beagle/*
12K config
323M Indexes
1.3G Log
1.4G TextCache
466M ToIndex
Changed in beagle: | |
importance: | Undecided → Low |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.