GNOME Bugzilla – Bug 634842
crash in File Browser: DVD aus Laufwerk, das an...
Last modified: 2010-11-14 19:40:44 UTC
Version: 2.32.0 What were you doing when the application crashed? DVD aus Laufwerk, das angezeigt wurde, entfernt Distribution: Ubuntu 10.10 (maverick) Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:17:33 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 219742208 vsize: 219742208 resident: 52920320 share: 31023104 rss: 52920320 rss_rlim: 18446744073709551615 CPU usage: start_time: 1289723176 rtime: 3293 utime: 2639 stime: 654 cutime:730 cstime: 38 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xac853b70 (LWP 5092)] [New Thread 0xb0cfeb70 (LWP 4567)] [New Thread 0xb73bfb70 (LWP 2014)] 0x0014d422 in __kernel_vsyscall ()
+ Trace 224666
Thread 1 (Thread 0xb7761860 (LWP 2010))
Inferior 1 [process 2010] 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 ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** GLib-GObject **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed ** Gtk **: IA__gtk_widget_set_child_visible: assertion `GTK_IS_WIDGET (widget)' failed ** Gtk **: IA__gtk_widget_size_allocate: assertion `GTK_IS_WIDGET (widget)' failed ----------- .xsession-errors --------------------- ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:1663): 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 627901 ***