GNOME Bugzilla – Bug 552653
crash in File Browser:
Last modified: 2008-09-18 23:53:24 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango-Blue-Materia Memory status: size: 561131520 vsize: 561131520 resident: 67956736 share: 19296256 rss: 67956736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1221639617 rtime: 1944 utime: 1805 stime: 139 cutime:5 cstime: 3 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 0x2af72214c240 (LWP 3386)] (no debugging symbols found) 0x00002af71b642edf in waitpid () from /lib/libpthread.so.0
+ Trace 206893
Thread 1 (Thread 0x2af72214c240 (LWP 3386))
----------- .xsession-errors (18 sec old) --------------------- CALLBACK: fill-authentication!!! 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: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3386): WARNING **: Hit unhandled case 31 (Anulowano operację) in fm_report_error_loading_directory --------------------------------------------------
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 ***