Bug 689254

Summary: [abrt] gvfs-smb-1.7.2-2.fc15: on_pending_call_notify: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Flóki Pálsson <flokip>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: alexl, bnocera, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:67928f1d0f9f9b35a6c0097c67ea4577e2cf51ca
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:09:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Flóki Pálsson 2011-03-20 15:48:41 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 20926 bytes
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.8 /org/gtk/gvfs/exec_spaw/4
component: gvfs
Attached file: coredump, 27926528 bytes
crash_function: on_pending_call_notify
executable: /usr/libexec/gvfsd-smb-browse
kernel: 2.6.38-1.fc15.x86_64
package: gvfs-smb-1.7.2-2.fc15
rating: 4
reason: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300634367
uid: 500

How to reproduce
-----
1.  starting samba
2.
3.
After the chrash I could star samba
Comment 1 Flóki Pálsson 2011-03-20 15:48:44 UTC 
Created attachment 486477 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:09:02 UTC 
Backtrace analysis found this bug to be similar to bug #743874, closing as duplicate.

Bugs which were found to be similar to this bug: bug #663255, bug #668753, bug #679940, bug #718482, bug #743874

This comment is automatically generated.

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