Closed
Bug 246166
Opened 21 years ago
Closed 21 years ago
firefox -remote - Error: No running window found
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: tomas, Assigned: bugs)
References
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+
I use command
firefox -remote "openURL(http://root.cz/)"
Error: No running window found
Firefox running, of course. Older nightbuilds was OK, but RC is wrong.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I can confirm this with here, also with Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.7) Gecko/20040608 Firefox/0.8.
It may be a duplicate of #246168.
Comment 2•21 years ago
|
||
*** Bug 246310 has been marked as a duplicate of this bug. ***
This bug is present in 0.9:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9
Comment 4•21 years ago
|
||
Marking as NEW (per dupe and user comments).
If I understand problem clearly, this bug affects for example Thunderbird users.
Asking for Firefox 1.0 blocking.
Should this belongs to OS Integration component?
Assignee: firefox → bugs
Status: UNCONFIRMED → NEW
Component: General → OS Integration
Ever confirmed: true
Flags: blocking1.0?
QA Contact: firefox.general → firefox.os-integration
Comment 5•21 years ago
|
||
Workaround (idea from Bug 246644):
Instead of
firefox -remote "openUrl(http://foo.bar)"
use
./run-mozilla.sh ./mozilla-xremote-client -a firefox "openUrl(http://foo.bar)"
Comment 6•21 years ago
|
||
An even easier workaround:
firefox -a firefox -remote "openURL(...)"
found here: Bug 246168
Comment 7•21 years ago
|
||
(In reply to comment #5)
> Workaround (idea from Bug 246644):
> Instead of
> firefox -remote "openUrl(http://foo.bar)"
>
> use
>
> ./run-mozilla.sh ./mozilla-xremote-client -a firefox "openUrl(http://foo.bar)"
you must then first cd to the install directory of firefox.
Comment 8•21 years ago
|
||
*** Bug 246027 has been marked as a duplicate of this bug. ***
Comment 9•21 years ago
|
||
Comments here: http://lwn.net/Articles/89519/ (3/4 of the way down the page or
so) suggest that this is a problem with the profile dir change. However,
editing the firefox script as suggested doesn't solve the problem for me, so I
can't confirm that it is indeed the cause.
And yes, this is the same as bug 246168 so one of them should be duped.
Comment 10•21 years ago
|
||
*** Bug 247319 has been marked as a duplicate of this bug. ***
Comment 11•21 years ago
|
||
*** Bug 247352 has been marked as a duplicate of this bug. ***
Comment 12•21 years ago
|
||
(In reply to comment #6)
> An even easier workaround:
> firefox -a firefox -remote "openURL(...)"
>
> found here: Bug 246168
This only works without the new-window or new-tab options otherwise it returns with:
Error: Failed to send command: 509 internal error
this from:
./firefox -a firefox -remote 'openURL('www.mozilla.org', new-tab)'
Comment 13•21 years ago
|
||
(In reply to comment #12)
> (In reply to comment #6)
> > An even easier workaround:
> > firefox -a firefox -remote "openURL(...)"
> This only works without the new-window or new-tab options otherwise it returns
> with:
> Error: Failed to send command: 509 internal error
> this from:
> ./firefox -a firefox -remote 'openURL('www.mozilla.org', new-tab)'
Use ./firefox -a firefox -remote "openURL(www.mozilla.org,new-tab)"
or ./firefox -a firefox -remote 'openURL(www.mozilla.org,new-tab)'
Comment 14•21 years ago
|
||
*** Bug 246644 has been marked as a duplicate of this bug. ***
Comment 15•21 years ago
|
||
(In reply to comment #13)
> > Error: Failed to send command: 509 internal error
> > this from:
> > ./firefox -a firefox -remote 'openURL('www.mozilla.org', new-tab)'
>
> Use ./firefox -a firefox -remote "openURL(www.mozilla.org,new-tab)"
> or ./firefox -a firefox -remote 'openURL(www.mozilla.org,new-tab)'
It is important to note that
./firefox -a firefox -remote "openurl(www.mozilla.org,new-window)"
WORKS, but
./firefox -a firefox -remote "openurl(www.mozilla.org, new-window)"
FAILS with "Error: Failed to send command: 509 internal error"
The difference between those two commands is that there is a space between the
openURL() parameters.
Comment 16•21 years ago
|
||
that's fixed on trunk, blizzard did it. Someone please file a bug assigned to
me to backport that to aviary :)
Comment 17•21 years ago
|
||
Yeah, sounds like a dup of bug #242123.
Comment 18•21 years ago
|
||
*** Bug 248149 has been marked as a duplicate of this bug. ***
Comment 19•21 years ago
|
||
Merged bug 242123 fix from the trunk to the aviary branch, and merged bug 244060
fix from the aviary branch to the trunk, so I think everything mentioned here is
now fixed.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 20•21 years ago
|
||
Does that mean that it should be fixed for 0.9.1? It's not the case AFAICS.
Comment 21•21 years ago
|
||
er, Firefox 0.9.1 was released 8-10 days before the fix was checked in, so no.
1.0 RC1 will have the fix.
Comment 22•21 years ago
|
||
*** Bug 251518 has been marked as a duplicate of this bug. ***
Comment 23•21 years ago
|
||
*** Bug 254588 has been marked as a duplicate of this bug. ***
Comment 24•21 years ago
|
||
*** Bug 252265 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Flags: blocking-aviary1.0?
Comment 25•21 years ago
|
||
*** Bug 256344 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•