| Summary: | No calendar entries shown in evolution-3.2.1-1.fc16.x86_64 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark van Rossum <mvanross> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | 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: | 2011-10-19 13:14:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Mark van Rossum
2011-10-19 08:56:27 UTC
Thanks for a bug report. Could you check if e-calendar-factory process is running? It might help to run evolution from console and see whether there will be printed any critical warning explaining the issue, probably with a communication towards the factory. Before you run evolution from console, make sure the factory process is not running (it should be started automatically when the calendar part of evolution is required, and then it should be shown as a running process). Cool! A restart of e-calendar-fac fixed it. (Should this be done by the install script?) (In reply to comment #2) > A restart of e-calendar-fac fixed it. > > (Should this be done by the install script?) Hmm, it should not be ideally needed, especially when moving from 3.20 to 3.2.1, I'm not sure what could broke there. |