GNOME Bugzilla – Bug 532511
crash in Open Folder: Browsing a samba share v...
Last modified: 2008-05-10 18:27:42 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing a samba share via Computer->Network Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 125202432 vsize: 125202432 resident: 61546496 share: 19755008 rss: 61546496 rss_rlim: 4294967295 CPU usage: start_time: 1210391336 rtime: 7235 utime: 6717 stime: 518 cutime:1 cstime: 4 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 0xb6c3f720 (LWP 22871)] [New Thread 0xb5802b90 (LWP 22780)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197393
Thread 1 (Thread 0xb6c3f720 (LWP 22871))
----------- .xsession-errors (120 sec old) --------------------- No such file or directory params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf": No such file or directory Using netbios name CALIRAISIN. Using workgroup WORKGROUP. Could not open from LAN: 'smb://california/storage/recordings/Dirty%20Jobs%20-%202007-06-28%2C%2010-00%20PM%20-%20Roadkill%20Cleaners.mpg' Failed to open smb://california/storage/recordings/Dirty%20Jobs%20-%202007-06-28%2C%2010-00%20PM%20-%20Roadkill%20Cleaners.mpg. Exiting... (Quit) UPDATING SHAPE UPDATING SHAPE ** (gnome-system-monitor:23795): WARNING **: SELinux was found but is not enabled. --------------------------------------------------
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 ***