Bug 841729
| Summary: | [abrt] evolution-3.4.3-2.1.fc17: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 17 | CC: | lucilanga, mbarnes, mcrha | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | i686 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:34a506d984bc3348550672024a7374edbd02c73e | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2012-08-03 10:58:16 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
Mikhail
2012-07-20 04:04:39 UTC
Created attachment 599290 [details]
File: backtrace
Created attachment 599291 [details]
File: gconf_subtree
Created attachment 599292 [details]
File: xsession_errors
Created attachment 599293 [details]
File: maps
Created attachment 599294 [details]
File: dso_list
Created attachment 599295 [details]
File: build_ids
Thanks for a bug report. I see in the backtrace that ews is waiting for a response from the server, but there is no ews_soup_thread, thus it'll wait for ever. Is this related to yours bug #809364, aka this happened when you lost connection to the server? (if so, I would close this as a duplicate of that bug). I don't remember when it happens. OK, no problem. As it seems like it, I'll close this as a duplicate. *** This bug has been marked as a duplicate of bug 809364 *** |