Closed Bug 246027 Opened 20 years ago Closed 20 years ago

-remote "ping()" always reports no running window found

Categories

(Toolkit :: Startup and Profile System, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 246166

People

(Reporter: gian, Assigned: bryner)

Details

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

When I try run firefox -remote "ping()", it's allways reports "Error: No running
window found".

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I confirm this bug for 0.9RC.

Not only does ping() not work, but it appears that running browser detection is
broken in general.  openURL() doesn't work either, for example.
Flags: blocking0.9?
Also confirming for 0.9 RC on Linux (Fedora Core 2).  This absolutely must get
fixed for the final release, or else firefox will be useless as a URL handler in
GNOME (or KDE).
Assignee: firefox → bsmedberg
Component: General → Startup and Profile System
QA Contact: firefox.general → bsmedberg
Assignee: bsmedberg → bryner
Confirmed on RH9.  Whose throat do we choke [wheels grease] to get this fixed
before 1.0?  This is huge!!
hrm, I'm not 100% sure on this, but I should point out that ping() syntax did
change (to be -a firefox ping() iirc)
Results of "firefox --help":
-remote <command>       Execute <command> in an already running Mozilla process.

I didn't see nothing about -a ;)
I have just tried 0.9-final on Debian and this bug seems to crawl here also. It
is realy too bad that you let this huge thing slip in the final release. 
This makes my Gnome desktop uninteractive with FireFox. I will have to switch
back to 0.8 or something. :-(


./firefox -remote "ping()"
Error: No running window found

./firefox -remote "OpenURL(http://www.slashdot.org)"
Error: No running window found
I tried on 0.9 final (with slackware 9.1 and current, conectiva 9.0 and FC1) and
got same problem. I think with a bug of this kind, final (0.9) can't be released.
fourwood and mconnor have pointed out that that the "-a firefox -remote
'ping()'" sequence will work.

I have confirmed that it does in fact work for me.

Here is my modified script to put a page in a new tab on an existing browser.

#!/bin/sh

cd /usr/local/firefox
((./firefox -a firefox -remote "ping()" &&
 ./firefox -a firefox -remote "openURL($@,new-tab)") ||
./firefox $@ ) &> /dev/null &
see the last comments in bug 246166

--help is out of date and inaccurate (i.e. it lists -splash, which segfaults :)

*** This bug has been marked as a duplicate of 246166 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Need to update firefox --help then.
Status: RESOLVED → VERIFIED
Flags: blocking0.9?
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.