Bug 824727

Summary: Can't close evolution
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-28 07:16:02 UTC Type: Bug
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
backtrace evolution
none
backtrace from another machine none

Description Mikhail 2012-05-24 05:08:00 UTC
Created attachment 586532 [details]
backtrace evolution

Description of problem: Can't close evolution

Comment 1 Mikhail 2012-05-26 20:38:42 UTC
Created attachment 587037 [details]
backtrace from another machine

Comment 2 Mikhail 2012-05-26 20:42:35 UTC
Kill with SEGV for more information here: https://bugzilla.redhat.com/show_bug.cgi?id=825490

Comment 3 Milan Crha 2012-05-28 07:13:26 UTC
*** Bug 825490 has been marked as a duplicate of this bug. ***

Comment 4 Milan Crha 2012-05-28 07:16:02 UTC
Thanks for a bug report. The first backtrace seems to be stuck in folder update/synchronization before it quits. Hard to guess what is the issue. I only see that the backtrace is missing debuginfo for evolution-data-server. It'll be good to have it installed too, in the same version as is the binary package.

The second backtrace, from another machine, shows evolution idle.

I just found upstream yours related bug #807908, which describes the same issue, thus I'm marking this as a duplicate of it.

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

Comment 5 Milan Crha 2012-05-29 05:55:25 UTC
*** Bug 825742 has been marked as a duplicate of this bug. ***