GNOME Bugzilla – Bug 529320
crash in Home Folder: Accessing Samba Shares, ...
Last modified: 2008-04-22 17:26:17 UTC
What were you doing when the application crashed? Accessing Samba Shares, Nautilus crashes Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.3 #1 SMP PREEMPT Mon Mar 10 10:30:05 CET 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX Memory status: size: 133705728 vsize: 133705728 resident: 76185600 share: 17821696 rss: 76185600 rss_rlim: 4294967295 CPU usage: start_time: 1208835703 rtime: 3024 utime: 2837 stime: 187 cutime:550 cstime: 44 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 0xb6be3720 (LWP 3832)] [New Thread 0xb287eb90 (LWP 5010)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 195825
Thread 1 (Thread 0xb6be3720 (LWP 3832))
----------- .xsession-errors (3371 sec old) --------------------- Initializing gnome-mount extension 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 0 Nautilus-Share-Message: caller wants GKeyFile Nautilus-Share-Message: success from calling net usershare and parsing its output Nautilus-Share-Message: ------------------------------------------ ** Message: <info> Sie sind nun mit dem Kabelnetzwerk verbunden. --------------------------------------------------
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 ***