GNOME Bugzilla – Bug 511186
crash in Open Folder: Did a search on Nautilus...
Last modified: 2008-01-23 10:14:31 UTC
Version: 2.18.3 What were you doing when the application crashed? Did a search on Nautilus for "nisi prius"; a court document Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks_Cairo-Breathe Icon Theme: Fedora Memory status: size: 107098112 vsize: 107098112 resident: 43536384 share: 25083904 rss: 43536384 rss_rlim: 4294967295 CPU usage: start_time: 1200639615 rtime: 709 utime: 512 stime: 197 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208576288 (LWP 3358)] [New Thread -1221416048 (LWP 20622)] 0x00110402 in __kernel_vsyscall ()
+ Trace 186286
Thread 2 (Thread -1221416048 (LWP 20622))
----------- .xsession-errors (16 sec old) --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". (gnome-help:20612): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (nautilus:3358): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x180e1)! Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
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 454799 ***