Activity log for bug #129453

Date Who What changed Old value New value Message
2007-07-31 16:01:44 exactt bug added bug
2007-07-31 16:01:44 exactt bug added attachment 'CoreDump.gz' (CoreDump.gz)
2007-07-31 16:01:44 exactt bug added attachment 'Dependencies.txt' (Dependencies.txt)
2007-07-31 16:01:44 exactt bug added attachment 'Disassembly.txt' (Disassembly.txt)
2007-07-31 16:01:44 exactt bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2007-07-31 16:01:44 exactt bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2007-07-31 16:01:44 exactt bug added attachment 'Registers.txt' (Registers.txt)
2007-07-31 16:01:44 exactt bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2007-08-01 09:27:57 Apport retracing service bug added attachment 'Stacktrace.txt' (Stacktrace.txt (retraced))
2007-08-01 09:28:03 Apport retracing service bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt (retraced))
2007-08-01 09:28:05 Apport retracing service bug added subscriber Crash bug triagers for universe packages
2007-08-01 09:28:14 Apport retracing service bug added subscriber Crash bug triagers for universe packages
2007-08-01 19:49:51 Pedro Villavicencio file-roller: status New Incomplete
2007-08-01 19:49:51 Pedro Villavicencio file-roller: importance Undecided Medium
2007-08-01 19:49:51 Pedro Villavicencio file-roller: statusexplanation Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.
2007-08-01 19:49:51 Pedro Villavicencio file-roller: assignee desktop-bugs
2007-08-22 16:42:02 Pedro Villavicencio file-roller: status Incomplete Invalid
2007-08-22 16:42:02 Pedro Villavicencio file-roller: statusexplanation Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. 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.