If I get this crash again I will re-open the bug and add a new coredump.
On a side note, it might be useful to be a little bit more descriptive
in your templates - IE "We where unable to retrace the uploaded files so
are unable to get useful information." or something. It will make the
comments le
the retracing didn't work for whatever reason, you can try sending a new
bug using apport, it might be retraced correctly
--
rhythmbox crashed with SIGSEGV
https://bugs.launchpad.net/bugs/191446
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
If I could reproducable cause the error then I might be able to get you
a better stack trace, I can not however. It just happens occasionally -
once every now and then.
Secondly, the page you linked to does not give information on how to
obtain more information then the apport report already conta
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 t
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 y
