No indication to the user that a core dump is in progress

[Matt Zimmerman]

Recently, my firefox crashed due to a plugin bug. After the window disappeared, I naturally tried to start it again, but was told that it was already running. I waited and tried again a couple of times before I realized the problem, which was that it was dumping an enormous core file.

Perhaps this is only an issue for programs like firefox which try to prevent concurrent instances.

[Martin Pitt (pitti)]

In the future we might add a small icon to update-notifier that informs about an ongoing crash dump. Also, in edgy+1 the kernel->apport protocol will be different and I have some ideas how to make apport block the crashed application much shorter than it is now.

[Martin Pitt (pitti)]

Version 0.24 should be magnitudes faster now, so the need for this became less urgent. However, I'll discuss this with Michael.

[Martin Pitt (pitti)]

This needs coordination wtih update-notifier. I propose to add a new exit code to apport-checkreports: it would exit with '2' if there is an ongoing apport process. Michael, what do you think?

And then we need a nice icon...

[Michael Vogt (mvo)]

If that is something we should have for edgy then please let me know about it and I will work on the update-notifier side. It shouldn't be hard.

[Matt Zimmerman (mdz)]

On Mon, Oct 02, 2006 at 12:30:35PM -0000, Michael Vogt wrote:
> If that is something we should have for edgy then please let me know
> about it and I will work on the update-notifier side. It shouldn't be
> hard.

According to Martin, it should be quick enough now that we don't need to do
this.

--
 - mdz

[Michael Vogt (mvo)]

If this is quick enough now, I close the bug.

[Martin Pitt (pitti)]

Closing apport task as well then. (Quick enough now)