Bug 671025

Summary: [abrt] gvfs-smb-1.6.6-1.fc14: gkr_operation_block_and_unref: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: JR <zerodl>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: alexl, bnocera, jmrbev, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:525677b4a3be98ab6373b878b4e5f090f0403594
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 19:29:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description JR 2011-01-19 22:50:51 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.9 /org/gtk/gvfs/exec_spaw/4
component: gvfs
crash_function: gkr_operation_block_and_unref
executable: /usr/libexec/gvfsd-smb-browse
kernel: 2.6.35.6-45.fc14.i686
package: gvfs-smb-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295477407
uid: 500

How to reproduce
-----
1.
2.
3.
just opened my share, couldnt mount, crashed
Comment 1 JR 2011-01-19 22:50:52 UTC 
Created attachment 474371 [details]
File: backtrace
Comment 2 Jose Rodriguez 2011-03-12 02:37:16 UTC 
Package: gvfs-smb-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Using Gigolo with a windows shared
2.
3.
Comment 3 abrt-bot 2012-03-20 19:29:55 UTC 
Backtrace analysis found this bug to be similar to bug #657460, closing as duplicate.

Bugs which were found to be similar to this bug: bug #599899, bug #615075, bug #625488, bug #652149, bug #653927, bug #657460, bug #664972, bug #674057

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 657460 ***