Activity log for bug #206151

Date Who What changed Old value New value Message
2008-03-24 19:38:03 Duncan Lithgow bug added bug
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'CoreDump.gz' (CoreDump.gz)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'Disassembly.txt' (Disassembly.txt)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'Registers.txt' (Registers.txt)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2008-03-24 19:38:03 Duncan Lithgow bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2008-03-26 01:07:56 Apport retracing service bug added subscriber Crash bug triagers for universe packages
2008-03-26 01:08:00 Apport retracing service bug added attachment 'Stacktrace.txt' (Stacktrace.txt (retraced))
2008-03-26 01:08:05 Apport retracing service bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt (retraced))
2008-03-26 01:08:06 Apport retracing service python2.5: importance Undecided Medium
2008-09-12 12:54:34 Matthias Klose python2.5: bugtargetdisplayname python2.5 (Ubuntu) gtk+2.0 (Ubuntu)
2008-09-12 12:54:34 Matthias Klose python2.5: bugtargetname python2.5 (Ubuntu) gtk+2.0 (Ubuntu)
2008-09-12 12:54:34 Matthias Klose python2.5: title Bug #206151 in python2.5 (Ubuntu): "python2.5 crashed with SIGSEGV" Bug #206151 in gtk+2.0 (Ubuntu): "python2.5 crashed with SIGSEGV"
2008-09-12 13:04:30 Sebastien Bacher gtk+2.0: status New Incomplete
2008-09-12 13:04:30 Sebastien Bacher gtk+2.0: assignee desktop-bugs
2008-09-12 13:04:30 Sebastien Bacher gtk+2.0: statusexplanation thank you for your bug report, do you still have the issue using the current versions?
2008-10-08 15:14:37 Sebastien Bacher gtk+2.0: status Incomplete Fix Released
2008-10-08 15:14:37 Sebastien Bacher gtk+2.0: statusexplanation thank you for your bug report, do you still have the issue using the current versions? closing since there is no recent mention of such issue, you can reopen if you get the issue again though