GNOME Bugzilla – Bug 497047
crash in Home Folder: starting a search with n...
Last modified: 2007-11-15 15:05:01 UTC
What were you doing when the application crashed? starting a search with nautilus Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.23.1 #1 Thu Nov 15 02:28:54 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: UbuntuStudio Icon Theme: UbuntuStudio Memory status: size: 89022464 vsize: 89022464 resident: 30044160 share: 16658432 rss: 30044160 rss_rlim: 4294967295 CPU usage: start_time: 1195129235 rtime: 1964 utime: 1824 stime: 140 cutime:13 cstime: 2 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6d618c0 (LWP 4365)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 177872
Thread 1 (Thread 0xb6d618c0 (LWP 4365))
----------- .xsession-errors --------------------- ** (nautilus:4365): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:4365): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:4365): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:4365): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:4365): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... warning: .dynamic section for "/usr/lib/libgnomecanvas-2.so.0" is not at the expected address (wrong library or version 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 440988 ***