*** This bug is a duplicate of bug 1677067 ***
https://bugs.launchpad.net/bugs/1677067
** This bug has been marked a duplicate of bug 1677067
nautilus crashed with SIGSEGV in nautilus_file_clear_info()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1675863
Title:
Nautilus crash after renaming an ODS file whilst in
I ran into this bug as well, see the attached stack trace.
The cause of this bug seems to be the fact that the parent_slot of the
file is empty, so the null pointer at g_class is dereferenced in the
NAUTILUS_FILE_GET_CLASS macro:
(gdb) print *file
$1 = {parent_slot = {g_type_instance = {g_class =
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
When this happens, the rename actually succeeded, so I usually just
relaunch nautilus and open the file. Having logged this, I was doing
some more replication checks, straight after the crash, it was not
possible to duplicate, but I really get this a lot.
If there are more diagnosis steps I can t
