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

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo
Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.
Oplost Argivearre

127.0.2 profiles in folders: "Firefox is already running"

Firefox Ynstallaasje en updates
chr15m beäntwurde
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.

Alle antwurden (1)

chr15m
chr15m Fraacheigener

Keazen oplossing

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.