GNOME Bugzilla – Bug 544130
crash in Open Folder:
Last modified: 2008-07-22 12:33:20 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mac_OS_X_Leopard_for_Debian_v1.4 Memory status: size: 547217408 vsize: 547217408 resident: 37527552 share: 17158144 rss: 37527552 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216712205 rtime: 1082 utime: 938 stime: 144 cutime:49 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f444aea57a0 (LWP 3341)] (no debugging symbols found) 0x00007f4445ec7edf in waitpid () from /lib/libpthread.so.0
+ Trace 203474
Thread 1 (Thread 0x7f444aea57a0 (LWP 3341))
----------- .xsession-errors (54 sec old) --------------------- ** Message: GetValue variable 2 (2) ** (nautilus:3341): WARNING **: Hit unhandled case 46 (Timeout reached) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a6 specified for 0x14042fe (). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a6 specified for 0x1404517 (). connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! --------------------------------------------------
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 522534 ***