Bug 465376 - firefox -no-remote option doesn't work
firefox -no-remote option doesn't work
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-02 19:08 EDT by Geoff Gustafson
Modified: 2008-10-03 09:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-03 09:27:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Geoff Gustafson 2008-10-02 19:08:29 EDT
Description of problem:
If I'm not mistaken, firefox -no-remote is supposed to bring up a new instance of the browser rather than pass on the URL to the existing browser. When I try it, 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."

I noticed that with the F9 version running, trying to run a version of Firefox I had built myself resulted in the same problem. Maybe the function is broken in upstream Firefox.

I'm seeing this on an Intel x86_64 box but with the i386 OS installed.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Launch firefox
2. Attempt to run firefox -no-remote from the cmdline to open a separate instance
Comment 1 Matěj Cepl 2008-10-03 08:35:04 EDT
yup, firefox-3.0.2-1.fc10.x86_64 100% reproduction
Comment 2 Matěj Cepl 2008-10-03 09:27:26 EDT
We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=458369) and believe that it is more appropriate to let it be resolved upstream.

Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.

Note You need to log in before you can comment on or make changes to this bug.