apport (0.21) edgy; urgency=low
.
* apport: Keep a partially written report with '000' permissions, and only
chmod it to 0600 when it is fully written. This stops update-notifier from
picking up half-written reports and get activated several times.
Closes: LP#59988
* apport:
Looping still occurs in 0.20.
--
Stuck in loop when Firefox crashed
https://launchpad.net/bugs/59988
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Heh, got it. update-notifier already picked up the new report although
it wasn't completely written yet. Since writing more to the file updates
the modification time again, u-n picked up various intermediate states.
Fixed in bzr head, will upload after the knot freeze.
** Changed in: apport (Ubun
I've seen this (or similar) from my Banshee cvs build.
After apport is triggered the window remains open indefinately, although not
redrawing.
Stopping the apport service or kill -9/-11 on the pid have no effect.
--
Stuck in loop when Firefox crashed
https://launchpad.net/bugs/59988
--
ubuntu-
I'll rather open a new bug, apport is indeed stuck, but it never
actually shows its own UI.
--
Stuck in loop when Firefox crashed
https://launchpad.net/bugs/59988
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: apport (Ubuntu)
Importance: Untriaged => High
Assignee: (unassigned) => Martin Pitt
--
Stuck in loop when Firefox crashed
https://launchpad.net/bugs/59988
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this and replicate. Start firefox, and then open a
terminal and run:
$ kill -SEGV `pidof firefox-bin`
** Changed in: apport (Ubuntu)
Status: Unconfirmed => Confirmed
--
Stuck in loop when Firefox crashed
https://launchpad.net/bugs/59988
--
ubuntu-bugs mailing list
ubuntu-
