Open Bug 592975 Opened 13 years ago Updated 1 year ago

Different configuration dependent whether directly started or started via a link in an e-mail


(Firefox :: Settings UI, defect)

3.6 Branch
Windows 7





(Reporter: ruckb, Unassigned)


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv: Gecko/20100722 Firefox/3.6.8 GTB7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv: Gecko/20100722 Firefox/3.6.8 GTB7.1

I have no idea what happens there and how to debug, so I hope to get some help here ... 
I have the portable edition of Firefox 3.6.8. 
normally I start it via a link to my portabable application directory. I have installed e. g. the google toolbar and some add ons (like download status bar). 

When i start my firefox via a link in an e-mail  there are different add-ons installed, some additional (that I just installed last time like and some are not there (like image zoom).

Looking into the Windows Task manager shows that in both cases Firefox is starte from the same executable in the same directory ... 

Any idea how to figure out what is different when starting it via the link in an e-mail ?

thanks and regards


Reproducible: Always

Steps to Reproduce:
1. Start FF portable via direct link to executable
2. install an add on
3. Exit FF
4. Start Firefox viw a link in an e-mail
5. Check add on: it is not there ... 

Expected Results:  
Both instances of Firefox should have the same configuration settings
One more observation:
If I start Firefox directly (link to executable) I can do this several times and get serveral instances from Firefox running.
If I have started Firefox via the link in an e-mail and try to start another instance with the executable I get the messeage:
"There is running another instance of Firefox. Please close all other instances of Firefox before starting Firefox portable"

Does anybody have an idea why I get two different configurations started ?
Version: unspecified → 3.6 Branch
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.