| Summary: | [abrt] evolution-3.2.0-1.fc16: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Waugh <twaugh> | ||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | JDP803, lucilanga, mbarnes, mcrha, raj | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:fe2db140e1fd63f3700ff82276e731ffe7255246 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-10-10 06:51:32 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
Tim Waugh
2011-10-07 11:58:02 UTC
Created attachment 526874 [details]
File: backtrace
Created attachment 526875 [details]
File: dso_list
Created attachment 526876 [details]
File: maps
Package: evolution-3.2.0-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Pressing Escape on a message window before it had finished formatting the message. Yours gtkhtml3-4.2.0-1.fc16.x86_64 has a fix from the upstream bug [1] included, still, it crashes for you. I'm reopening the upstream bug and moving there this one. [1] https://bugzilla.gnome.org/show_bug.cgi?id=659217 Tim, is this specific to a certain message, please? I see it's crashing on a message hierarchy cleanup, thus in a slightly different place than the upstream bug, but not that different to deal with it in a separate bug. At least for now. I would like to get the message for testing, if possible. To help you with it, I expect it being an HTML formatted message, probably with some tables or such things, maybe a usual spam or yahoo mail? Sorry, I have no idea which message it was at this stage. No problem. Just if you face it again, try to ping me, please, if possible. Thanks in advance. *** Bug 759945 has been marked as a duplicate of this bug. *** *** Bug 851515 has been marked as a duplicate of this bug. *** |