Activity log for bug #242375

Date Who What changed Old value New value Message
2008-06-23 14:54:46 George Dumitrescu bug added bug
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'CoreDump.gz' (CoreDump.gz)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'Dependencies.txt' (Dependencies.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'Disassembly.txt' (Disassembly.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'ExtensionSummary.txt' (ExtensionSummary.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'ProcMaps.txt' (ProcMaps.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'ProcStatus.txt' (ProcStatus.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'Registers.txt' (Registers.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'Stacktrace.txt' (Stacktrace.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'pluginreg.dat.txt' (pluginreg.dat.txt)
2008-06-23 14:54:46 George Dumitrescu bug added attachment 'profiles.ini.txt' (profiles.ini.txt)
2008-06-23 15:07:08 Apport retracing service bug added attachment 'Stacktrace.txt' (Stacktrace.txt (retraced))
2008-06-23 15:07:12 Apport retracing service bug added attachment 'ThreadStacktrace.txt' (ThreadStacktrace.txt (retraced))
2008-06-23 15:07:17 Apport retracing service firefox-3.0: importance Undecided Medium
2008-06-23 15:20:29 Richard Seguin firefox-3.0: status New Incomplete
2008-06-23 17:45:05 George Dumitrescu bug added attachment '_usr_lib_firefox-3.0_firefox.1000.crash' (_usr_lib_firefox-3.0_firefox.1000.crash)
2008-06-25 11:09:48 Richard Seguin firefox-3.0: status Incomplete Confirmed
2008-06-25 11:10:06 Richard Seguin title firefox crashed with SIGSEGV in snd_pcm_state() firefox 3 crashed with SIGSEGV in snd_pcm_state()
2008-12-24 15:00:33 Richard Seguin firefox-3.0: status Confirmed Triaged
2008-12-24 15:00:33 Richard Seguin firefox-3.0: statusexplanation It looks like there is enough information here for a developer to look at the issue... There probably will be more questions though so I am asking that you please stay subscribed to the bug report...