Firefox in Jaunty made messy upgrade to Karmic

Bug #476370 reported by Duncan Lithgow
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox-3.5 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: firefox

I wanted to report a bug in Firefox (3.5.4) but I can't vis 'Help > Report a Problem'. It goes through the motion but never opens a new tab for me to use. When I start firefox from the cli I get the following output:

(firefox:2258): Gdk-WARNING **: XID collision, trouble ahead [repeated more than I have space for in the cli]
(firefox:2258): Gdk-WARNING **: XID collision, trouble ahead
Warning: The options -p/-P are deprecated, please do not use them. See /usr/bin/ubuntu-bug --help
Error showing url: Failed to execute child process "/home/duncan/bin/firefox/firefox" (No such file or directory)
Error showing url: Failed to execute child process "/home/duncan/bin/firefox/firefox" (No such file or directory)

Probably the core problem here is that I installed Firefox 3.5 in Jaunty manually and the upgrade to karmic has messed things up. The reason there is an error with the URL is that there is no longer a /home/duncan/bin on my system, although that's where I had installed 3.5 under Jaunty. I deleted that bin directory after the upgrade to Karmic as I assumed that I had a clean new copy of Firefox.

So, Ubuntu needs to find a cleaner way to upgrade when an application has been manually installed somewhere non-standard.

If someone can tell me where to find the files generated by apport before they are overwritten I will happily upload them.

Tags: jaunty karmic
Revision history for this message
Camille Appert (bibinou) wrote :

> Ubuntu needs to find a cleaner way to upgrade when an application has been manually installed somewhere non-standard.

There was a firefox-3.5 package in Jaunty as there is a firefox-3.6 one in Karmic to address this very problem.

What is the output of
"which firefox"
 and
"ls -l firefox"
?

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote : Re: [Bug 476370] Re: Firefox in Jaunty made messy upgrade to Karmic

duncan@duncan-laptop:~$ which firefox
/usr/bin/firefox

duncan@duncan-laptop:/usr/bin$ ls -l firefox
lrwxrwxrwx 1 root root 11 2009-11-05 22:02 firefox -> firefox-3.5

Camille Appert (bibinou)
Changed in firefox (Ubuntu):
status: New → Invalid
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

@Camille: Please explain why this is invalid.

Changed in firefox (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Micah Gersten (micahg) wrote :

Moving to Firefox 3.5 for triage

affects: firefox (Ubuntu) → firefox-3.5 (Ubuntu)
Revision history for this message
Micah Gersten (micahg) wrote :

This is invalid because Firefox installed properly during the upgrade. You might need to get rid of any manual shortcuts you made to the Mozilla version of Firefox you installed. Your system is set up to use the correct copy of Firefox. If you need more help, I suggest posting to the answers section. Please report any issues you have with the system version of Firefox.

Changed in firefox-3.5 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

@Micah: But the upgrade did not make a working shortcut in the main menu for me. If it had there wouldn't be any problem to report. I know that Firefox is installed and working, because I can start it from the cli, but there is no menu entry.

Changed in firefox-3.5 (Ubuntu):
status: Invalid → Incomplete
Phillip Susi (psusi)
tags: removed: upgrade
Revision history for this message
Micah Gersten (micahg) wrote :

Did you have a manual shortcut in your home directory for firefox? That might have caused the non-working shortcut in the menu.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for firefox-3.5 (Ubuntu) because there has been no activity for 60 days.]

Changed in firefox-3.5 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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