Activity log for bug #102643

Date Who What changed Old value New value Message
2007-04-03 22:53:15 Philipp bug added bug
2007-04-03 22:53:15 Philipp bug added attachment 'CoreDump.gz' (CoreDump.gz)
2007-04-03 22:53:15 Philipp bug added attachment 'Dependencies.txt' (Dependencies.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'Disassembly.txt' (Disassembly.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'Registers.txt' (Registers.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2007-04-03 22:53:15 Philipp bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2007-04-04 05:31:49 Apport retracing service title [apport] epiphany crashed with SIGSEGV in __kernel_vsyscall()" [apport] epiphany crashed with SIGSEGV in __kernel_vsyscall()
2007-04-04 05:32:46 Apport retracing service bug added attachment '<fdopen>' (Stacktrace.txt (retraced))
2007-04-04 05:32:48 Apport retracing service bug added attachment '<fdopen>' (ThreadStacktrace.txt (retraced))
2007-04-04 05:36:41 Brian Murray epiphany-browser: importance Undecided Medium
2007-04-04 05:36:41 Brian Murray epiphany-browser: statusexplanation
2007-04-04 08:12:15 Sebastien Bacher epiphany-browser: status Unconfirmed Needs Info
2007-04-04 08:12:15 Sebastien Bacher epiphany-browser: assignee desktop-bugs
2007-04-04 08:12:15 Sebastien Bacher epiphany-browser: 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-04-25 12:07:11 Sebastien Bacher epiphany-browser: status Needs Info Rejected
2007-04-25 12:07:11 Sebastien Bacher epiphany-browser: 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.