GNOME Bugzilla – Bug 467828
crash in File Browser: looking for ANT file
Last modified: 2007-08-21 20:25:03 UTC
Version: 2.18.3 What were you doing when the application crashed? looking for ANT 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: 119300096 vsize: 119300096 resident: 35680256 share: 21630976 rss: 35680256 rss_rlim: 4294967295 CPU usage: start_time: 1187389510 rtime: 4567 utime: 2901 stime: 1666 cutime:12 cstime: 5 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 -1208994080 (LWP 3113)] [New Thread -1266533488 (LWP 3764)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156040
Thread 2 (Thread -1266533488 (LWP 3764))
----------- .xsession-errors --------------------- Current serial number in output stream: 82012 AFD changed from -2 to -1 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 42 (X_SetInputFocus) Resource id in failed request: 0xe00843 Serial number of failed request: 9038 Current serial number in output stream: 9040 --- Hash table keys for warning below: --> file:///root (nautilus:3756): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3113): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x26b51)! --------------------------------------------------
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 ***