Bug 804864
| Summary: | [abrt] evolution-data-server-3.2.3-2.fc16: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kahlil Hodgson <kahlil.hodgson> | ||||||||
| 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: | 16 | CC: | mbarnes, mcrha | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:0ccba8e3d49b7a56720017e2835a3c5bf739104d | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-03-22 10:52:57 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Kahlil Hodgson
2012-03-20 01:20:17 UTC
Created attachment 571259 [details]
File: dso_list
Created attachment 571260 [details]
File: maps
Created attachment 571261 [details]
File: backtrace
> comment: trying to accept an appointment to my default google calendar. > though this was fixed by most recent update Thanks for a bug report. You've right this particular issue should be fixed with evolution-data-server 3.2.3-2. The first line of the backtrace says: > warning: core file may not match specified executable file. which might mean that the e-calendar-factory process (similar with e-addressbook-factory) is still running from the previous version of evolution-data-server, aka it was not restarted yet. Am I right? Good point. Hmmm ... memory is a bit hazy so lets check the logs: yum log says evolution was updated to 3.2.3-2 at 09:12. messages says I rebooted at 12:03. I submitted the bug report around 12:20 so all should be fresh from the update. Just realized that I had previously tried to accept this invitation, which caused the crash noted in previous bug reports. Since the update, I tried to accept the invitation again and got the above crash. Perhaps there is something (file, db entry, ...) left lying around from the previous crash that is blocking the 2nd attempt at accepting? I've also noticed that there is corresponding entry in my calendar (not sure which attempt put it there), but the invitation email is still asking me to accept it. Wondering whether my 'acceptance' emails have been sent too. Damn! Just has the same error happen with a new meeting invitation so that probably rules out the above suggestion. This time the new meeting does not appear in my calendar, though. Oops, I'm sorry, this is pretty bad. I'm wrong with the "evolution-data-server-3.2.3-2 has it fixed". It doesn't, actually. There was no official release with the fix yet, thus this is really just a duplicate of bug #755791, thus I'm marking it as such. *** This bug has been marked as a duplicate of bug 755791 *** |