Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

127.0.2 profiles in folders: "Firefox is already running"

  • 1 (رد واحد)
  • 3 have this problem
  • 253 views
  • آخر ردّ كتبه chr15m

chr15m
chr15m

For a long time I've used Firefox on Linux with multiple instances each with their own profile folder. Today when I try to run these instances with separate profile folders I get the following error:

> Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile.

Profiles are created like this:

firefox --new-instance --createprofile "PROFILENAME ~/.firefox-PROFILENAME"

They are run like this:

firefox --new-instance --profile "~/.firefox-PROFILENAME"

It seems something has broken with the instance isolation as this is now throwing an error. Additionally I run "createprofile" it doesn't seem to actually create the folder.

For a long time I've used Firefox on Linux with multiple instances each with their own profile folder. Today when I try to run these instances with separate profile folders I get the following error: > Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile. Profiles are created like this: firefox --new-instance --createprofile "PROFILENAME ~/.firefox-PROFILENAME" They are run like this: firefox --new-instance --profile "~/.firefox-PROFILENAME" It seems something has broken with the instance isolation as this is now throwing an error. Additionally I run "createprofile" it doesn't seem to actually create the folder.

الحل المُختار

Solution: this is happening when Firefox is installed as a snap instead of via `apt`. To fix it I did the following:

``` snap remove firefox apt install firefox ```

I previously had it installed with `apt` but somehow it must have been re-installed as a snap along the line.

Read this answer in context 👍 0

All Replies (1)

chr15m
chr15m صاحب السؤال

الحل المُختار

Solution: this is happening when Firefox is installed as a snap instead of via `apt`. To fix it I did the following:

``` snap remove firefox apt install firefox ```

I previously had it installed with `apt` but somehow it must have been re-installed as a snap along the line.