← Back to team overview

desktop-packages team mailing list archive

[Bug 1487174] Re: apport-retrace's build sandbox routine carries on if it can't find the package for an ExecutablePath


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

apport (2.18.1-0ubuntu1) wily; urgency=medium

  * New upstream bug fix release. Changes since our previous snapshot:
    - packaging.py: Only consider first word in /etc/os-release's NAME value.
      This works around Debian's inconsistent value. (LP: #1408245)
    - Unify and simplify Package: field generation in kernel_crashdump,
      kernel_oops, and package_hook by using the new Report.add_package()
      method.  (LP: #1485787)
    - sandboxutils.py, make_sandbox(): Make "Cannot find package which ships
      Executable/InterpreterPath" fatal, to save some unnecessary package
      unpack cycles. (LP: #1487174)
  * etc/apport/crashdb.conf: Enable crash reports on Launchpad for wily.
    Really late, sorry about that!

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Thu, 10 Sep 2015 11:48:46

** Changed in: apport (Ubuntu)
       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.

  apport-retrace's build sandbox routine carries on if it can't find the
  package for an ExecutablePath

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  In the event that a package which provides an ExecutablePath or
  InterpreterPath can not be found apport will carry on building the
  sandbox but then exits a short while later (the last line in the
  pasted code). I think it'd be better if apport just quit earlier.

  Here's the code in question from sandboxutils.py:

      # package hooks might reassign Package:, check that we have the originally
      # crashing binary
      for path in ('InterpreterPath', 'ExecutablePath'):
          if path in report:
              pkg = apport.packaging.get_file_package(report[path], True, pkgmap_cache_dir,
              if pkg:
                  apport.log('Installing extra package %s to get %s' % (pkg, path), log_timestamps)
                  pkgs.append((pkg, pkg_versions.get(pkg)))
                  apport.warning('Cannot find package which ships %s', path)

      # unpack packages for executable using cache and sandbox
      if pkgs:
              outdated_msg += apport.packaging.install_packages(
                  sandbox_dir, config_dir, report['DistroRelease'], pkgs,
                  verbose, cache_dir, permanent_rootdir,
                  architecture=report.get('Architecture'), origins=origins)
          except SystemError as e:

      # sanity check: for a packaged binary we require having the executable in
      # the sandbox; TODO: for an unpackage binary we don't currently copy its
      # potential local library dependencies (like those in build trees) into the
      # sandbox, and we call gdb/valgrind on the binary outside the sandbox.
      if 'Package' in report:
          for path in ('InterpreterPath', 'ExecutablePath'):
              if path in report and not os.path.exists(sandbox_dir + report[path]):
                  apport.fatal('%s %s does not exist (report specified package %s)',
                               path, sandbox_dir + report[path], report['Package'])

  Instead of warning with ('Cannot find package which ships %s', path) I
  think that should be a fatal error. It'd probably be optimal to even
  move the check for the crashing binary to the earliest place possible
  in make_sandbox.

To manage notifications about this bug go to: