Bug 833865
Summary: | [abrt] evolution-3.4.2-1.fc17: do_idle_run_queue: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Douglas Furlong <bugzilla_rhn> | ||||||||||||||
Component: | libsoup | Assignee: | Dan Winship <danw> | ||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 17 | CC: | danw, lucilanga, mbarnes, mcrha | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | abrt_hash:b8a26c53c135783b02d9787620d5c5066cf28e51 | ||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2013-07-31 23:29:56 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
Douglas Furlong
2012-06-20 13:43:51 UTC
Created attachment 593218 [details]
File: backtrace
Created attachment 593219 [details]
File: gconf_subtree
Created attachment 593220 [details]
File: smolt_data
Created attachment 593221 [details]
File: maps
Created attachment 593222 [details]
File: dso_list
Created attachment 593223 [details]
File: build_ids
Thanks for a bug report. It seems to me like a bug/issue in libsoup, as it's deep in its code. Dan, did you see anything similar already, please? Or any insight, what can be going on? looks like this could happen if you quit (or delete an account) while a request is in progress I have not been adding/deleting accounts for about a week now, not sure what you mean by quitting an account. I meant quitting evolution... the crash should (as far as i can tell) only happen when evolution destroys the SoupSession object while a request is in progress. So, it seems like that would probably happen when quitting evolution, when deleting an account, maybe when going offline? (If you weren't doing any of those things then it might point to a reference counting bug in evolution, but more likely it just means there's some other case where evolution destroys the SoupSession that I'm just not aware of; a reference counting bug would be more likely to cause lots of crashes for lots of people.) Would a killall -9 evolution count as quitting evolution? As, when calendar's are concerned, that's not an infrequent occurrence. 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. |