Activity log for bug #94686

Date Who What changed Old value New value Message
2007-03-22 08:49:43 zuzuf bug added bug
2007-03-22 08:49:43 zuzuf bug added attachment 'CoreDump.gz' (CoreDump.gz)
2007-03-22 08:49:43 zuzuf bug added attachment 'Dependencies.txt' (Dependencies.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'Disassembly.txt' (Disassembly.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'Registers.txt' (Registers.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2007-03-22 08:49:43 zuzuf bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2007-03-22 10:20:29 Daniel Holbach kdelibs: assignee kubuntu-team
2007-03-22 10:20:29 Daniel Holbach kdelibs: statusexplanation Thanks for your bug report.
2007-03-22 10:24:18 Apport retracing service bug added attachment '<fdopen>' (Stacktrace.txt (retraced))
2007-03-22 10:24:19 Apport retracing service bug added attachment '<fdopen>' (ThreadStacktrace.txt (retraced))
2007-03-22 12:15:24 Daniel Holbach kdelibs: importance Undecided Medium
2007-03-22 12:15:24 Daniel Holbach kdelibs: statusexplanation Thanks for your bug report.
2007-03-23 10:11:06 Sebastien Bacher kdelibs: status Unconfirmed Needs Info
2007-03-23 10:11:06 Sebastien Bacher kdelibs: 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-04-28 05:29:38 Andrew Ash kdelibs: status Needs Info Rejected
2007-04-28 05:29:38 Andrew Ash kdelibs: assignee kubuntu-team
2007-04-28 05:29:38 Andrew Ash kdelibs: 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.