Bug 632823 - [abrt] gvfs-gphoto2-1.6.2-1.fc13: __pthread_mutex_lock: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-gphoto2-1.6.2-1.fc13: __pthread_mutex_lock: Process /usr/libexec/...
Keywords:
Status: CLOSED DUPLICATE of bug 620109
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d2e292364510dde49ce7a69b1a8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-11 08:34 UTC by Jeff lats
Modified: 2015-03-03 22:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:46:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (11.47 KB, text/plain)
2010-09-11 08:34 UTC, Jeff lats
no flags Details

Description Jeff lats 2010-09-11 08:34:18 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-gphoto2 --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
comment: Running Digicam to import pictures you end up with a conflict between gvfs and digicam.  gvfs opens a file explorer and digicam opens a import window.  Closing teh gvfs windows causes this problem.
component: gvfs
crash_function: __pthread_mutex_lock
executable: /usr/libexec/gvfsd-gphoto2
kernel: 2.6.34.6-54.fc13.x86_64
package: gvfs-gphoto2-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284192518
uid: 500

Comment 1 Jeff lats 2010-09-11 08:34:22 UTC
Created an attachment (id=446637)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 17:46:39 UTC

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

Comment 3 Karel Klíč 2010-11-08 17:46:39 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 #620109.

Sorry for the inconvenience.


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