Bug 630127
| Summary: | [abrt] evolution-2.31.90-1.fc14: et_get_n_children: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Manuel Morales <mmorales> | ||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | beland, flextc, jeff.raber, kanelxake, lucilanga, mbarnes, mcepl, mcepl, mcrha | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:23663c536ed6f5fdbf4c93a5f64733f8bad70b1d | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-09-21 17:16:30 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
Manuel Morales
2010-09-03 18:40:33 UTC
Created an attachment (id=442956) File: backtrace Package: evolution-2.31.90-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start evolution 2. Switch to Calendar Forgot to say that "evolution --component mail" makes evolution start again, but crash as soon as calendar is selected again. Package: evolution-2.31.90-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Switching Evolution to Calendar View leads to crash 100% of time 2. 3. I can very well reproduce this (unfortunately). Try disabling accessibility. Evolution's accessibility support is known to be extremely flakey. Duping to 629386 as it has a (more) detailed workaround. *** This bug has been marked as a duplicate of bug 629386 *** *** Bug 637512 has been marked as a duplicate of this bug. *** *** Bug 640132 has been marked as a duplicate of this bug. *** |