GNOME Bugzilla – Bug 497655
crash in Home Folder: I was searching for a fi...
Last modified: 2007-11-20 19:48:27 UTC
What were you doing when the application crashed? I was searching for a file with Ctrl+F in the File Manager 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: Enforcing Accessibility: Disabled GTK+ Theme: YattaBlues Icon Theme: Echo Memory status: size: 133042176 vsize: 133042176 resident: 50495488 share: 36630528 rss: 50495488 rss_rlim: 4294967295 CPU usage: start_time: 1195306998 rtime: 1330 utime: 1167 stime: 163 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 -1208989984 (LWP 2641)] [New Thread -1232655472 (LWP 3452)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178336
Thread 2 (Thread -1232655472 (LWP 3452))
----------- .xsession-errors (14 sec old) --------------------- (Banshee:3044): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed GStreamer resource error: NotFound Could not fetch recommendations: Text node cannot appear in this state. Line 903, position 18. (Banshee:3044): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed GStreamer resource error: NotFound Could not fetch recommendations: Text node cannot appear in this state. Line 903, position 18. (Banshee:3044): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed GStreamer resource error: NotFound JACK tmpdir identified as [/dev/shm] (nautilus:2641): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x129646)! --------------------------------------------------
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 ***