User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124) Gecko/20091028 Ubuntu/9.10 (karmic) Firefox/3.5.4 When I restart Firefox (not close and reopen, but the "Restart Firefox" button after changing an add-on), buttons in custom toolbars (added by extensions) are absent, although the toolbar itself appears (empty). Manually closing and opening Firefox (instead of a restart or after) causes things to work as expected again. Reproducible: Always Steps to Reproduce: 1. Install Googlebar Lite or some other extension that adds a toolbar to Firefox. 2. Add, remove, or disable some other add-on, click "Restart Firefox" when prompted. (Note that if you quit and restart manually after changing the add-on, you don't get this problem.) 3. New toolbar is present after restart, but missing all buttons. 4. Quit Firefox and reopen it normally and all is back to normal. Actual Results: New toolbar missing all buttons after quick restart (but not after subsequent close and reopen). Expected Results: Toolbar should render properly with all buttons after quick restart. The extension I'm having trouble with specifically is Googlebar Lite, but I think this is a Firefox bug, not an extension bug (unless there's something specific extension writers have to do for quick restarts?). I installed that in place of the Google Toolbar, which broke horribly when I upgraded to Firefox 3.5 (search bar doesn't appear in the toolbar at all, resetting to default settings doesn't work properly, layout doesn't change properly). Not sure any of those problems are related to this bug, though.
Looking at it a bit more, seems to happen after add-ons are changed, regardless of whether Firefox is restarted quickly or manually, seems to affect all toolbar buttons created by any add-on.
Actually, looks like it might be related to this: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/281348 But manifesting in a way that I did not expect. If that's the case, then the problem is further downstream than Firefox itself.
Or it could be the fault of the addon.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.