Firefox 3.5.3pre: Restart launches /usr/bin/firefox regardless of the original launch command.

Bug #416627 reported by aslam karachiwala on 2009-08-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Low
Unassigned
firefox-3.5 (Ubuntu)
Medium
Micah Gersten

Bug Description

Binary package hint: firefox-3.5

Originally reported as a Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=510403

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3pre)
Gecko/20090813 Ubuntu/9.04 (jaunty) Shiretoko/3.5.3pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3pre)
Gecko/20090813 Ubuntu/9.04 (jaunty) Shiretoko/3.5.3pre

/usr/bin/firefox --> /opt/firefox/firefox (Ubuntuzilla; FF 3.5.1)
/usr/bin/firefox-3.5 --> /usr/lib/firefox-3.5.3pre/firefox.sh

Original FF session command:
> /usr/bin/firefox-3.5 -P akDefault -no-remote %u

When I do a Restart from this session, the newly started session starts using
/usr/bin/firefox with the same profile.

I believe this started happening after the last nightly update.

Reproducible: Always

Steps to Reproduce:
1. Have 2 installs of FF -- see the versions in the Details above.
2. Launch FF 3.5.3pre as explained in the Details.
3. Restart.
Actual Results:
See Details above.

Expected Results:
Restart should relaunch using the same command as the original session.

What appears to be happening is that /usr/bin/firefox-3.5 (see symbolic links
in the description) causes /opt/firefox/firefox-bin (see description) to
launch, when it should be launching the appropriate executable in
/usr/lib/firefox-3.5.3pre/.

Besides Restart, the same thing happens if FF is shutdown after an add-on
update, and started anew manually. If an add-on update hasn't happened in the
terminated session then the next launch uses the correct executable.

Micah Gersten (micahg) wrote :

Thank you for reporting this to Ubuntu. This report has enough information for a developer to start working on it. Please feel free to report any other issues you may have.

Changed in firefox-3.5 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 affects ubuntu/firefox-3.0
 status Triaged
 importance Low
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqN6N8ACgkQTniv4aqX/Vmb1ACeKk7ciKhX3tFZ19td3VQpqVpp
rOYAnRjuyV+5uHJnULlP3BVTNemsHYhd
=vD6S
-----END PGP SIGNATURE-----

Micah Gersten (micahg) on 2009-08-27
Changed in firefox-3.5 (Ubuntu):
assignee: nobody → Micah Gersten (micahg)
status: Triaged → In Progress
Micah Gersten (micahg) on 2009-11-11
Changed in firefox-3.5 (Ubuntu):
milestone: none → lucid-alpha-2
Micah Gersten (micahg) on 2009-12-17
Changed in firefox-3.5 (Ubuntu):
milestone: lucid-alpha-2 → ubuntu-10.04-beta-1
Micah Gersten (micahg) wrote :

Not actually working on this right now. Although, I think it might be fixed in Firefox 3.6, but needs testing.

Changed in firefox-3.5 (Ubuntu):
milestone: ubuntu-10.04-beta-1 → ubuntu-10.04-beta-2
status: In Progress → Triaged
aslam karachiwala (akwala) wrote :

Confirming that it's fixed in FF 3.6.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers