retracing failed with status: 1 Traceback

Bug #1191366 reported by Cody Garver on 2013-06-15
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Apport
Undecided
Unassigned

Bug Description

This happens on everything I try to retrace. Tested on raring and precise.

06/15/13 17:28:50: retracing #1189991 failed with status: 1
Traceback (most recent call last):
  File "bin/crash-digger", line 209, in <module>
    opts.dupcheck_mode, opts.publish_db, opts.crash_db).run()
  File "bin/crash-digger", line 136, in run
    self.retrace_next()
  File "bin/crash-digger", line 101, in retrace_next
    raise SystemError('retracing #%i failed' % id)
SystemError: retracing #1189991 failed

Martin Pitt (pitti) wrote :

Please show me the complete command line that you used for this, as well as your configuration directory (for elementary). This output doesn't have any actual error message, we need the real error from apport-retrace to see what's going on. Can you please run apport-retrace on that bug directly and copy&paste the output? (Something like

  apport-retrace -sv --auth /your/auth/file --sandbox /your/config -C /your/cache 1189991
)

Or provide me with above configs so that I can run this myself?

Changed in apport:
status: New → Incomplete
Cody Garver (codygarver) wrote :

cd apport; for project in $(cat /home/$USER/apport-retrace-sandbox/project-list); do PYTHONPATH=. bin/crash-digger --crash-db="$project" --config-dir=/home/$USER/apport-retrace-sandbox/ --cache=/home/$USER/.crash-digger-cache/ --auth=~/.cache/apport/launchpad.credentials; done

lp:~elementary-os/elementaryos/apport-retrace-sandbox

I can confirm. This bug has been haunting us for a while now.

I believe the report contains all the required info now. I can also provide you access to our bot account shall you need it, or subscribe you to several crash reports to make it easier for you to reproduce the problem.

Changed in apport:
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers