Bug 739319
Summary: | evolution-mapi calendar fails to reconnect after going offline (with OpenVPN) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Derek Atkins <warlord> |
Component: | evolution-mapi | Assignee: | Matthew Barnes <mbarnes> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | mbarnes, mcrha |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-19 09:03:34 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: |
Description
Derek Atkins
2011-09-17 15:52:17 UTC
Thanks for a bug report. There is an opened upstream bug, which is created from bug #558651, thus I'm marking this as a duplicate of it. With respect of: > Also, the e-calendar-factory should die when evolution quits. The calendar factory does quit, after 10 seconds delay if nothing is using it. If there left any connections to it, then it doesn't stop and is kept running. *** This bug has been marked as a duplicate of bug 558651 *** Okay, so how do I tell what's connected to it? It does not seem to be dying on its own after Evo exits, even if I wait 10-15 seconds before I retry. I do not know except of some deeper debugging lower in the factory code. Similar situation can happen when evolution is closed, but it doesn't properly free all ECalClient-s it had opened. It's not only about evolution itself, basically any process which is using the calendar factory and is not disposing created ECalClient-s can make the factory feel it's in use. Other process which can have opened connections to the factory is the evolution-alarm-notify process. I'm happy to try to help test for you, but the fact remains that the calendar factory doesn't die, even after I kill Evo. And evo-mapi calendar will not work until the calendar factory restarts. So this is still a major issue, IMHO, and possibly different than the "wont reconnect" issue. The calendar factory probably doesn't terminate because the GNOME Shell calendar is using it. E-D-S services are not just there to serve Evolution. |