GNOME Bugzilla – Bug 469195
crash in Open Folder:
Last modified: 2007-08-30 17:07:37 UTC
Version: 2.18.3 What were you doing when the application crashed? 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:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: glass-icons Memory status: size: 138190848 vsize: 138190848 resident: 33566720 share: 20385792 rss: 33566720 rss_rlim: 4294967295 CPU usage: start_time: 1187759402 rtime: 2925 utime: 2752 stime: 173 cutime:0 cstime: 1 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 -1208244512 (LWP 2333)] [New Thread -1231324272 (LWP 4365)] [New Thread -1274803312 (LWP 3724)] [New Thread -1241814128 (LWP 3721)] [New Thread -1220834416 (LWP 3720)] [New Thread -1252303984 (LWP 3709)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 157093
Thread 2 (Thread -1231324272 (LWP 4365))
----------- .xsession-errors (11 sec old) --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! (nautilus:2333): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2641a)! --------------------------------------------------
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 ***