Bug 629805 - [abrt] gvfs-gphoto2-1.6.3-1.fc14: backend_died: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-gphoto2-1.6.3-1.fc14: backend_died: Process /usr/libexec/gvfsd-gp...
Keywords:
Status: CLOSED DUPLICATE of bug 617338
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3e3f307ba5126b54106031f9e07...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-03 02:16 UTC by Jon Dufresne
Modified: 2015-03-03 22:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:30:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (9.66 KB, text/plain)
2010-09-03 02:16 UTC, Jon Dufresne 		no flags Details
View All

Description Jon Dufresne 2010-09-03 02:16:56 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-gphoto2 --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
component: gvfs
crash_function: backend_died
executable: /usr/libexec/gvfsd-gphoto2
kernel: 2.6.35.4-12.fc14.x86_64
package: gvfs-gphoto2-1.6.3-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1283479500
uid: 500

How to reproduce
-----
1. Had camera plugged in, browsing in nautilus
2. Clicked the "eject" icon next to the volume in the nautilus side bar
3. gphoto crashed
Comment 1 Jon Dufresne 2010-09-03 02:16:57 UTC 
Created an attachment (id=442776)
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:30:03 UTC 

*** This bug has been marked as a duplicate of bug 617338 ***
Comment 3 Karel Klíč 2010-11-08 18:30:03 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 #617338.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.