GNOME Bugzilla – Bug 498792
crash in Computer: After type Ctrl+F, i typ...
Last modified: 2007-11-24 19:10:11 UTC
Version: 2.18.3 What were you doing when the application crashed? After type Ctrl+F, i type my search topic, just after type Enter I get this bug. 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-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 83697664 vsize: 83697664 resident: 29523968 share: 19685376 rss: 29523968 rss_rlim: 4294967295 CPU usage: start_time: 1195664578 rtime: 345 utime: 307 stime: 38 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 -1208785184 (LWP 12009)] [New Thread -1280926832 (LWP 12109)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179132
Thread 2 (Thread -1280926832 (LWP 12109))
----------- .xsession-errors --------------------- --- Hash table keys for warning below: --> file:///home/bodman (nautilus:11766): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) AFD changed from -2 to -1 (nautilus:3093): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed (nautilus:11955): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed [mpeg4 @ 0xe7f1a4]frame skip 8 Event too old, discarding Event too old, discarding AFD changed from -2 to -1 (nautilus:12009): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***