unable to update an bug with an existing .crash file

Bug #1208508 reported by James Hunt on 2013-08-05
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)

Bug Description

I may be misunderstanding the man pages, but I was assuming that if I ran the following...

    $ sudo apport-cli --save /tmp/linux.crash linux

... then copied linux.crash to a local system, I would be able to append the meta-data in linux.crash to an *existing* bug report like this:

    $ apport-cli --update-report $bug --crash-file linux.report

However, that doesn't work:

    Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash file]

    apport-cli: error: -u/--update-bug option cannot be used together with options for a new report

This looks like a bug since I've specified '--update-report', hence this is not a new report.

Martin Pitt (pitti) wrote :

That's right, this cannot currently be used like that. apport-collect is meant to be run on the affected system.

It would be nice to make it work on a system which isn't connected to the internet, with --save indeed.

Changed in apport:
importance: Undecided → Wishlist
status: New → Triaged
tags: added: rls-bb-incoming
Manoj Iyer (manjo) wrote :

This would be a very useful feature for cases where bugs are mirrored from a bug tracking tool like bugzilla to launchpad, usually servers are behind firewalls, so .apport could be collected offline and later (the mirrored lp bug could be) updated with .apport information.

Changed in apport (Ubuntu):
importance: Undecided → Wishlist
Steve Langasek (vorlon) on 2017-11-09
tags: added: rls-bb-notfixing
removed: rls-bb-incoming
Changed in apport (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers