GNOME Bugzilla – Bug 468606
crash in File Browser: I am searching in home d...
Last modified: 2007-08-21 20:29:20 UTC
Version: 2.18.3 What were you doing when the application crashed? I am searching in home directory for a file (CTRL+F): after press <enter> Gnome crashes. 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:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 494379008 vsize: 494379008 resident: 37957632 share: 20525056 rss: 37957632 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187629670 rtime: 139 utime: 123 stime: 16 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496348208 (LWP 3060)] [New Thread 1126189392 (LWP 3579)] (no debugging symbols found) 0x0000003fea8c82e6 in poll () from /lib64/libc.so.6
+ Trace 156639
Thread 2 (Thread 1126189392 (LWP 3579))
----------- .xsession-errors --------------------- Empty dir /home/davalv/.aMule/Incoming/ shared Host: amule.sourceforge.net:80 URL: http://amule.sourceforge.net/lastversion Response: 200 (Error: 0) Download size: 6 HTTP download thread ended Shutting down aMule... aMule dialog destroyed Now, exiting main app... aMule OnExit: Terminating core. Saving PartFile 1 of 2 Saving PartFile 2 of 2 All PartFiles Saved. aMule shutdown completed. (nautilus:3060): 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 ***