Remote fail with a mix of old and new firefox.

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
4 years ago
2 years ago

People

(Reporter: hub, Unassigned)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Following up on bug 1080319

Since then, if you try to open an URL with using the old xremote client when you run nightly, it fail, and will make subsequent attempt even with nightly fail until restart of nightly.

STR:
- Install Nightly on a system that has Firefox 33.1 (Fedora 21 here). Firefox 33.1 comes from the distro
- Start Nightly. You can restore your session.
- On the command line "<path/to/nightly> http://gnome.org/" will open the URL in the currently running browser.
- On the command line, "firefox http://gnome.org/" should start Firefox 33.1 to run the xremote-client and open it. It fails. It mostly hangs.
- - On the command line "<path/to/nightly> http://gnome.org/" will show the profile chooser (it is enabled by default here) or a new window (if disable).

In nsAppRunner.cpp, client.SendCommandLine() returned a failure. ~line 1649

If I never try with the older Firefox, it works alright.
(Reporter)

Updated

4 years ago
Blocks: 1080319
(In reply to Hubert Figuiere [:hub] from comment #0)
> - On the command line, "firefox http://gnome.org/" should start Firefox 33.1
> to run the xremote-client and open it.

What the what? What is "firefox" on Fedora? a shell script?
(Reporter)

Comment 2

4 years ago
Yes it is a script. Seems to be RH / RPM distro specific.
(Reporter)

Comment 3

4 years ago
This is the source code in git for the package.

http://pkgs.fedoraproject.org/cgit/firefox.git/tree/firefox.sh.in
What if you use /usr/lib{64,}/firefox/firefox instead of that /usr/bin/firefox script?
(Reporter)

Comment 5

4 years ago
Mmmm. Indeed this works. So I guess this is a horrible packaging bug.

Comment 6

2 years ago
Mass resolving a bunch of old bugs in the x-remote component in preparation for archiving it. If this bug is still valid and useful, please move it to the "Toolkit: Startup and Profile System" component and reopen it.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
(Reporter)

Comment 7

2 years ago
It ended up working after a while, either because of the trains or else. And I no longer run nightly / inbound anyway so it's not impacting me anymore.

Thanks
You need to log in before you can comment on or make changes to this bug.