Bug 649168

Summary: [abrt] gvfs-smb-1.6.4-2.fc14: command_read_cb: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jonathan
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, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cfee4ce6f43f3387f14f2a35d88bed869bd86960
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 14:22:06 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 jonathan 2010-11-03 03:33:21 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/3
component: gvfs
crash_function: command_read_cb
executable: /usr/libexec/gvfsd-smb
kernel: 2.6.35.6-48.fc14.x86_64
package: gvfs-smb-1.6.4-2.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288750550
uid: 500

How to reproduce
-----
1. Run PS3 Media Server
2. Play a file through PS3MS that's on an smb share using the .gvfs directory.
3. Wait a few minutes to a few hours. Seems to happen pretty much at random, but always in the middle of playback.

Comment 1 jonathan 2010-11-03 03:33:23 UTC
Created attachment 457349 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:22:06 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:22:06 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #628501.

Sorry for the inconvenience.