Nautilus crashes on "open and close self" operation on file

[Phil Housley]

Trying to open a file and close the current nautilus window at once
(meaning either double-middle-clicking, or shift-double-clicking on a regular file,) causes a crash for me. There's no bug-buddy or anything, nautilus just vanishes and immediately restarts.

NB. This only happens in spatial mode of course, as there is no such function in browser mode.

[Alberto Fernández (unicyn)]

Yes, I have also the same problem. I get this backtrace:
Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 2012284608 (LWP 5498)]
[New Thread 2009316272 (LWP 5512)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x4577448b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0x4b3f7672 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0x0810d1c5 in nautilus_marshal_VOID__STRING_ENUM_INT_INT ()
#5 0x0809b26e in POA_Nautilus_MetafileFactory__fini ()
#6 0x080a877f in fm_directory_view_pop_up_location_context_menu ()
#7 0x080f02f1 in nautilus_file_get_string_attribute ()
#8 0x080d3527 in nautilus_clipboard_monitor...

[Phil Housley (undeconstructed)]

Fixed upstream in 2.14.0 it seems.

[Sebastien Bacher (seb128)]

Thanks for your bug. That's probably the same issue than http://bugzilla.gnome.org/show_bug.cgi?id=330491 which is fixed now with dapper. Feel free to reopen if you get the issue again