GNOME Bugzilla – Bug 505407
crash in Open Folder: Searching for a file wit...
Last modified: 2007-12-24 14:22:38 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching for a file with the file browser 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: Clearlooks Icon Theme: Fedora Memory status: size: 93540352 vsize: 93540352 resident: 35647488 share: 22102016 rss: 35647488 rss_rlim: 4294967295 CPU usage: start_time: 1198487617 rtime: 316 utime: 209 stime: 107 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 -1209121056 (LWP 3083)] [New Thread -1232200816 (LWP 4337)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182905
Thread 2 (Thread -1232200816 (LWP 4337))
----------- .xsession-errors (12 sec old) --------------------- package is installed and that the service is running. Max failures exceeded, exiting now Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e00003 (Save as JP) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. index:0 set language de-DE en-US en-GB fr-FR nl kbuildsycoca running... Reusing existing ksycoca DCOP Cleaning up dead connections. JACK tmpdir identified as [/dev/shm] ** (audacity:4324): CRITICAL **: clearlooks_style_draw_focus: assertion `height >= -1' failed (nautilus:3083): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2042)! --------------------------------------------------
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 ***