GNOME Bugzilla – Bug 468024
crash in Home Folder: in nautilus gesucht
Last modified: 2007-08-21 20:24:35 UTC
What were you doing when the application crashed? in nautilus gesucht 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: No Accessibility: Disabled GTK+ Theme: Nova-Blue Icon Theme: Fedora Memory status: size: 115056640 vsize: 115056640 resident: 40976384 share: 22482944 rss: 40976384 rss_rlim: 4294967295 CPU usage: start_time: 1187461686 rtime: 20297 utime: 17718 stime: 2579 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 -1208359200 (LWP 2988)] [New Thread -1317139568 (LWP 4156)] [New Thread -1221461104 (LWP 3925)] [New Thread -1254102128 (LWP 3807)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156203
Thread 2 (Thread -1317139568 (LWP 4156))
----------- .xsession-errors --------------------- --> file:///home/jonny (nautilus:4103): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) beryl: core: Received winTypeAtom but unable to find the window for the event --- Hash table keys for warning below: --> file:///home/jonny (nautilus:4145): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2988): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed warning: .dynamic section for "/lib/libasound.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 ***