apport-collect should show you what is being sent

Bug #371827 reported by Brian Murray
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

Binary package hint: apport

When you report a bug with ubuntu-bug you are presented with a dialog indicating what information is being submitted to Launchpad. However, when runs apport-collect there is no indication as to what is being uploaded to Launchpad. To allay any privacy concerns I think apport-collect should behave the same way and present one with a dialog indicating what is going to be uploaded before actually performing the operation.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 371827] [NEW] apport-collect should show you what is being sent

 status triaged
 assignee pitti
 importance medium

Martin Pitt (pitti)
Changed in apport (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Undecided → Medium
status: New → Triaged
Martin Pitt (pitti)
Changed in apport (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
apport (1.10-0ubuntu1) lucid; urgency=low

  * New upstream release:
    - Add a mode for updating an existing problem report to ui.py
      (-u/--update). This is similar to the Ubuntu specific "apport-collect"
      tool, but implemented the right way now: In particular, this has access
      to the UI and thus can use interactive hooks (LP: #385811) and show you
      what is being sent for confirmation/cancelling (LP: #371827)

    - apport-bug: If invoked as "apport-collect" or "apport-update-bug" (i. e.
      through a symlink), run apport in update mode (-u <number>). This
      provides a convenient no-options command line program. Please note that
      setup.py does not currently install such a symlink. Update the
      apport-bug manpage accordingly.

    - launchpad.py: Use new login_with() to clean up code, and specify allowed
      access levels (WRITE_PRIVATE is the only sensible one anyway).
      (LP: #410205)

    - New hookutils functions:
      + xsession_errors (match lines from ~/.xsession-errors)
      + shared_libraries (determine which libraries a binary links with)
      + links_with_shared_library (test if a binary links with a particular
        library)

    - New CrashDatabase API: get_affected_packages(), can_update(), is_reporter()

    - Rename CrashDatabase.update() to update_traces().

    - Add CrashDatabase.update() for adding all new fields of a report. This is
      primarily useful for collecting local standard and package hook data for an
      already existing bug report which was not filed through Apport. This checks
      can_update()/is_reporter() if the user is eligible for updating that
      particular bug. (LP: #485880)

    - Ignore SIGXCPU and SIGXFSZ; thanks to Kees Cook. (LP: #498074)

    - launchpad.py: Do not mark non-Ubuntu bugs as needs-retrace, since there is
      no retracer right now. (LP: #489794)

    - packaging-apt-dpkg.py, install_retracing_packages(): Do not crash on
      malformed Dependencies.txt lines. (LP: #441709)

    - use-local: Fix for new source tree location of "apport" binary.

  * Drop debian/local/apport-collect{,.1} and install symlinks for apport-bug
    instead.
  * data/general-hooks/ubuntu.py: Do not report "corrupted filesystem tarfile"
    package errors. (LP: #320743)
  * data/general-hooks/ubuntu.py: Report "package ... is already installed and
    configured" errors against dpkg, not the package that failed. (LP: #467688)
 -- Martin Pitt <email address hidden> Sat, 19 Dec 2009 16:48:48 +0100

Changed in apport (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.