246977 - existing firefox instance not found by startup script

Status: RESOLVED DUPLICATE of bug 177996

(Toolkit :: Startup and Profile System, defect)

Description

[Leif K-Brooks]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9

When I try to run Firefox with the URL of a page meant to be opened in another
window, it doesn't seem to detect the existing Firefox instance and displays the
profile manager instead.

Reproducible: Always
Steps to Reproduce:
1. Start a new Firefox instance.
2. Run "firefox http://slashdot.org/" at a shell.
Actual Results:  
The output "Error: No running window found" is generated, and the profile
manager starts.

Expected Results:  
Slashdot should have opened in a new Firefox window.

I'm running Fedora Core 2 with a plain vanilla Firefox install. The problem also
occurs when running as a different user, so I know it's not something in my profile.

Comment 1

[Cott Lang]

Attachment: Here's a firefox .9 startup script patch that should work

I think sometime after .7, somebody modified the firefox script and removed the
part that opened a URL in a new window. If you run just 'firefox' it will open
a new window just fine, but if you passed in a URL it wouldn't.

I just hacked in a condition to do an openurl() call if the browser is already
running and there's an argument $1. It won't support any other command line
arguments if it finds firefox already running, that's up to someone wiser than
me to fix. :)

Comment 2

[Phillip Stewart :P]

see bug 177996

Comment 3

[David Chin]

Attachment: test script

this ksh script works for current mozilla, but not firefox 0.9.1 Mozilla/5.0
(X11; Linux i686; en-US; rv: 1.7) Gecko/20040626; Firefox/0.9.1

Comment 4

[David Chin]

Comment on attachment 153073 [details]
test script

scratch that. the script works for the latest nightly as of this writing.

Comment 5

[(not currently active) Ted Mielczarek]

I'm pretty sure the fix for bug 177996 fixes this.

*** This bug has been marked as a duplicate of 177996 ***