Bug 652714 - [abrt] gvfs-gphoto2-1.6.4-3.fc14: __pthread_mutex_lock: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-gphoto2-1.6.4-3.fc14: __pthread_mutex_lock: Process /usr/libexec/...
Keywords:
Status: CLOSED DUPLICATE of bug 719722
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7a2656e8434a67ffd679d5d88d2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-12 15:55 UTC by Igor Katalnikov
Modified: 2015-03-03 22:55 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:11:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (22.94 KB, text/plain)
2010-11-12 15:55 UTC, Igor Katalnikov 		no flags Details
View All

Description Igor Katalnikov 2010-11-12 15:55:36 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-gphoto2 --spawner :1.13 /org/gtk/gvfs/exec_spaw/6
component: gvfs
crash_function: __pthread_mutex_lock
executable: /usr/libexec/gvfsd-gphoto2
kernel: 2.6.35.6-48.fc14.x86_64
package: gvfs-gphoto2-1.6.4-3.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-gphoto2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289491274
uid: 500

How to reproduce
-----
1.Unknown
2.
3.
Comment 1 Igor Katalnikov 2010-11-12 15:55:39 UTC 
Created attachment 460084 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:11:42 UTC 
Backtrace analysis found this bug to be similar to bug #719722, closing as duplicate.

Bugs which were found to be similar to this bug: bug #553114, bug #591067, bug #591691, bug #596265, bug #600859, bug #603695, bug #608503, bug #625817, bug #627523, bug #677535, bug #680471, bug #719722, bug #758802

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 719722 ***
Note You need to log in before you can comment on or make changes to this bug.