looping when it's your browser that's crashing

Bug #61106 reported by Brian J. Murrell
4
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

If your web browser (i.e. Bon Echo b1 from only a few days ago) is the application that has crashed/is crashing, apport does it's thing and then tries to bring up the launchpad site in your browser, which is a second crash, causing a second navigation to the launchpad website which causes a third browser crash, and third navigation and on it goes.

Somehow apport needs to break this cycle.

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

Confirmed. This is a pretty tricky use case, especially since firefox is not hardcoded into apport (it uses gnome-open, which respects the user's configuration of default browser).

However, since apport-gtk never opens the browser automatically, but just after clicking 'Report a bug', it's not too bad for now, since users will recognize this pretty easily.

When we have a proper bug reporting tool, this will sort out itself.

Changed in apport:
importance: Untriaged → Low
status: Unconfirmed → Confirmed
Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 61106] Re: looping when it's your browser that's crashing

On Tue, 2006-19-09 at 11:09 +0000, Martin Pitt wrote:
> Confirmed. This is a pretty tricky use case, especially since firefox is
> not hardcoded into apport (it uses gnome-open, which respects the user's
> configuration of default browser).
>
> However, since apport-gtk never opens the browser automatically, but
> just after clicking 'Report a bug', it's not too bad for now, since
> users will recognize this pretty easily.

Are you sure? I am pretty sure I would have thought to not want to
actually click that button due to the predictable result, yet I still
saw this endless loop any time Bon Echo crashed. I usually had to try
to kill apport and apport-gtk to break the cycle.

b.

--
My other computer is your Microsoft Windows server.

Brian J. Murrell

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

I could never reproduce this, nor did I hear similar reports. In Feisty it is not an issue anyway, since we tightened the restart function to programs in /usr/bin (and firefox-bin isn't), so it's not an issue any more anyway.

Also, Feisty has a completely new user interface implementation which probably behaves differently wrt. this issue anyway.

Do you still have this problem and can reproduce it somehow?

Changed in apport:
status: Confirmed → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote :

I am closing this bug due to inactivity and because it is not a problem in Feisty (see previous comment). I will reopen it if you still have an issue with this and report back. Thank you!

Changed in apport:
status: Needs Info → Fix Released
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.