GNOME Bugzilla – Bug 468180
crash in Open Folder: Searching mu homedir for...
Last modified: 2007-08-21 20:29:10 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching mu homedir for '*.eri' Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.3-vanilla #1 SMP Thu Aug 16 15:00:42 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 495591424 vsize: 495591424 resident: 45854720 share: 26669056 rss: 45854720 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187528005 rtime: 430 utime: 343 stime: 87 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47644849896960 (LWP 3379)] [New Thread 1166059856 (LWP 3671)] (no debugging symbols found) 0x00000036ddec82e6 in poll () from /lib64/libc.so.6
+ Trace 156324
Thread 2 (Thread 1166059856 (LWP 3671))
----------- .xsession-errors --------------------- most likely the X server was shut down or you killed/destroyed the window manager. kbuildsycoca running... DCOP Cleaning up dead connections. --- Hash table keys for warning below: --> file:///home/loes (nautilus:3629): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Debug: Creating a ResponseMessageException from an ErrorResponse *** Using mono runtime at mono *** *** Using mono runtime at mono *** Beagle Daemon exited with errors. See ~/.beagle/Log/current-Beagle for more details. (nautilus:3379): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***