abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/2 component: gvfs crash_function: raise executable: /usr/libexec/gvfsd-smb kernel: 2.6.35.6-48.fc14.x86_64 package: gvfs-smb-1.6.4-3.fc14 rating: 4 reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1289479122 uid: 500 comment ----- I tried to copy a directory (76 files/directories, 15,8 Mb total) to SMB share using Nautilus. Server OS is MS Windows Server 2008 service pack 2. libsmbclient package version is 3.5.6-69.fc14 (x86_64). It was very similar to bug 580079. Just like in that case mountpoint for network share in Nautilus (in Places menu) disappeared, and the nautilus process showed 100% CPU load until I killed it. Th only major difference with bug 580079 I can tell is that then similar error happened (sometimes, and was quite rare, and nedded many attempts to reproduce) while copiing large amount of data (several gigabytes with thousands of files), whereas now it was rather small folder. Right after the error i reconnected to SMB share with Nautilus and have succesfully copied that very same folder.
Created attachment 459758 [details] File: backtrace
One more notion: maybe we need Nautilus to handle such errors in more graceful way. As I've said before, I had to kill nautilus process with 100% CPU load. And right now I still have an icon in notification area, and can open/hide window called "File actions" or "Actions with files" (I'm not sure what title it has in English) -- that's the window showing text "XX files are bing copied from <source> to <destination>", progress bar and red stop button. It's frosen -- i.e. neigther file numbers and size nor progress bar aren't changing. And I have no way to close it.
Backtrace analysis found this bug to be similar to bug #703302, closing as duplicate. Bugs which were found to be similar to this bug: bug #655639, bug #658912, bug #665743, bug #668064, bug #669890, bug #678460, bug #692791, bug #703302 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 703302 ***