Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Firefox is OPEN and working fine, but when I click a link in Thunderbird I get 'Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.'

  • 7 réponses
  • 30 ont ce problème
  • 8 vues
  • Dernière réponse par pigsflew

more options

If I click a link on my desktop or in any other program (while Firefox is open and running), I get this message: "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system." There's about a billion links for this if you Google it, but they all say that Firefox wasn't shut down properly. (OK, maybe not ALL of them, but if the needle is in that haystack, I haven't yet found it.) That's not the issue in my case since I haven't shut FF down at all.

This happened

Every time Firefox opened

== IDK

If I click a link on my desktop or in any other program (while Firefox is open and running), I get this message: "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system." There's about a billion links for this if you Google it, but they all say that Firefox wasn't shut down properly. (OK, maybe not ALL of them, but if the needle is in that haystack, I haven't yet found it.) That's not the issue in my case since I haven't shut FF down at all. == This happened == Every time Firefox opened == IDK

Toutes les réponses (7)

more options

This began to happen to me when I tried to run two separate profiles simultaneously on the same installation of firefox with -no-remote

more options

You shouldn't run your "Default" Profile using the -no-remote command - the Profile that is listed as Default=1 in the profiles.ini file..

more options

This began happening for me after running a copy of Firefox 4 beta in parallel with Firefox 3 (I wasn't using a -no-remote command), and even after I thoroughly uninstalled both copies of Firefox, deleted my profiles, and reinstalled Firefox 3, it still happened. I hope I don't have to reinstall Windows to clear this.

more options

Solution for windows.

To setup a firefox install side by side so that links from external programs (like email) can open (so you don't get a "Firefox is already running but is not responding" message) do the following.

The solution entails the use of the -no-remote switch. Don't use it for the default browser. Use it for the non default browser.

I'll use firefox 3.6 and firefox 4.0 as examples but this should work for future versions.

+ Install firefox 3.6 and Firefox 4.0 in different directories. Eg.

C:\Program Files\Mozilla Firefox\firefox.exe
C:\Program Files\Mozilla Firefox 4\firefox.exe

+ Open profile manager. Start > Run : firefox.exe -ProfileManager

+ In profile manager create Two Profiles.

   firefox3.6
   firefox4

+ In profile manager select firefox 4 as your default (assuming you want to default to the latest) and tick "Don't ask at startup"

+ Create two windows shortcuts.

  • General: Mozilla Firefox 4 (default). Shortcut > Target: "C:\Program Files\Mozilla Firefox 4\firefox.exe". Shortcut > Start In: "C:\Program Files\Mozilla Firefox 4"
  • General: Mozilla Firefox 3.6. Shortcut > Target: "C:\Program Files\Mozilla Firefox\firefox.exe" -p firefox3.6 -no-remote. Shortcut > Start In: "C:\Program Files\Mozilla Firefox"

That's it. Links from external programs should now open in your default browser.

Further details see. Opening a new instance of your Mozilla application with another profile

more options

I'm not running ff with no-remote but still have this problem

more options

It can also happen if you have the environment variable MOZ_NO_REMOTE=1 (Control Panel > System > Advanced > Environment variables).

more options

Cor-el-- That fixed it! I wish this solution was anywhere in the error's help pages.