[Bug 1378134] Re: update-notifier crash detection checks for writable crash files

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 0.154.1ubuntu1

---------------
update-notifier (0.154.1ubuntu1) trusty-proposed; 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.
    (LP: #1378134)
 -- Brian Murray <brian at ubuntu.com>   Mon, 06 Oct 2014 16:42:19 -0700

** Changed in: update-notifier (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1378134

Title:
  update-notifier crash detection checks for writable crash files

Status in “update-notifier” package in Ubuntu:
  Fix Released
Status in “update-notifier” source package in Trusty:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1378134/+subscriptions