[gutsy] cannot report bug in system update when firefox already running

Bug #149279 reported by parren
8
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: apport

When a bug like:

E: /var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_i386.deb: trying to overwrite `/usr/share/doc/libcupsys2/CREDITS.txt', which is also in package libcupsys2

happens during system update, apport starts, but cannot open the browser. It tells me to close firefox first:

Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.

Revision history for this message
Oded Arbel (oded-geek) wrote :

I'm pretty sure there was another bug report for this behavior - one which has more comments - but I can't find it right now.

As it just happened to me again, I wanted to note that this problem induces data loss - when apport tries to open firefox to report on a problem, if it can't launch the bug report url, the bug report data is lost - you get no option to close the firefox and retry.

Revision history for this message
Martin Pitt (pitti) wrote :

Indeed there have been several bugs about this already (bug 81207 and bug 96503).

What does
  gconftool --get /desktop/gnome/url-handlers/http/command

print for you?

Changed in apport:
status: New → Incomplete
Revision history for this message
parren (peter-arrenbrecht) wrote : Re: [Bug 149279] Re: [gutsy] cannot report bug in system update when firefox already running

Here you go:

$ gconftool --get /desktop/gnome/url-handlers/http/command
firefox %s

-peo

Revision history for this message
Martin Pitt (pitti) wrote :

Ah, thanks. So you do have the standard browser setting, and apport is just calling "firefox -new-window https://launchpad....". That seems to be a bug in the firefox wrapper script then.

Mozilla maintainers, do you have an idea how to debug this?

Changed in apport:
status: Incomplete → New
Revision history for this message
Juraj Lukac (hrasko) wrote :

Hi,
I have the same problem. It doesn't happen always but mostly it does. Sometimes it works.
gconftool gives me the same result:

$ gconftool --get /desktop/gnome/url-handlers/http/command
firefox %s

Juraj

Revision history for this message
sam tygier (samtygier) wrote :

still seeing this in hardy

Changed in firefox:
status: New → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

i am pretty sure this is resolved in jaunty. anyone still seeing this?

Changed in firefox (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Oded Arbel (oded-geek) wrote :

I don't see this problem in Karmic, and I'm pretty sure it didn't exist in Jaunty

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.