GNOME Bugzilla – Bug 641883
crash in Home Folder: just moving a document t...
Last modified: 2011-02-09 00:57:40 UTC
What were you doing when the application crashed? just moving a document to the basket bin... ¿could it be that it was contained in a Dropbox 'linked to' folder? Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.36-mfat #1 SMP Wed Dec 15 12:06:33 IRST 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 219258880 vsize: 219258880 resident: 45359104 share: 27852800 rss: 45359104 rss_rlim: 18446744073709551615 CPU usage: start_time: 1297185772 rtime: 2880 utime: 2322 stime: 558 cutime:371 cstime: 58 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [Nuevo Thread 0xae01bb70 (LWP 2899)] [Nuevo Thread 0xad81ab70 (LWP 2172)] [Nuevo Thread 0xb1de8b70 (LWP 1992)] [Nuevo Thread 0xb6189b70 (LWP 1822)] 0xb77ed424 in __kernel_vsyscall ()
+ Trace 225903
Inferior 1 [process 1810] will be detached. ¿Salir de cualquier modo? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** nautilus **: nautilus_information_panel_set_uri: assertion `new_uri != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** GConf **: gconf_value_free: assertion `value != NULL' failed ** nautilus **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed ----------- .xsession-errors (6 sec old) --------------------- ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1182): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged aviso: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). aviso: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). --------------------------------------------------
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 bug 602500 ***