GNOME Bugzilla – Bug 661246
crash in Computer: I copied some photos fro...
Last modified: 2011-10-08 16:51:12 UTC
Version: 2.32.0 What were you doing when the application crashed? I copied some photos from my camera to an external harddrive. Then I deleted the photos from the camera. I believe the crash was induced by the deletion? Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Ambiance Icon Theme: ubuntu-mono-dark GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 246849536 vsize: 246849536 resident: 66867200 share: 14917632 rss: 66867200 rss_rlim: 18446744073709551615 CPU usage: start_time: 1316629594 rtime: 38409 utime: 32568 stime: 5841 cutime:394 cstime: 209 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb2850b70 (LWP 455)] [New Thread 0xb7586b70 (LWP 2264)] 0x00298422 in __kernel_vsyscall ()
+ Trace 228716
Thread 1 (Thread 0xb7788860 (LWP 2256))
Inferior 1 [process 2256] 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 (40 sec old) --------------------- ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2175): 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). --------------------------------------------------
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 ***