GNOME Bugzilla – Bug 505465
crash in Open Folder: using the system explore...
Last modified: 2007-12-25 00:10:41 UTC
Version: 2.18.3 What were you doing when the application crashed? using the system explorer to search for a file, then clicked on the \ windows to expand /usr 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 97525760 vsize: 97525760 resident: 34947072 share: 21868544 rss: 34947072 rss_rlim: 4294967295 CPU usage: start_time: 1198521921 rtime: 744 utime: 566 stime: 178 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 -1208686880 (LWP 4110)] [New Thread -1210786928 (LWP 4134)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182941
Thread 2 (Thread -1210786928 (LWP 4134))
----------- .xsession-errors --------------------- Loading "priorities" plugin Loading "refresh-updatesd" plugin Loading mirror speeds from cached hostfile 0 packages excluded due to repository protections 0 packages excluded due to repository priority protections Loading mirror speeds from cached hostfile Loading mirror speeds from cached hostfile 2007-12-24 10:29:00.183 XMLParse::LoadTheme using /usr/share/mythtv/themes/default/stream-ui.xml (nautilus:3450): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x7116b)! Xlib: sequence lost (0x800f1 > 0x711a6) in reply type 0xe9! (nautilus:4110): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0xdca3)! --------------------------------------------------
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 ***