← Back to team overview

desktop-packages team mailing list archive

[Bug 1537211] Re: clean up /var/log/udev.log


This bug was fixed in the package apport - 2.19.4-0ubuntu1

apport (2.19.4-0ubuntu1) xenial; urgency=medium

  * New upstream bug fix release:
    - Fix fileutils.test_find_package_desktopfile test for symlinks and other
      unowned files in /usr/share/applications/.
    - Fix ui.test_run_crash_anonymity test case to not fail if the base64
      encoded core dump happens to contain the user name, as that's just by
      chance.  - Fix test_hooks.py for unreleased gcc versions which have a
      different --version format.
    - hookutils.py, attach_hardware(): Stop attaching /var/log/udev. This was
      an upstart-ism, mostly redundant with the udev db and is not being
      written under systemd. (LP: #1537211)
  * etc/apport/crashdb.conf: Enable crash reports on Launchpad for xenial.

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Tue, 26 Jan 2016 15:37:44

** Changed in: apport (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.

  clean up /var/log/udev.log

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in apport source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in libmtp package in Debian:

Bug description:
  The udev package contains an upstart job, /etc/init/udevmonitor.conf,
  whose purpose is to record boot-time information about devices in a
  log file for future debugging.  There is no equivalent systemd unit
  for this job, so with the move to systemd, we now lose this useful
  debugging information.  I'm not aware of any other way under systemd
  to get a replay of the boot-time kernel events.  If there is one,
  that's fine, but otherwise there should be a systemd unit equivalent
  here that can give us this log.

To manage notifications about this bug go to: