GNOME Bugzilla – Bug 509282
crash in Open Folder: Nautilus Search: user@la...
Last modified: 2008-01-14 23:44:52 UTC
Version: 2.18.3 What were you doing when the application crashed? Nautilus Search: user@lan:filename 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-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 130129920 vsize: 130129920 resident: 57548800 share: 31903744 rss: 57548800 rss_rlim: 4294967295 CPU usage: start_time: 1200109315 rtime: 478 utime: 396 stime: 82 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 -1208408352 (LWP 26331)] [New Thread -1243620464 (LWP 5519)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 185237
Thread 2 (Thread -1243620464 (LWP 5519))
----------- .xsession-errors (6 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/b21an (nautilus:5372): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (gnome-terminal:26364): Vte-WARNING **: No handler for control sequence `device-control-string' defined. --- Hash table keys for warning below: --> file:///home/b21an (nautilus:5509): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:26331): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x192ed)! Xlib: sequence lost (0x29319 > 0x19319) in reply type 0x8! --------------------------------------------------
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 ***