GNOME Bugzilla – Bug 506973
crash in Open Folder: unmounting an external h...
Last modified: 2008-01-03 23:34:47 UTC
Version: 2.18.3 What were you doing when the application crashed? unmounting an external hard drive with a window open to a folder on the drive Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Bluecurve Memory status: size: 148865024 vsize: 148865024 resident: 38297600 share: 28545024 rss: 38297600 rss_rlim: 4294967295 CPU usage: start_time: 1198222776 rtime: 5803 utime: 2345 stime: 3458 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209059616 (LWP 2710)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183875
Thread 1 (Thread -1209059616 (LWP 2710))
----------- .xsession-errors (21 sec old) --------------------- ** (nautilus:2710): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed (nautilus:2710): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:2710): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:2710): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (nautilus:2710): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 warning: .dynamic section for "/usr/lib/libexif.so.12" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 355018 ***