GNOME Bugzilla – Bug 648995
crash in Home Folder: sending a directory to t...
Last modified: 2011-04-30 14:52:23 UTC
What were you doing when the application crashed? sending a directory to trash Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-31-generic #61-Ubuntu SMP Fri Apr 8 18:25:51 UTC 2011 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Human GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 657166336 vsize: 657166336 resident: 39186432 share: 11886592 rss: 39186432 rss_rlim: 18446744073709551615 CPU usage: start_time: 1303851234 rtime: 18019 utime: 15787 stime: 2232 cutime:32 cstime: 28 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0x7f44ff4fc700 (LWP 22805)] [New Thread 0x7f44f6ffd700 (LWP 2277)] [New Thread 0x7f45122aa700 (LWP 1697)] 0x00007f451d1b26dd in waitpid () from /lib/libpthread.so.0
+ Trace 226948
Thread 1 (Thread 0x7f451dfe0940 (LWP 1683))
Inferior 1 [process 1683] will be detached. Quit anyway? (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 ** 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 ** 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 --------------------- ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged warning: 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). warning: 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). ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1598): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged --------------------------------------------------
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 ***