GNOME Bugzilla – Bug 485416
crash in Computer: Recherche automtique d'u...
Last modified: 2007-10-13 22:35:21 UTC
Version: 2.18.3 What were you doing when the application crashed? Recherche automtique d'un document sous le critère nom : "histoire" 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: Simple Memory status: size: 101847040 vsize: 101847040 resident: 38461440 share: 21082112 rss: 38461440 rss_rlim: 4294967295 CPU usage: start_time: 1192018539 rtime: 1711 utime: 1580 stime: 131 cutime:0 cstime: 2 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 -1208551712 (LWP 2842)] [New Thread -1339114608 (LWP 9979)] (no debugging symbols found) 0x00588402 in __kernel_vsyscall ()
+ Trace 169272
Thread 2 (Thread -1339114608 (LWP 9979))
----------- .xsession-errors --------------------- package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now compiz: pixmap 0xe1e3f6 can't be bound to texture compiz: pixmap 0xe1f9fa can't be bound to texture (nautilus:2842): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x3dbe9)! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 484773 ***