Firefox no longer supports -remote parameter

Bug #1425972 reported by David Pottage on 2015-02-26
218
This bug affects 42 people
Affects Status Importance Assigned to Milestone
GNU Emacs
Unknown
Unknown
Mozilla Firefox
Fix Released
Medium
Python
New
Unknown
exo
Fix Released
Medium
emacs24 (Ubuntu)
Medium
Unassigned
Trusty
Medium
Unassigned
Utopic
Medium
Unassigned
exo (Debian)
New
Unknown
exo (Ubuntu)
Medium
Unassigned
Trusty
Medium
Unassigned
Utopic
Medium
Unassigned
firefox (Ubuntu)
High
Unassigned
Trusty
High
Unassigned
Utopic
High
Unassigned

Bug Description

[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped. This parameter is used in versions of exo prior to 0.10.3. Because of this, opening any URLs via exo-open will cause a new firefox window to launch at the home screen.

As reported, this affects the terminal, ubuntu-bug, xchat, and numerous other applications.

[Test Case]
1. Set Firefox as the default web browser in "Preferred Applications".
2. From a terminal, type the following:

exo-open "http://www.xfce.org"

Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.

[Regression Potential]
No regressions by this change. This fixes the application call to correctly open URLs.

---

[Original Report]
When I click a link from an email it does not work any more.

Instead of opening the link in a new tab, Firefox opens a new empty window and does not follow the link.

If I change the default browser for my desktop from Firefox to Chrome, then Chrome can open the link fine.

I have started seeing this today since firefox was upgraded from v35 to 36.

My email client is Mozilla thunderbird at the latest stable version.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dpottage 3729 F.... pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions:
 English (South Africa) Language Pack - <email address hidden>
 English (GB) Language Pack - <email address hidden>
 Français Language Pack - <email address hidden>
 Deutsch (DE) Language Pack - <email address hidden>
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
IpRoute:
 default via 192.168.1.254 dev eth0 proto static
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric 1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
 LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so (browser-plugin-libreoffice)
 Java(TM) Plug-in 11.25.2 - /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.

Created attachment 6003
fix helper commands for Firefox 36.0

Firefox 36.0 dropped support for command line argument -remote. This
changes desktop helper file to call firefox with argument -new-tab.

(In reply to Christian Hesse from comment #1)
> Created attachment 6003 [details]
> fix helper commands for Firefox 36.0
>
> Firefox 36.0 dropped support for command line argument -remote. This
> changes desktop helper file to call firefox with argument -new-tab.

According to the mozilla bug, the equivalent of "-remote 'openURL(url)'" is "firefox url".

We also need to fix the icecat and iceweasel helpers. I'm build those now to see how they behave and if any options are needed.

10 comments hidden view all 147 comments
11 comments hidden view all 147 comments

Created attachment 6004
Drop use of the -remote option in Firefox helpers

The attached patch works for me. 'exo-open --launch WebBrowser' opens a new browser window and 'exo-open url' opens the url in a new tab (for all three changed helpers).

Tested browsers:

 - Firefox 36.0
 - Iceweasel 36.0
 - IceCat 31.4.0

10 comments hidden view all 147 comments
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Changed in firefox (Ubuntu):
importance: Undecided → Medium
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → Medium
Jeffrey DeLeo (jeffreydeleo) wrote :

I am seeing the same problem clicking on a link from emacs - where it used to go to the link, now I just get a new window.
Can get some links to work - clicking a link in terminal, and selecting "open link", works OK.
Notice that "/usr/share/applications/firefox.desktop" was just changed, is there a change in option syntax?

10 comments hidden view all 147 comments
9 comments hidden view all 147 comments
Marcin Sochacki (wanted) wrote :

The root cause is removing the "-remote" option in Firefox 36:
https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#Remote_Control
https://bugzilla.mozilla.org/show_bug.cgi?id=1080319

I'm running XFCE and the option is used in /usr/share/xfce4/helpers/firefox.desktop.

Workaround:
replace the last line in /usr/share/xfce4/helpers/firefox.desktop with:
X-XFCE-CommandsWithParameter=%B -new-tab "%s";%B "%s";

Thanks. @wanted

That workarround fixed the problem for me, and should be an easy fix for the Ubuntu package maintainers to put into the next release.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in exo (Ubuntu):
status: New → Confirmed
Ivan Frederiks (idfred) wrote :

@wanted

I think than one has to replace last two lines:

X-XFCE-Commands=%B -new-window "about:blank";%B;
X-XFCE-CommandsWithParameter=%B -new-tab "%s";%B %s;

Jeffrey DeLeo (jeffreydeleo) wrote :

Yes, the problem is the remote option going away. The emacs function "browse-url-firefox" uses the remote option on non-ms-dos systems. Changing that function to not use the remote option solves the problem.

Marcin Sochacki (wanted) wrote :

@idfred:
yes, of course that is the complete fix

affects: firefox → exo
Changed in firefox (Ubuntu):
status: Confirmed → Invalid
summary: - Links from thunderbird email do not work
+ Firefox no longer supports -remote parameter
Changed in exo:
importance: Unknown → Medium
status: Unknown → Fix Released
5 comments hidden view all 147 comments
affects: firefox (Ubuntu) → emacs-defaults (Ubuntu)
Changed in emacs-defaults (Ubuntu):
status: Invalid → Confirmed
affects: emacs-defaults (Ubuntu) → emacs24 (Ubuntu)
Marcin Sochacki (wanted) wrote :

Perhaps it would make sense to make a proactive search of other packages in Ubuntu (and Debian) which could be affected.

This tool can be of help:
https://codesearch.debian.net/results/remote.*openurl/page_0

Changed in exo (Ubuntu):
importance: Undecided → Medium
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1425972

tags: added: iso-testing
ajgreeny (ajg-charlbury) wrote :

This comment is copied from my entry in https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144

I also had this problem, not only with links in Thunderbird but also in Libreoffice documents, which both opened Firefox at my chosen homepage, not the link URL.
I have always changed my Preferred Application setting in XFCE Settings-manager to firefox rather than Debian Sensible Browser which is the default, and this never before caused any problem. With the upgrade to FF36 this seems to have broken.
Changing the Preferred Application back to Debian Sensible Browser seems to have fixed this and links are again opening in Firefox to the URL of the clicked link.

I have not tested George Shuklin's solution above yet, but will investigate later. (# NB This comment relates to the bug I mention above, not this one so the solution from George is there, not here.)

I have responded to a Ubuntuforum post with this and previous workarounds for this problem
See http://ubuntuforums.org/showthread.php?t=2267439

I am using Xubuntu 14.04.2 64bit.
uname -a output:-
Linux XubuntuTrusty 3.13.0-46-generic #76-Ubuntu SMP Thu Feb 26 18:52:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Unit 193 (unit193) wrote :

Attached is a debdiff for trusty.

Unit 193 (unit193) wrote :
Unit 193 (unit193) wrote :

When is a patch coming to precise?

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

Brian Murray (brian-murray) wrote :

The convention for package version is to use the release so instead of 0.10.2-4ubuntu0.2 use 0.10.2-4ubuntu0.14.10.1. With the version numbers that you've used if the Trusty version of the package needs an update that the Utopic version doesn't we'll need to become creative with the version numbers. See the following link for the convention:

https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging

Brian Murray (brian-murray) wrote :

Actually 0.10.2-4, isn't even in trusty so the version number for the trusty upload makes even less sense.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in emacs24 (Ubuntu Trusty):
status: New → Confirmed
Changed in emacs24 (Ubuntu Utopic):
status: New → Confirmed
Changed in exo (Ubuntu Trusty):
status: New → Confirmed
Changed in exo (Ubuntu Utopic):
status: New → Confirmed
3 comments hidden view all 147 comments
Damian Yerrick (tepples) wrote :

Just in case others are searching for the symptoms I'm seeing in Xubuntu 14.04:

* Following links in XChat opens a new empty Firefox window
* ubuntu-bug opens a new empty Firefox window

Sean Davis (bluesabre) on 2015-03-04
description: updated
Sean Davis (bluesabre) on 2015-03-04
Changed in exo (Ubuntu Utopic):
status: Confirmed → In Progress
Sean Davis (bluesabre) wrote :

Attaching debdiff for trusty.

Changed in exo (Ubuntu Trusty):
status: Confirmed → In Progress
76 comments hidden view all 147 comments

I wish I had found this earlier, but my code breaking with the last update seems to have 'informed' me... :( I too have a big problem with removing this.

Any suggestions in this new world on how the following might be implemented? Essentially part of a bigger program that gives a menu of profiles to invoke, creates a new window if it's the first instance of that profile, or adds on if not (to get around 'firefox is already running' error). Using -no-remote doesn't work and all new instances now either fail or open in the first profile called with other variations tried.

1) firefox -P generic1 -remote "ping()"
   if [ ! $? == 0 ]; then
 nohup firefox -P generic1 -new-instance $URL 2>&1 >/dev/null &
   else
 nohup firefox -P generic1 -remote "openurl($URL,new-window)" 2>&1>/dev/null &
   fi
 ;;

To update after installing the restore-remote add-in, assume cases 1,2,3... from above. I start 1. I then start 2. It doesn't complain, but the new window is in profile 1, not 2!

Also tested with instances of 1 and 2 running, then opening another telling it profile 2. It came up in profile 1, which was the first one started of the 3 windows...

Still need a working method.

76 comments hidden view all 147 comments

In Xubuntu 12.04.5 with xfdesktop 4.8.3-2ubuntu7 clicking links in pidgin 1:2.10.3-0ubuntu1.6 opens a Firefox new window with the homepage set in Firefox, although clicking links in e-mails in thunderbird 1:31.5.0+build1-0ubuntu0.12.04.1 opens the link in a new Firefox tab (normal/expected bahviour).

My last lines in /usr/share/xfce4/helpers/firefox.desktop are:

X-XFCE-Binaries=firefox;firefox-gtk2;firefox-gtk;mozilla-firefox;
X-XFCE-Category=WebBrowser
X-XFCE-CommandsWithParameter=%B -new-tab "%s)";%B %s;

77 comments hidden view all 147 comments

Created attachment 8573128
Backout the part that removed -remote

Approval Request Comment
[Feature/regressing bug #]: this bug
[User impact if declined]: Among many things, python's webbrowser module doesn't work properly.
[Describe test coverage new/current, TreeHerder]: https://treeherder.mozilla.org/#/jobs?repo=try&revision=e8d349c9a6d0 (this is orange because I changed the mozconfigs to match those of release)
[Risks and why]: This is the opposite of the patch that landed, except for the removal of the mozilla-xremote-client executable, which stays removed. Call that a partial backout. This is the low-risk option. Other branches will be dealt with differently. -release needs something simple.
[String/UUID change made/needed]: None

I verified if disabled on:

FF 36.0.1
Build Id:20150305021524
OS: Ubuntu 14.04 x64

The following commands:

-remote 'openURL(url)'
-remote 'openURL(url,new-tab)'
-remote 'openURL(url,new-window)'
-remote 'openfile(file)'

were verified and are working properly.

It would be really nice if -new-window and -new-tab had the same behavior whether or not a browser is already running. Currently if no browser is running, 'firefox -new-window <url>' does not exit with a status code after the URL is opened (i.e. it waits for all windows to be closed before exiting), however if a browser is already running, this command does exit immediately, presumably with a status code indicating success.

(In reply to Catalin Varga [QA][:VarCat] from comment #66)
> I verified if disabled on:
>
> FF 36.0.1
> Build Id:20150305021524
> OS: Ubuntu 14.04 x64
>
> The following commands:
>
> -remote 'openURL(url)'
> -remote 'openURL(url,new-tab)'
> -remote 'openURL(url,new-window)'
> -remote 'openfile(file)'
>
> were verified and are working properly.

How about -remote 'ping()', or is that not supported with this reversion?

The way the old code worked, I needed to first detect if a firefox profile was running before I could do a -remote 'openURL(url,new-window)', otherwise I needed to do -new-instance url.

Here's an example of what I'm doing to launch windows into two different simultanously running firefox profiles.

if $firefoxpath -P $profile -remote 'ping()' > /dev/null 2>&1; then
  $firefoxpath -P $profile -remote "openurl($url,new-window)"
else
  $firefoxpath -P $profile -new-instance $url
fi

80 comments hidden view all 147 comments

Hello David, or anyone else affected,

Accepted exo into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/exo/0.10.2-3ubuntu1.14.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in exo (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed

I can confirm this bug, and that the fix mentioned in comment #7 (https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1425972/comments/7) resolves it.

Greg (thorn-m) wrote :

# 7 fixed it for me too. Clicking on links in Thunderbird that went to a new blank Firefox window was driving me crazy after the recent update.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu Trusty):
status: New → Confirmed
Changed in firefox (Ubuntu Utopic):
status: New → Confirmed
Changed in firefox (Ubuntu):
status: New → Confirmed
2 comments hidden view all 147 comments
Jochen Seidel (x+launchpad) wrote :

The proposed package fixed the bug for me.

tags: added: verification-done-trusty
removed: verification-needed
Ivan Frederiks (idfred) wrote :

LOL, Firefox developers returned -remote option in 36.0.1

Changed in exo (Debian):
status: Unknown → New
Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Changed in firefox:
importance: Unknown → Medium
status: Unknown → Fix Released
74 comments hidden view all 147 comments

Quick update, another thing this broke is the Windows 7 + jump menu:
http://i.imgur.com/OiyEzUI.png

(In reply to noitidart from comment #69)
> Quick update, another thing this broke is the Windows 7 + jump menu:
> http://i.imgur.com/OiyEzUI.png

This makes no sense, those are not using -remote: https://dxr.mozilla.org/mozilla-central/source/browser/modules/WindowsJumpLists.jsm#91

(In reply to Mike Hommey [:glandium] from comment #70)
> (In reply to noitidart from comment #69)
> > Quick update, another thing this broke is the Windows 7 + jump menu:
> > http://i.imgur.com/OiyEzUI.png
>
> This makes no sense, those are not using -remote:
> https://dxr.mozilla.org/mozilla-central/source/browser/modules/
> WindowsJumpLists.jsm#91

Ah you're right excuse that then. I don't know why it keeps telling me "Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window".

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 36.0.1+build2-0ubuntu0.14.10.1

---------------
firefox (36.0.1+build2-0ubuntu0.14.10.1) utopic-security; urgency=medium

  * New upstream stable release (FIREFOX_36_0_1_BUILD2)
    - see LP: #1429115
    - revert removal of the deprecated -remote command line option, as some
      older software (eg, Python 2.7's webbrowser module) still depends on it
      (LP: #1425972)
 -- Chris Coulson <email address hidden> Fri, 06 Mar 2015 12:43:36 +0000

Changed in firefox (Ubuntu Utopic):
status: Confirmed → Fix Released
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package firefox - 36.0.1+build2-0ubuntu0.14.04.1

---------------
firefox (36.0.1+build2-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * New upstream stable release (FIREFOX_36_0_1_BUILD2)
    - see LP: #1429115
    - revert removal of the deprecated -remote command line option, as some
      older software (eg, Python 2.7's webbrowser module) still depends on it
      (LP: #1425972)
 -- Chris Coulson <email address hidden> Fri, 06 Mar 2015 12:44:25 +0000

Changed in firefox (Ubuntu Trusty):
status: Confirmed → Fix Released

Just a note, the documentation should be updated that the feature has been re-included.

https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-remote_remote_command

(In reply to haarp from comment #72)
> Just a note, the documentation should be updated that the feature has been
> re-included.
>
> https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options#-
> remote_remote_command

Ok i can do that. Should i update it to say:
"Not availabile in Gecko 36.0, but available again since Gecko ?.?"

What should i put for "?.?"?

It's in 36.0.1, but it's guaranteed to still be there in 37.

So, if I'm following correctly: -remote was removed in Fx 36, readded in the chemspill 36.0.1 and won't be removed in 37 at least?

Is this correct (We also need to update Fx 36 for devs).

A tip that we'll help us: if you back-out a bug that has "dev-doc-complete", please turn it back to "dev-doc-needed", so the doc team is aware of the change.

(In reply to Jean-Yves Perrier [:teoli] from comment #75)
> So, if I'm following correctly: -remote was removed in Fx 36, readded in the
> chemspill 36.0.1 and won't be removed in 37 at least?
>
> Is this correct (We also need to update Fx 36 for devs).

Err, I missed a not in my sentence. It is *not* guaranteed to still be there in 37.

(In reply to Mike Hommey [:glandium] from comment #74)
> It's in 36.0.1, but it's guaranteed to still be there in 37.

Awesome thanks ill check docs and update if its not updated yet!

I don't think this works on windows.

I opened my 2nd profile with this:
firefox.exe -P Dev -no-remote

Then tried to open a new tab in that profile with this:
firefox.exe -P Dev -remote "openURL(http://www.bing.com,new-tab)"

it didnt work :(

(In reply to noitidart from comment #78)
> I opened my 2nd profile with this:
> firefox.exe -P Dev -no-remote

Try "firefox.exe -P Dev -new-instance"

(In reply to Pavlos Touboulidis from comment #79)
> (In reply to noitidart from comment #78)
> > I opened my 2nd profile with this:
> > firefox.exe -P Dev -no-remote
>
> Try "firefox.exe -P Dev -new-instance"

Thanks Pavlos I tried that.

1) firefox.exe -P Dev -new-instance
2) it opened new window of the current profile already open, it did not open my proflie named Dev

So i tried this:
1) firefox.exe -P Dev -new-instance -no-remote

this opened my profiled named Dev in parallel/concurrent to my other running profile
I then tried to remote it:
2) firefox.exe -P Dev -remote "openURL(http://www.bing.com,new-tab)"

but it just opens a new window in my first running profile, and it doesnt even point to bing.com just the homepage of that first running profile :(

(In reply to noitidart from comment #80)
> (In reply to Pavlos Touboulidis from comment #79)
> > (In reply to noitidart from comment #78)
> > > I opened my 2nd profile with this:
> > > firefox.exe -P Dev -no-remote
> >
> > Try "firefox.exe -P Dev -new-instance"
>
> Thanks Pavlos I tried that.
>
> 1) firefox.exe -P Dev -new-instance
> 2) it opened new window of the current profile already open, it did not open
> my proflie named Dev
>
> So i tried this:
> 1) firefox.exe -P Dev -new-instance -no-remote
>
> this opened my profiled named Dev in parallel/concurrent to my other running
> profile
> I then tried to remote it:
> 2) firefox.exe -P Dev -remote "openURL(http://www.bing.com,new-tab)"
>
> but it just opens a new window in my first running profile, and it doesnt
> even point to bing.com just the homepage of that first running profile :(

That's bug 1138053 and it's fixed in nightly. Use -new-tab instead of -remote, though.

Changed in emacs:
status: New → Fix Released
affects: hundredpapercuts → python
Changed in python:
importance: Medium → Unknown
status: Confirmed → Unknown
Changed in emacs:
importance: Undecided → Unknown
status: Fix Released → Unknown
Changed in python:
status: Unknown → New

Comment on attachment 8573128
Backout the part that removed -remote

Approval Request Comment: See comment 64

Considering how late we are in the beta cycle, it's more reasonable to get this on 37. 38 will get the alternative approach.

(In reply to Mike Hommey [:glandium] from comment #82)
> Comment on attachment 8573128
> Backout the part that removed -remote
>
> Approval Request Comment: See comment 64
>
> Considering how late we are in the beta cycle, it's more reasonable to get
> this on 37. 38 will get the alternative approach.

Aw darn are you sure we can't land it in 36? Then for backwards compatability addons have to work in an exception for just FF36. :( And I know software like Notepad++ and other softwares won't add in an exception for FF36. It will impact ESR when it gets to FF36 for the longest amount of time.

Just sharing my thoughts on some ways it hurts if we cant get it into FF36 but I appreciate you guys bringing it back, even if it doesnt get to FF36.

(In reply to noitidart from comment #83)
> (In reply to Mike Hommey [:glandium] from comment #82)
> > Comment on attachment 8573128
> > Backout the part that removed -remote
> >
> > Approval Request Comment: See comment 64
> >
> > Considering how late we are in the beta cycle, it's more reasonable to get
> > this on 37. 38 will get the alternative approach.
>
> Aw darn are you sure we can't land it in 36? Then for backwards
> compatability addons have to work in an exception for just FF36. :( And I
> know software like Notepad++ and other softwares won't add in an exception
> for FF36. It will impact ESR when it gets to FF36 for the longest amount of
> time.
>
> Just sharing my thoughts on some ways it hurts if we cant get it into FF36
> but I appreciate you guys bringing it back, even if it doesnt get to FF36.

Do you mean 38 everywhere you wrote 36? Do you also mean that notepad++ on windows is actually using the -remote option? And what addons are you talking about? Addons should not care about Firefox command line.

(In reply to Mike Hommey [:glandium] from comment #84)
> (In reply to noitidart from comment #83)
> > (In reply to Mike Hommey [:glandium] from comment #82)
> > > Comment on attachment 8573128
> > > Backout the part that removed -remote
> > >
> > > Approval Request Comment: See comment 64
> > >
> > > Considering how late we are in the beta cycle, it's more reasonable to get
> > > this on 37. 38 will get the alternative approach.
> >
> > Aw darn are you sure we can't land it in 36? Then for backwards
> > compatability addons have to work in an exception for just FF36. :( And I
> > know software like Notepad++ and other softwares won't add in an exception
> > for FF36. It will impact ESR when it gets to FF36 for the longest amount of
> > time.
> >
> > Just sharing my thoughts on some ways it hurts if we cant get it into FF36
> > but I appreciate you guys bringing it back, even if it doesnt get to FF36.
>
> Do you mean 38 everywhere you wrote 36? Do you also mean that notepad++ on
> windows is actually using the -remote option? And what addons are you
> talking about? Addons should not care about Firefox command line.

No man I was hoping for FF36 :( I'm addon dev and I use this command line.

Also this very popular addon uses the remote feature: https://addons.mozilla.org/en-US/firefox/addon/profileswitcher/

Yep Notepad++ when you do preview in webbrowser it wont open.
Also Camtasia screen recording software it wont open the generated video in firefox for preview/youtube.

(In reply to noitidart from comment #85)
> (In reply to Mike Hommey [:glandium] from comment #84)
> > (In reply to noitidart from comment #83)
> > > (In reply to Mike Hommey [:glandium] from comment #82)
> > > > Comment on attachment 8573128
> > > > Backout the part that removed -remote
> > > >
> > > > Approval Request Comment: See comment 64
> > > >
> > > > Considering how late we are in the beta cycle, it's more reasonable to get
> > > > this on 37. 38 will get the alternative approach.
> > >
> > > Aw darn are you sure we can't land it in 36? Then for backwards
> > > compatability addons have to work in an exception for just FF36. :( And I
> > > know software like Notepad++ and other softwares won't add in an exception
> > > for FF36. It will impact ESR when it gets to FF36 for the longest amount of
> > > time.
> > >
> > > Just sharing my thoughts on some ways it hurts if we cant get it into FF36
> > > but I appreciate you guys bringing it back, even if it doesnt get to FF36.
> >
> > Do you mean 38 everywhere you wrote 36? Do you also mean that notepad++ on
> > windows is actually using the -remote option? And what addons are you
> > talking about? Addons should not care about Firefox command line.
>
> No man I was hoping for FF36 :( I'm addon dev and I use this command line.

-remote was restored in 36.0.1 already. But maybe you're still talking about comment 80? In which case, it is not related to this bug.

> Yep Notepad++ when you do preview in webbrowser it wont open.

I just tested, and it works. Also, Notepad++ doesn't use -remote, it just invokes "firefox.exe edited-file-name".

(In reply to Mike Hommey [:glandium] from comment #86)
> (In reply to noitidart from comment #85)
> > (In reply to Mike Hommey [:glandium] from comment #84)
> > > (In reply to noitidart from comment #83)
> > > > (In reply to Mike Hommey [:glandium] from comment #82)
> > > > > Comment on attachment 8573128
> > > > > Backout the part that removed -remote
> > > > >
> > > > > Approval Request Comment: See comment 64
> > > > >
> > > > > Considering how late we are in the beta cycle, it's more reasonable to get
> > > > > this on 37. 38 will get the alternative approach.
> > > >
> > > > Aw darn are you sure we can't land it in 36? Then for backwards
> > > > compatability addons have to work in an exception for just FF36. :( And I
> > > > know software like Notepad++ and other softwares won't add in an exception
> > > > for FF36. It will impact ESR when it gets to FF36 for the longest amount of
> > > > time.
> > > >
> > > > Just sharing my thoughts on some ways it hurts if we cant get it into FF36
> > > > but I appreciate you guys bringing it back, even if it doesnt get to FF36.
> > >
> > > Do you mean 38 everywhere you wrote 36? Do you also mean that notepad++ on
> > > windows is actually using the -remote option? And what addons are you
> > > talking about? Addons should not care about Firefox command line.
> >
> > No man I was hoping for FF36 :( I'm addon dev and I use this command line.
>
> -remote was restored in 36.0.1 already. But maybe you're still talking about
> comment 80? In which case, it is not related to this bug.
>
> > Yep Notepad++ when you do preview in webbrowser it wont open.
>
> I just tested, and it works. Also, Notepad++ doesn't use -remote, it just
> invokes "firefox.exe edited-file-name".

Ohh! Thanks for the clarificaiton! Excuse that mixup im going to go to sleep late here :P

Comment on attachment 8573128
Backout the part that removed -remote

That being said, I can see a point in being more conservative for the upcoming ESR.

(In reply to Mike Hommey [:glandium] from comment #88)
> Comment on attachment 8573128
> Backout the part that removed -remote
>
> That being said, I can see a point in being more conservative for the
> upcoming ESR.

thanks :)

It isn't clear to me what the final resolution is. Is -remote going to stay, or will it be removed?

-remote has been part of the API for quite a long time. Pulling it without an _extended_ notification (on the order of a year, say) will inconvenience a lot of people. Firefox and Thunderbird are upgraded a lot more frequently than most packages, and you have no way of knowing what software out there relies on -remote. In particular, I know that GNU Emacs does, and it is not updated very often (the current release, 24.4, dates to 10/2014; the previous release, 24.3, dates to 03/2013).

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package exo - 0.10.2-3ubuntu1.14.04.2

---------------
exo (0.10.2-3ubuntu1.14.04.2) trusty-proposed; urgency=medium

  * Fix firefox helper being unable to open URLs (LP: #1425972)
 -- Sean Davis <email address hidden> Wed, 04 Mar 2015 19:02:35 -0500

Changed in exo (Ubuntu Trusty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for exo has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

(In reply to Robert Krawitz from comment #91)
> It isn't clear to me what the final resolution is. Is -remote going to
> stay, or will it be removed?

See Tracking Flags in the header of this bug (where "fixed" means removed)

The release notes for 36.0.3 still claim that the -remote option has been removed, even though it now hasn't.

ni Sylvestre for comment 93

Indeed. Removed. thanks

Changed in exo (Ubuntu):
status: Confirmed → Fix Released

This also breaks ubuntu-bug/apport-bug itself.
Report filed here: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1464053

Changed in exo (Ubuntu Utopic):
status: In Progress → Won't Fix
Changed in emacs24 (Ubuntu Utopic):
status: Confirmed → Won't Fix
Changed in emacs24 (Ubuntu):
status: Confirmed → Triaged
Mathew Hodson (mathew-hodson) wrote :

According to the upstream bug this is fixed in emacs 24.5, which has been uploaded to Wily.

Changed in emacs24 (Ubuntu):
status: Triaged → Fix Released
Changed in emacs24 (Ubuntu Trusty):
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in exo (Ubuntu Trusty):
importance: Undecided → Medium
Changed in emacs24 (Ubuntu Utopic):
importance: Undecided → Medium
Changed in exo (Ubuntu Utopic):
importance: Undecided → Medium
Changed in firefox (Ubuntu):
importance: Undecided → High
Changed in firefox (Ubuntu Trusty):
importance: Undecided → High
Changed in firefox (Ubuntu Utopic):
importance: Undecided → High
Displaying first 40 and last 40 comments. View all 147 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.