|
|
|
|
|
|
by k8svet
934 days ago
|
|
|
No. Sorry. I have a list of complaints with Firefox but this is clearly user error. I do this literally every day for a decade or more. It works fine. It particularly helps to not unnecessarily use things that can affect the env like launching a browser with su. In fact I can I think it a list of things that could go wrong with that. |
|
|
On my Linux system, this works with any other browser I try. It only fails with Firefox. If this is user error, it seems every other browser handles user errors much better.
- Firefox: First window is open, running `firefox URL` from the other terminal hangs for 15-20 seconds and then shows the popup "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.". No new tabs or windows are spawned.
- Chromium: First window is open, running a `chromium URL` command from the other terminal opens a new tab on the existing window.
- Microsoft Edge: First window is open, running a `microsoft-edge-stable URL` command from the other terminal opens a new tab on the existing window.
- Ladybird: First window is open, running `ladybird` in the other terminal opens a new ladybird window.
- Emacs/eww: First window is open, running `emacs --eval '(eww "example.com")'` on another terminal opens a new browser window.
- Netsurf: First window is open, running `netsurf URL` from the other terminal opens a new netsurf window.
- Dillo: First window is open, running `dillo URL` from the other terminal opens a new dillo window.
- Links/XLinks: First window is open, running `xlinks -G URL` from the other terminal opens a new links window.
You can see a clear pattern. Got any other browsers that refuse to run with a message like that? Or is this not a fault of Firefox, and something super extra that everything from other mainstream browsers to more obscure ones somehow handle for the user?