Bug 691968

Summary: [abrt] gvfs-gphoto2-1.6.6-1.fc14: gp_context_progress_update: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Josh Jensen <jensen.josh>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alexl, bnocera, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e7bbba1e7e207fa6fd983ecc0f4ef287c7a2cccd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:53:53 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 Josh Jensen 2011-03-30 02:29:24 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 9561 bytes
cmdline: /usr/libexec/gvfsd-gphoto2 --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
comment: This doesn't seem like a very serious bug but this is the first one I have had since I installed Fedora so I thought I would report it. Thanks for all you do.
component: gvfs
Attached file: coredump, 10534912 bytes
crash_function: gp_context_progress_update
executable: /usr/libexec/gvfsd-gphoto2
kernel: 2.6.35.11-83.fc14.i686
package: gvfs-gphoto2-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301450648
uid: 500

How to reproduce
-----
1. I plugged in my Canon Rebel XT digital camera.
2. I was prompted to select whether to open folder or other app. I selected folder.
3. The folder opened at at the top there was an option to open Shotwell. I clicked that button which probably where the bug is.

Comment 1 Josh Jensen 2011-03-30 02:29:26 UTC
Created attachment 488617 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 16:53:53 UTC
Backtrace analysis found this bug to be similar to bug #701696, closing as duplicate.

Bugs which were found to be similar to this bug: bug #574960, bug #579101, bug #611121, bug #616734, bug #620779, bug #623838, bug #695710, bug #701696

This comment is automatically generated.

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