update-notifier crash detection checks for writable crash files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Brian Murray |
Bug Description
The update-notifier user session job checks to see if a crash file is writable, however apport doesn't make the crash file writable until after it has finished its initial data collection. Subsequently, its possible for the upstart job to notice the crash file and it not be writable and then apport is never launched for the crash file.
[Test Case]
1) sleep 100 &
2) pkill -11 sleep
3) ls -lh /var/crash/
You'll notice there is a crash in /var/crash but that you've received no apport dialog for the crash file. With the version of update-notifier from trusty-proposed you will receive an apport notification regarding the crash file.
[Impact]
Crashes from 14.04 are likely being underreported to the Ubuntu Error Tracker.
[Regression Potential]
This is a minor change to the update-notifier crash detection job and is unlikely to cause problems.
Changed in update-notifier (Ubuntu): | |
status: | New → Fix Released |
Changed in update-notifier (Ubuntu Trusty): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Brian Murray (brian-murray) |
I've fixed this in Utopic already.
update-notifier (3.157) utopic; urgency=medium
* debian/ update- notifier- crash.conf: avoid race condition where the crash
report may not yet be writable when the inotify create event happens.
-- Brian Murray <email address hidden> Fri, 03 Oct 2014 17:00:11 -0700