GNOME Bugzilla – Bug 503499
crash in Home Folder: Try to install Google De...
Last modified: 2007-12-16 19:10:27 UTC
What were you doing when the application crashed? Try to install Google Desktop 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: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 93597696 vsize: 93597696 resident: 30445568 share: 18980864 rss: 30445568 rss_rlim: 4294967295 CPU usage: start_time: 1197590303 rtime: 505 utime: 409 stime: 96 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 -1208256800 (LWP 2881)] [New Thread -1302910064 (LWP 3384)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181813
Thread 2 (Thread -1302910064 (LWP 3384))
----------- .xsession-errors (7 sec old) --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. --- Hash table keys for warning below: --> file:///home/tassinari (nautilus:3337): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/tassinari (nautilus:3373): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2881): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0xd73f)! --------------------------------------------------
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 ***