GNOME Bugzilla – Bug 538780
crash in Computer: Browsing Windows Samba s...
Last modified: 2008-06-17 17:51:40 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing Windows Samba shares with nautilus Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 84041728 vsize: 84041728 resident: 26619904 share: 17522688 rss: 26619904 rss_rlim: 4294967295 CPU usage: start_time: 1213713630 rtime: 465 utime: 438 stime: 27 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c14720 (LWP 2178)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200661
Thread 1 (Thread 0xb6c14720 (LWP 2178))
----------- .xsession-errors (6 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Initializing gnome-mount extension fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013 ** (nautilus:2178): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « Public »), veuillez avertir la liste de diffusion de gnome-vfs. --------------------------------------------------
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 ***