Activity log for bug #197417

Date Who What changed Old value New value Message
2008-03-01 21:06:42 XANA bug added bug
2008-03-01 21:06:42 XANA bug added attachment 'CoreDump.gz' (CoreDump.gz)
2008-03-01 21:06:42 XANA bug added attachment 'Dependencies.txt' (Dependencies.txt)
2008-03-01 21:06:42 XANA bug added attachment 'Disassembly.txt' (Disassembly.txt)
2008-03-01 21:06:42 XANA bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2008-03-01 21:06:42 XANA bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2008-03-01 21:06:42 XANA bug added attachment 'Registers.txt' (Registers.txt)
2008-03-01 21:06:42 XANA bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2008-03-01 21:06:42 XANA bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2008-03-12 20:41:32 Apport retracing service bug added attachment 'Stacktrace.txt' (Stacktrace.txt (retraced))
2008-03-12 20:41:41 Apport retracing service bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt (retraced))
2008-03-12 20:41:43 Apport retracing service bug added attachment 'StacktraceSource.txt' (StacktraceSource.txt)
2008-03-12 20:41:45 Apport retracing service emifreq-applet: importance Undecided Medium
2008-03-12 20:41:48 Apport retracing service bug added subscriber Crash bug triagers for universe packages
2008-12-10 14:51:02 Charlie Kravetz emifreq-applet: status New Incomplete
2008-12-10 14:51:02 Charlie Kravetz emifreq-applet: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Did this happen more than once? Thanks in advance.
2009-01-06 18:10:49 Charlie Kravetz emifreq-applet: status Incomplete Invalid
2009-01-06 18:10:49 Charlie Kravetz emifreq-applet: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Did this happen more than once? Thanks in advance. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!