apport-collect: do not ask for LP access level

Bug #410205 reported by David Nielsen
88
This bug affects 14 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

There is the scenerio where the user gets into trouble with apport-collect.

Typically a developer in the course of a bug report request that the user collect some data using apport-collect.

1. user types in requested command
2. Launchpad pops up and requests access
3. user being careful figures a program that collects data should be given the permission to read only non-private data.
4. going back to the terminal the user now discovers that he needed to give more rights to the bugger for it to work

Now in best quiz style we have 3 options to get to set the correct settings
5a. apport-collect --help
5b. run the requested apport-collect call hoping it will reset.
5c. go to your launchpad profile and see a handy list of applications which have been granted access and options to tweak previous settings.
5c. all of the above

the correct answer is.
rm .cache/apport/launchpad.credentials followed by 5b.

This is failing very ungratefully for no reason, I suspect something the above listed options should be evaluated. More granulated control of the sharing levels would be good as well.

Revision history for this message
Martin Pitt (pitti) wrote :

Just delete ~/.cache/apport/ to re-set the privileges and get the question again in the meantime.

summary: - credentials cannot requested resat if previously set to low
+ apport-collect: do not ask for privilege level
summary: - apport-collect: do not ask for privilege level
+ apport-collect: do not ask for LP access level
Changed in apport (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
dino99 (9d9) wrote :

hi Martin,
thx that's work

Revision history for this message
dino99 (9d9) wrote :

bad news,

one day later, using again apport-collect -p, Launchpad ask again for right. So the right allowed previously run only one time ?

oem@oem-desktop:~$ apport-collect -p gdm 433928
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
Bug title: gdm-binary[2671]: WARNING: Unable to find users: no seat-id found
Collecting apport information for source package gdm...
No additional information collected.
oem@oem-desktop:~$ sudo rm .cache/apport/launchpad.credentials
[sudo] password for oem:
oem@oem-desktop:~$ apport-collect -p gdm 433928
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
The authorization page:
   (https://edge.launchpad.net/+authorize-token?oauth_token=wtJVH3sQpSNf4dkmTv4F)
should be opening in your browser. After you have authorized
this program to access Launchpad on your behalf you should come
back here and press <Enter> to finish the authentication process.

Bug title: gdm-binary[2671]: WARNING: Unable to find users: no seat-id found
Collecting apport information for source package gdm...
No additional information collected.

Revision history for this message
Martin Pitt (pitti) wrote :

trunk r1652

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
Revision history for this message
dino99 (9d9) wrote :

still there with jaunty64:

oem@dubuntu:~$ apport-collect -p linux 541011
Logging into Launchpad...
Downloading bug...
Bug title: Memory corruption detected in low memory
Collecting apport information for source package linux...
Uploading additional information to Launchpad bug...
   short text data...
   attachment: Dependencies.txt...
Error connecting to Launchpad: HTTP Error 500: Internal Server Error
You have to allow "Change anything" privileges.

Changed in apport (Ubuntu):
status: Fix Released → New
Revision history for this message
dino99 (9d9) wrote : apport-collect data

Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: apport 1.0-0ubuntu5.4
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.utf8
Uname: Linux 2.6.28-18-generic x86_64
UserGroups: adm admin boinc cdrom dialout lpadmin plugdev sambashare

Revision history for this message
dino99 (9d9) wrote :

oem@dubuntu:~$ sudo rm .cache/apport/launchpad.credentials
[sudo] password for oem:
oem@dubuntu:~$ apport-collect -p apport 410205
Logging into Launchpad...
The authorization page (https://edge.launchpad.net/+authorize-token?oauth_token=btkfq1wWCqSzW2pzpmH8) should be opening in your browser. After you have authorized this program to access Launchpad on your behalf you should come back here and press <Enter> to finish the authentication process.

Downloading bug...
Bug title: apport-collect: do not ask for LP access level
Collecting apport information for source package apport...
Uploading additional information to Launchpad bug...
   short text data...
   attachment: Dependencies.txt...
Error connecting to Launchpad: HTTP Error 500: Internal Server Error
You have to allow "Change anything" privileges.

Revision history for this message
Philip Muškovac (yofel) wrote :

This bug has been fixed for lucid and above. This isn't such a grave issue that backporting the fix would be justified either even though it's annoying for sure. Please report any other bugs you may find!

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

Other bug subscribers

Related questions

Remote bug watches

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