Bug 134851
Summary: | evolution-data-server has achieved immortality | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Lee <clee> |
Component: | evolution-data-server | Assignee: | Dave Malcolm <dmalcolm> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-17 18:58: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: | |||
Bug Depends On: | |||
Bug Blocks: | 134598 |
Description
Chris Lee
2004-10-06 18:58:11 UTC
I've filed some notes on this upstream here: http://bugzilla.ximian.com/show_bug.cgi?id=68533 I've added a workaround to e-d-s-1.0.2-3: The problem is that there's a reference leak somewhere in the code, filed upstream here: http://bugzilla.ximian.com/show_bug.cgi?id=68533 This reference leak means that when each calendar backend goes away, the corresponding GObject doesn't get finalized; in particular there's a calendar backend that generates events for the birthdays and anniversaries of the people in your local addressbook - and this holds open a reference to the local addressbook. Hence the final addressbook never goes away, and e-d-s outlives the session. Unfortunately I haven't been able to track down the reference leak; so I've gone for a workaround instead: as well as e-d-s going away when all calendars and addressbooks have gone away, e-d-s should also now go away in the case when there are no calendars open, and only a single addressbook. I don't _think_ it's possible to trigger this state via normal uses of the packages, apart from when a shutdown is occurring that has been blocked by the reference leak bug. Resolving as DEFERRED - the symptoms of the bug are fixed, but fixing the deeper problem will not happen in this release of the product. Looks like there's another possible way to trigger these symptoms, described here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139834#c3 |