Bug 611944

Summary: [abrt] crash in syncevolution-1:1.0-3.fc13: dbus_error_is_set: Process /usr/bin/syncevolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ricardo Alonso <ricardoalonsos>
Component: syncevolutionAssignee: Peter Robinson <pbrobinson>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dmaphy, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:9a056249d754174b8b48940a5235035d70ed86f2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-06 23:06:31 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 Ricardo Alonso 2010-07-06 22:05:18 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: syncevolution
component: syncevolution
crash_function: dbus_error_is_set
executable: /usr/bin/syncevolution
global_uuid: 9a056249d754174b8b48940a5235035d70ed86f2
kernel: 2.6.33.5-124.fc13.x86_64
package: syncevolution-1:1.0-3.fc13
rating: 4
reason: Process /usr/bin/syncevolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

comment
-----
1. Install: # yum install syncevolution
2. Run: $ syncevolution
3. It crashes with message:
[ricardo.alonso@ricardoalonso ~]$ syncevolution 
Segmentation fault (core dumped)

The SELinux was in Permissive mode.

How to reproduce
-----
1. Install: # yum install syncevolution
2. Run: $ syncevolution
3. It crashes with message:
[ricardo.alonso@ricardoalonso ~]$ syncevolution 
Segmentation fault (core dumped)

The SELinux was in Permissive mode.

Comment 1 Ricardo Alonso 2010-07-06 22:05:21 UTC
Created attachment 429920 [details]
File: backtrace

Comment 2 Peter Robinson 2010-07-06 23:06:31 UTC

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