Closing this bug report as no further information has been provided.
Please feel free to reopen this bug if you can provide the information
asked for. Thanks!.
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Invalid
--
nautilus crashed with SIGSEGV in open_read_async_thread()
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Attachment
don't attach crash files to bug but use apport so they can be
automatically retraced in a proper way
--
nautilus crashed with SIGSEGV in open_read_async_thread()
https://bugs.launchpad.net/bugs/239870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Reopening, because it happened again.
** Changed in: nautilus (Ubuntu)
Status: Invalid = Confirmed
--
nautilus crashed with SIGSEGV in open_read_async_thread()
https://bugs.launchpad.net/bugs/239870
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
The new crash file is attached. I'm not sure it has all the information
needed. Suggestions for extra debug libs to install? Just installed
libgtk2.0-0-dbg, after the crash.
I can try to keep gdb attached to it, if needed. It's been about a
month since the last one.
** Attachment added:
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
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.
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/15270662/CoreDump.gz
**
