Activity log for bug #140882

Date Who What changed Old value New value Message
2007-09-19 07:12:23 twager bug added bug
2007-09-19 07:12:23 twager bug added attachment 'CoreDump.gz' (CoreDump.gz)
2007-09-19 07:12:23 twager bug added attachment 'Dependencies.txt' (Dependencies.txt)
2007-09-19 07:12:23 twager bug added attachment 'Disassembly.txt' (Disassembly.txt)
2007-09-19 07:12:23 twager bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2007-09-19 07:12:23 twager bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2007-09-19 07:12:23 twager bug added attachment 'Registers.txt' (Registers.txt)
2007-09-19 07:12:23 twager bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2008-08-07 09:09:32 Apport retracing service bug added subscriber Crash bug triagers for universe packages
2008-08-12 20:29:23 Sebastien Bacher kmplayer: status New Incomplete
2008-08-12 20:29:23 Sebastien Bacher kmplayer: title Bug #140882 in kmplayer (Ubuntu): "kxineplayer crashed with SIGSEGV" Bug #140882 in xine-lib (Ubuntu): "kxineplayer crashed with SIGSEGV"
2008-08-12 20:29:23 Sebastien Bacher kmplayer: importance Undecided Medium
2008-08-12 20:29:23 Sebastien Bacher kmplayer: bugtargetname kmplayer (Ubuntu) xine-lib (Ubuntu)
2008-08-12 20:29:23 Sebastien Bacher kmplayer: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.
2008-08-12 20:29:23 Sebastien Bacher kmplayer: bugtargetdisplayname kmplayer (Ubuntu) xine-lib (Ubuntu)
2008-11-27 18:49:53 Pedro Villavicencio xine-lib: status Incomplete Invalid
2008-11-27 18:49:53 Pedro Villavicencio xine-lib: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.