*** This bug is a duplicate of bug 413152 ***
https://bugs.launchpad.net/bugs/413152
thanks for the bug report. this bug is duplicate of bug 413152 marked
duplicate.
** This bug has been marked a duplicate of bug 413152
nautilus crashed with SIGSEGV in g_type_class_ref()
* You can
** Changed in: nautilus
Status: Incomplete = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661254
Title:
nautilus crashed with SIGSEGV in thread_memory_from_self() while
opening
** Changed in: nautilus
Status: Unknown = Incomplete
** Changed in: nautilus
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661254
Title:
nautilus crashed
This bug has been with the developers at
https://bugzilla.gnome.org/show_bug.cgi?id=638304. You can track it and
make comments there. Thank you.
** Bug watch added: GNOME Bug Tracker #638304
https://bugzilla.gnome.org/show_bug.cgi?id=638304
** Changed in: nautilus (Ubuntu)
Status:
Here is the valgrind log as per your instructions.
** Attachment added: valgrind.log
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/661254/+attachment/1701303/+files/valgrind.log
--
nautilus crashed with SIGSEGV in thread_memory_from_self() while opening
/usr/bin
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.
** Changed in:
