Bug 3471 - All user-installed extensions disappear after browser restart
: All user-installed extensions disappear after browser restart
Status: RESOLVED WORKSFORME
Product: Browser
MicroB engine
: 4.1 (4.2008.23-14)
: N810 Maemo
: Low major with 1 vote (vote)
: ---
Assigned To: unassigned
: microb-bugs
:
: moreinfo
:
:
  Show dependency tree
 
Reported: 2008-07-20 05:15 UTC by Vincent Lefevre
Modified: 2009-09-24 03:56 UTC (History)
1 user (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Vincent Lefevre (reporter) 2008-07-20 05:15:54 UTC
SOFTWARE VERSION:
4.2008.23-14

STEPS TO REPRODUCE THE PROBLEM:
1. Reboot and rename the .mozilla directory.
2. Start the browser. The extensions installed by the user appear as expected
in Tools -> Components.
3. Restart the browser a few times (2 may be sufficient).

EXPECTED OUTCOME:
The extensions should still be visible.

ACTUAL OUTCOME:
Only the following default components (i.e. not installed by the user) appear
in Tools -> Components:
* Default plug-in, Real Player, Windows Media
* Shockwave Flash
(components-installer doesn't appear either). At least one of the extensions
(Flashblock) doesn't work at all. So, this isn't just a display problem in this
dialog box.

REPRODUCIBILITY:
sometimes (always after a few times)

I could reproduce the problem 3 times (I haven't tried more). Once the problem
appears, it remains after restarting the browser. Rebooting doesn't solve the
problem either. Removing the .mozilla directory and restarting the browser
doesn't solve the problem either. But after rebooting and removing the .mozilla
directory, the extensions reappear:

* components-installer
* Default plug-in, Real Player, Windows Media
* Dictionnaire MySpell en Français
* Flashblock port for MicroB
* Greasemonkey port for MicroB
* Shockwave Flash

This problem is similar to bug 3468.

EXTRA SOFTWARE INSTALLED:
Here are the extensions I've installed:
flashblock-webaddon
french-france-dictionary
greasemonkey-webaddon
Comment 1 Andre Klapper maemo.org 2008-07-21 19:15:34 UTC
Why would you want to rename the .mozilla directory?
If you move the default preferences directory of an application I wouldn't
expect the application to work. Sounds like a WONTFIX to me.
Comment 2 Vincent Lefevre (reporter) 2008-07-21 21:30:11 UTC
(In reply to comment #1)
> Why would you want to rename the .mozilla directory?

The bug occurred *before* I renamed the .mozilla directory. Renaming the
.mozilla directory is the only way I found to work around this problem (but
this works only once).

BTW, the .mozilla directory is just *user* preferences. Any application should
be able to work with empty user preferences.
Comment 3 Andre Klapper maemo.org 2008-07-22 16:52:16 UTC
I still don't get what this is about. So if you do NOT rename the directory,
what does not work?
Can you come up with a description about what exactly the issue is that you are
facing?
Comment 4 Vincent Lefevre (reporter) 2008-07-22 16:59:53 UTC
Initially, after installing the packages, all the extensions and plugins
appeared in Tools -> Components:
* components-installer
* Default plug-in, Real Player, Windows Media
* Dictionnaire MySpell en Français
* Flashblock port for MicroB
* Greasemonkey port for MicroB
* Shockwave Flash

But after one or two restarts of the browser, without changing anything in my
configuration (without renaming anything...), all the extensions disappear,
i.e. Tools -> Components just says:
* Default plug-in, Real Player, Windows Media
* Shockwave Flash

Note that even the "components-installer" is missing.
Comment 5 Andre Klapper maemo.org 2008-08-04 17:15:33 UTC
(In reply to comment #4)
> But after one or two restarts of the browser, without changing anything in my
> configuration (without renaming anything...), all the extensions disappear

Is this always reproducible (because you wrote "browser restarts", not "device
restarts")?

Can you also please create a browser logfile and reproduce the error:
Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in
the browser location bar, set that preference, reproduce the browser problem
and post the content of the file /tmp/browserlog here (you can for example
start the terminal application, run "more /tmp/browserlog" and copy the output
to this bug report).
Comment 6 Vincent Lefevre (reporter) 2008-08-05 05:43:21 UTC
(In reply to comment #5)
> Is this always reproducible (because you wrote "browser restarts", not "device
> restarts")?

Almost always reproducible. Same problem when the device restarts.

/tmp/browserlog contents:

({type:"message", msg:"No chrome package registered for
chrome://navigator/locale/navigator.properties ."})
({typetext:"typeError", type:"error", msg:"[JavaScript Error:
\"Components.classes['@mozilla.org/updates/timer-manager;1'] has no
properties\" {file:
\"file:///usr/lib/microb-engine/components/nsExtensionManager.js\" line:
2835}]", url:"file:///usr/lib/microb-engine/components/nsExtensionManager.js",
line:2835, hideCode:"true"})
({type:"message", msg:"No chrome package registered for
chrome://navigator-platform/locale/navigator.properties ."})
({type:"message", msg:"No chrome package registered for
chrome://navigator/locale/navigator.properties ."})
Comment 7 Andre Klapper maemo.org 2009-02-02 17:56:15 UTC
I'm still not able to reproduce this - never run into this, but I only have my
three default components here ("components-installer", "Default plug-in,
RealPlayer, Windows Media" and "Shockwave Flash").
Is this still an issue in 5.2008.43-7?
File and folder permissions are OK I assume?
Does this also happen when only having those three default components installed
and no "third party software" (in the sense of "not delivered on the device by
default")?
Comment 8 Andre Klapper maemo.org 2009-06-05 02:58:26 UTC
Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for/if
you can still reproduce this. Thanks!
Comment 9 Vincent Lefevre (reporter) 2009-09-24 03:56:59 UTC
FYI, the problem was no longer reproducible.