Activity log for bug #85160

Date Who What changed Old value New value Message
2007-02-14 18:00:16 sbassett bug added bug
2007-02-14 18:00:16 sbassett bug added attachment 'CoreDump.gz' (CoreDump.gz)
2007-02-14 18:00:16 sbassett bug added attachment 'Dependencies.txt' (Dependencies.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'Disassembly.txt' (Disassembly.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'Registers.txt' (Registers.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2007-02-14 18:00:16 sbassett bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2007-02-14 18:16:54 Sebastien Bacher synaptic: status Unconfirmed Needs Info
2007-02-14 18:16:54 Sebastien Bacher synaptic: importance Undecided Medium
2007-02-14 18:16:54 Sebastien Bacher synaptic: statusexplanation Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)
2007-02-15 14:58:46 sbassett bug added attachment 'valgrind-logs-synaptic.tar.gz' (synaptic valgrind logs)
2007-04-14 12:58:08 Apport retracing service bug added attachment '<fdopen>' (Stacktrace.txt (retraced))
2007-04-14 12:58:15 Apport retracing service bug added attachment '<fdopen>' (ThreadStacktrace.txt (retraced))
2007-05-24 12:16:40 Sebastien Bacher synaptic: status Needs Info Rejected
2007-05-24 12:16:40 Sebastien Bacher synaptic: statusexplanation Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that) We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.