No indication to the user that a core dump is in progress
Bug #61730 reported by
Matt Zimmerman
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
update-notifier (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
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.
Changed in apport: | |
importance: | Untriaged → Low |
To post a comment you must log in.
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.