Thunderbird not cleaning up after extensions

[Jamie Dimmel]

Binary package hint: thunderbird

When you remove programs or addons from Mozilla Thunderbird, the legacy configuration data continues to exist in Thunderbird. This includes 'Attahment Extractor' addon, 'Addressbook Sync' addon and Beagle. All of these have been uninstalled (Beagle for several weeks), yet the information is still in Thurnderbirds configuration. This can only slow the program down (and it is REALLY slow since the latest upgrade). I realize the programs themselves should clean up after themselves, but if Mozilla allows addons to alter it's configuration (whether for Thunderbird or Firefox) it should be smart enough to remove (or offer to remove) that data when the program has been uninstalled.

I am running Thunderbird 2.0.0.17 (20080925) on Ubuntu 8.04.

ProblemType: Bug
Architecture: i386
Date: Sat Oct 4 14:01:41 2008
DistroRelease: Ubuntu 8.04
Package: mozilla-thunderbird 2.0.0.17+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: all
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: thunderbird
Uname: Linux 2.6.24-19-generic i686

[arno_b (arno.b)]

I experienced the same problem, notably with allpeers.

[arno_b (arno.b)]

Moreover, I think it is a xulrunner issue since Firefox is also concerned by this problem.

[Przemek K. (azrael)]

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. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs that are relevant for this particular issue.

[Przemek K. (azrael)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
If you decide to reopen this bug, it would help us a lot if you could test the current Ubuntu development version (10.10) and check if this bug is still relevant.
Thanks again!