notifier detects crashes before core is finished being written
Bug #224071 reported by
Kees Cook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
When a very large program crashes (say... firefox), the crash notifier will pop up before the crash file has been written out all the way, causing a number of issues:
- repeated "new crash" notification popups as the crash file grows
- apport-gtk complains the crash is corrupted (since it is still growing)
I would suggest an rsync-style "temp" filename to be used until apport is finished building the crash file, which can then be moved into place.
Changed in apport: | |
status: | Invalid → Incomplete |
To post a comment you must log in.
That's indeed weird, since the .crash file is created with permissions 000, and only chmod'ed to 600 after it is completely written. apport-checkreports ignores files which are inaccessible, so this shouldn't happen (and doesn't for me). Can you please trigger a firefox or evo crash (or anything else which takes a while to coredump) and check the permissions of the /var/crash/ file while it is being written? Seems that chmodding doesn't work properly for you?