GNOME Bugzilla – Bug 515087
crash in Computer:
Last modified: 2008-02-08 11:18:20 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Mist Memory status: size: 85504000 vsize: 85504000 resident: 27238400 share: 16248832 rss: 27238400 rss_rlim: 4294967295 CPU usage: start_time: 1202419010 rtime: 2322 utime: 2207 stime: 115 cutime:8 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6bb76c0 (LWP 3348)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 188471
Thread 1 (Thread 0xb6bb76c0 (LWP 3348))
----------- .xsession-errors --------------------- Nautilus-Share-Message: REFRESHING SHARES Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: spawn arg "net" Nautilus-Share-Message: spawn arg "usershare" Nautilus-Share-Message: spawn arg "info" Nautilus-Share-Message: end of spawn args; SPAWNING 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 Permission non ac You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share. (nautilus:3348): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***