The script /usr/bin/firefox does not correctly handle its arguments. It does able to deal with a call like "firefox -remote 'openURL(http://www.gentoo.org, new-window)", which did work with mozilla-firebird. It just resumes to calling "/usr/lib/MozillaFirefox/mozilla-xremote-client 'openURL(, new-tab)'". Reproducible: Always Steps to Reproduce: 1. Emerge net-www/mozilla-firefox-0.8 2. Execute the command: firefox -remote 'openURL(http://www.gentoo.org, new-window)' Actual Results: Mozilla Firefox opens with an empty window. Expected Results: Mozilla Firefox should open "http://www.gentoo.org" Debugging: $ bash -x firefox -remote 'openURL(http://www.gentoo.org, new-window)' [...] + declare -a 'args=(-remote openURL(http://www.gentoo.org, new-window))' firefox: array assign: line 22: syntax error near unexpected token `(' firefox: array assign: line 22: `-remote openURL(http://www.gentoo.org, new-window)' [...] + /usr/lib/MozillaFirefox/mozilla-xremote-client 'openURL(, new-tab)'
Exactly the same bug here.
change the "fbpath" variant to "ffpath" in /usr/bin/firefox that works for me.
I do not see how this can help. /usr/bin/firefox has the following lines: export MOZILLA_FIVE_HOME="/usr/lib/MozillaFirefox" fbpath=${MOZILLA_FIVE_HOME} It should make no difference if fbpath is renamed to ffpath.
Same here but solved. emerge net-www/mozilla-firefox 0.8 and /usr/bin/firefox leads only to an error in line 104 (file not found). Problem was that in the beginning there is: ffpath=${MOZILLA_FIVE_HOME} but later on is asked for fbpath. Replaced all occurences of fbpath with ffpath solved the problem for me.
Problems: (1) array assign: line 22: syntax error ... This is actually a bash bug, which I've reported, but also worked around in the script. (2) inconsistent use of ffpath vs fbpath ... fixed in the script (by Brad, who hardly complained at all that I'd broken it ;-) These are both fixed in the portage tree. After syncing, you can copy the script from /usr/portage/net-www/mozilla-firefox/files/firefox to /us/bin and you should be all set.
marking fixed
*** Bug 42142 has been marked as a duplicate of this bug. ***