possible for apport to report all packages with an origin of unknown

Bug #1217517 reported by Brian Murray
This bug affects 6 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)

Bug Description

[Test Case]
1) Install saucy without Internet access
2) Reboot
3) Open a terminal and run 'xeyes &'
4) Run 'pkill -11 xeyes'
5) View details of the crash and notice that every package in Dependencies has [origin: unknown]

This problem instance (https://errors.ubuntu.com/oops/ac5a56d8-0d19-11e3-9952-2c768aafd08c) on the error tracker shows the following:

  Package: apport-gtk 2.9.2-0ubuntu8 [origin: unknown]

Looking at the Dependencies, every single one is shown as unknown. This is because the system was just installed (look at the InstallationDate) and apt-get update has not been ran. Because there is any package with an 'origin: unknown' marker in it the bug report and error is then tagged 'third-party-packages' which is erroneous.

description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Looking at the origins for a package on a freshly installed saucy system we can see:


[<Origin component:'' archive:'now' origin:'' label:'' site:'' isTrusted:False>]

description: updated
tags: added: saucy
Changed in apport (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
Changed in apport (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

Yeah, this problem is ancient, and has been discussed a lot of times. We simply don't have any apt packaging lists after an offline install, so it's impossible to determine origins, source package names, etc. We just can't make apport work properly without having run "apt-get update" at least once, I'm afraid.

Changed in apport (Ubuntu):
assignee: Martin Pitt (pitti) → nobody
status: Confirmed → Won't Fix
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Revision history for this message
Martin Pitt (pitti) wrote :

To be more clear, we could work around this particular check by adding a heuristics whether coreutils' origin is known, etc. But we actually do want people to install updates before reporting problems to ensure that they are running with the current version (that's the "old version" check). I'm really not keen about dropping this.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers