GNOME Bugzilla – Bug 473609
crash in Open Folder: Searching for a file
Last modified: 2007-09-05 15:38:03 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching for a file 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 97701888 vsize: 97701888 resident: 33878016 share: 20500480 rss: 33878016 rss_rlim: 4294967295 CPU usage: start_time: 1188910012 rtime: 1059 utime: 975 stime: 84 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 -1208101152 (LWP 3862)] [New Thread -1250952304 (LWP 4134)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 160411
Thread 2 (Thread -1250952304 (LWP 4134))
----------- .xsession-errors (9 sec old) --------------------- localuser:at being added to access control list SESSION_MANAGER=local/yoda:/tmp/.ICE-unix/3752 compiz: Another composite manager is already running on screen: 0 compiz: No manageable screens found on display :0.0 compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. error getting update info: Cannot open/read repomd.xml file for repository: fedora compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. --- Hash table keys for warning below: --> file:///home/at (nautilus:4060): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3862): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0xbf3a)! --------------------------------------------------
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 ***