GNOME Bugzilla – Bug 527928
crash in Open Folder:
Last modified: 2008-04-13 23:19:05 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 98439168 vsize: 98439168 resident: 32051200 share: 16392192 rss: 32051200 rss_rlim: 4294967295 CPU usage: start_time: 1208091401 rtime: 9968 utime: 9181 stime: 787 cutime:22 cstime: 12 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b7d720 (LWP 4105)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 195147
Thread 1 (Thread 0xb6b7d720 (LWP 4105))
----------- .xsession-errors (11 sec old) --------------------- CALLBACK: fill-authentication!!! ** (nautilus:4105): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C"), please tell the gnome-vfs mailing list. closing ** (update-notifier:4125): WARNING **: no cdrom: disk Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00058 (e-QIP_Inve) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00058 (e-QIP_Inve) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***