| Summary: | [abrt] evolution-data-server-2.32.2-1.fc14: talloc_abort: Process /usr/libexec/e-calendar-factory was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vincent Gerris <vgerris> | ||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | mbarnes, mcrha | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:bc850fd90ab4e2e4725caebcfefa5c988a138029 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-05 06:15:04 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Vincent Gerris
2011-05-04 12:15:49 UTC
Created attachment 496768 [details]
File: backtrace
Package: evolution-data-server-2.32.2-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start evolution 2. click on calendar if not enabled (when it is nothing has to be done) 3. error appears: Error on mapi://username.nl/ Failed to fetch changes from a server: QueryRows: MAPI error (0x80040fff) occurred The Evolution calendar has quit unexpectedly. Your calendars will not be available until Evolution is restarted. Comment ----- Install evolution-mapi from test repo: 0.32.2-2 fill in details for account, use MAPI. Then do above steps Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 701971 *** |