abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/2 component: gvfs crash_function: g_assertion_message executable: /usr/libexec/gvfsd-smb kernel: 2.6.35.4-28.fc14.i686 package: gvfs-smb-1.6.4-2.fc14 rating: 4 reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1286400628 uid: 500 How to reproduce ----- 1. Trying to connect to a bookmarked SMB share from nautilus.
Created attachment 451996 [details] File: backtrace
Package: gvfs-smb-1.6.4-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Suspend machine 2. Resume machine 3. Right-click smb share on desktop, and select unmount 4. Open nautilus and select share from bookmarks All of the above was while the machine was under very heavy IO and CPU load.
This still happens to me very time I mount a samba share for the first time. After the first time, I click the share again and it works. After rebooting, it will crash again, then work. Using: gvfs-smb-1.6.4-3.fc14.i686
*** Bug 645129 has been marked as a duplicate of this bug. ***
*** Bug 650318 has been marked as a duplicate of this bug. ***
*** Bug 650388 has been marked as a duplicate of this bug. ***
*** Bug 650428 has been marked as a duplicate of this bug. ***
Package: gvfs-smb-1.6.4-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. create a bookmark in nautilus to an existing SMB-Share (with username/password) 2. shut down the SMB-Server on the other end 3. try to connect to the SMB-Share while the server is down, by clicking on the bookmark Comment ----- reproducible...
Backtrace analysis found this bug to be similar to bug #657179, closing as duplicate. Bugs which were found to be similar to this bug: bug #585657, bug #592649, bug #597371, bug #598081, bug #601013, bug #605005, bug #605239, bug #611351, bug #624899, bug #625287, bug #645129, bug #649350, bug #650318, bug #650428, bug #652139, bug #655115, bug #655586, bug #655703, bug #657179, bug #657631, bug #665054, bug #666201 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 657179 ***