Bug 719786
| Summary: | [abrt] evolution-3.4.1-2.fc17: SIGSEGV in append_escaped_text | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miloslav Trmač <mitr> | ||||||||
| Component: | evolution-rss | Assignee: | Lucian Langa <lucilanga> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | lucilanga, mbarnes, mcrha, sanzoh | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:95756a60ee01c4a6de9232b1b786ac02b5e10dff | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-07-31 22:34: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
Miloslav Trmač
2011-07-08 00:45:08 UTC
Created attachment 511817 [details]
File: maps
Created attachment 511818 [details]
File: dso_list
Created attachment 511819 [details]
File: backtrace
I was fixing similar issues in evolution, and for cases where it's uncertain whether the input string will be encoded in UTF8, it's required to validate the string before calling g_markup_printf_escaped(). I do not see whether it's correct to call this function with the given input in the place indicated by the backtrace, though the username part seems like a memory garbage. (It's just my opinion on the backtrace.) It seems this was triggered by an early free on the displayed string. @Miloslav, would you care to try the following build: https://koji.fedoraproject.org/koji/taskinfo?taskID=3231844, and report back ? Thanks. (In reply to comment #5) > It seems this was triggered by an early free on the displayed string. > @Miloslav, would you care to try the following build: > https://koji.fedoraproject.org/koji/taskinfo?taskID=3231844, and report back ? Sorry for the delay. The crash with -23 happens often, but is not 100% reproducible; anyway, -24 looks much better. With -23, I got a password prompt (with nonsensical description, e.g. HTML fragments) whenever selecting an article (although the article was already displayed in the preview pane by that time), and sooner or later Evolution crashed. With -24, I don't get any password prompts - and Evolution hasn't crashed so far. *** Bug 659630 has been marked as a duplicate of this bug. *** I right clicked on the Junk folder of one of my IMAP accounts to the Inbox, and it crashed. I was copying the Junk folder to the inbox because for some reason the junk folder is the inbox for this account and noth the actual inbox. This is a new mail account I had just created. I was able to recreate the issue with the Junk folder housing the inbox mail and not the junk mail. (This is the only folder even getting any mail). However I was not able to recreate the issue with copying the junk foder to the inbox. Only mentioned the issue with the account because well that is the only time I have seen this issue, and quite frankly I am not sure if the issue of the junk mail folder housing the inbox mail is a bug, or some issue with my server itself. Sorry I wish I could provide more information on this issue. backtrace_rating: 4 Package: evolution-3.4.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) but at the same time, it looks like that my machine got a sudden death. backtrace_rating: 4 Package: evolution-3.4.4-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |