GNOME Bugzilla – Bug 541576
crash in File Browser:
Last modified: 2008-07-04 19:14:03 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-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 115306496 vsize: 115306496 resident: 43909120 share: 18440192 rss: 43909120 rss_rlim: 4294967295 CPU usage: start_time: 1215181294 rtime: 23913 utime: 7362 stime: 16551 cutime:121 cstime: 33 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 0xb6aa5720 (LWP 4446)] (no debugging symbols found) 0xb7eee424 in __kernel_vsyscall ()
+ Trace 202053
Thread 1 (Thread 0xb6aa5720 (LWP 4446))
----------- .xsession-errors --------------------- Nautilus-Share-Message: returned from spawn: SUCCESS: Nautilus-Share-Message: exit code 255 Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Permiso denegado You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:4446): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Documents»), avise a la lista de correo de gnome-vfs. warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 ***