GNOME Bugzilla – Bug 468566
crash in File Browser: Looking for a file
Last modified: 2007-08-21 20:29:01 UTC
Version: 2.18.3 What were you doing when the application crashed? Looking 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 85540864 vsize: 85540864 resident: 31440896 share: 21233664 rss: 31440896 rss_rlim: 4294967295 CPU usage: start_time: 1187624680 rtime: 2616 utime: 1243 stime: 1373 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 -1208596768 (LWP 2727)] [New Thread -1232184432 (LWP 3060)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156608
Thread 2 (Thread -1232184432 (LWP 3060))
----------- .xsession-errors --------------------- --- Hash table keys for warning below: --> file:///root (nautilus:3054): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2727): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x7082)! warning: .dynamic section for "/usr/lib/libgstinterfaces-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstvideo-0.10.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***