They are not useless. The "retraced" means, that they tried to load the
symbols from the dbgsym packages. As you still see unknown symbols in
the retraced stacktraces, something went wrong, probably because of too
old packages without matching symbol tables.
I'll close this bug as the reporter is
I'm sorry but this would mean downgrading to feisty and upgrading to
hardy back again and still there's no guarantee that this would trigger
the bug once more. If the apport reports without the debugging symbols
are useless maybe they shouldn't be reported at all?
--
quodlibet.py crashed with SIG
Thank you for taking the time to report this bug and helping to make
Ubuntu better. If you are able to reproduce this issue, please try to
obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attachment) to the bug report. Thi
StacktraceTop:do_mktuple (p_format=0x1, p_va=0x816a1a0, endchar=135166005,
_Py_BuildValue_SizeT (
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/15200696/Stacktrace.txt
** Tags added: need-i386-retrace
--
quodlibet.py crashed with SIGSEGV in PyTraceBack_Print()
https://bugs.launchpad.net/bugs/221640
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/13877552/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/13877553/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/13877554/Disassembly.txt
** Attachm
