firefox extension upgrade does not work

[LGB [Gábor Lénárt]]

Binary package hint: firefox-3.5

Usually after a new version of the firefox-3.5 (and/or xulrunner?) [some] extensions don't work anymore: Tools->Add-ons report "restart firefox to complete your changes" but even if I do this, I got the same message after the restart, and extension can't work. If I hit "cancel" for upgrade on such an extension, then disable - restart - enable - restart it works again, but of course only with the old version of that extension. NoScript is such an extension for example, but it's possible that every extension is affected if they have upgrade ...

ProblemType: Bug
Architecture: i386
Date: Tue Sep 29 09:31:42 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu3
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-10-generic i686

[Jamie Strandboge (jdstrand)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 433128, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[LGB [Gábor Lénárt] (lgb)]

I've just tried it out, I completely disabled apparmor, but still I have the problem, that upgrade of extensions does not work, firefox-3.5 always says that I have to restart firefox, even if I did dozens of time. I can just cancel the installation and i can use my extensions then, but of course no newer versions then. I am sure that I disabled apparmor since I had some kernel log where apparmor said denies about moonlight plugin (mmap), but there is no sign of this after doing /etc/init.d/apparmor stop, but still I have the problem. I commented this bug for now, since for it does not seem that the problem is apparmor, or at least there must be other problems here too, which is not related of bug #433128 I think.

[LGB [Gábor Lénárt] (lgb)]

Since it seems not to be an apparmor related issue (or not only), I think the report should be reopened, it can be reproduced here with apparmor fully disabled (see my previous comment please). So I hope it's not a problem to modify the status of the bug report for now ...

[Luís Silva (luis)]

I'm having the same problem.

As usr.bin.firefox-3.5 is in /etc/apparmor.d/disable/, the problem shouldn't be apparmor, right?

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 441552, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.