Version-Release number of selected component: evolution-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: WTF::StringImpl::hashSlowCase executable: /usr/bin/evolution kernel: 3.6.10-5.fc18.x86_64 remote_result: NOTFOUND uid: 14316 Truncated backtrace: Thread no. 1 (10 frames) #0 WTF::StringImpl::hashSlowCase at /lib64/libjavascriptcoregtk-3.0.so.0 #1 WebCore::PluginDatabase::refresh at /lib64/libwebkitgtk-3.0.so.0 #2 WebCore::PluginDatabase::installedPlugins at /lib64/libwebkitgtk-3.0.so.0 #3 WebCore::FrameLoader::defaultObjectContentType at /lib64/libwebkitgtk-3.0.so.0 #4 WebCore::HTMLPlugInImageElement::isImageType at /lib64/libwebkitgtk-3.0.so.0 #5 WebCore::HTMLObjectElement::parseAttribute at /lib64/libwebkitgtk-3.0.so.0 #6 WebCore::Element::attributeChanged at /lib64/libwebkitgtk-3.0.so.0 #7 WebCore::Element::parserSetAttributes at /lib64/libwebkitgtk-3.0.so.0 #8 WebCore::HTMLConstructionSite::createHTMLElement at /lib64/libwebkitgtk-3.0.so.0 #9 WebCore::HTMLConstructionSite::insertHTMLElement at /lib64/libwebkitgtk-3.0.so.0
Created attachment 664477 [details] File: backtrace
Created attachment 664478 [details] File: cgroup
Created attachment 664479 [details] File: core_backtrace
Created attachment 664480 [details] File: dso_list
Created attachment 664481 [details] File: environ
Created attachment 664482 [details] File: limits
Created attachment 664483 [details] File: maps
Created attachment 664484 [details] File: open_fds
Created attachment 664485 [details] File: proc_pid_status
Created attachment 664486 [details] File: var_log_messages
Created attachment 664487 [details] File: xsession_errors
Thanks for a bug report. I see this crashed deep in WebKitGTK3 thread, with not much interaction from evolution itself. Is it possible that it is caused by a concrete message, which you select in Evolution and instead of it being shown in a preview panel evolution crashes? Could you provide the message, or any steps you did before the crash, please?
I'm sorry, I don't remember what happened before I take notice of this crash report.
I've had a number of these and abrt has associated it with this bug, so I assume it is very much the same. In the most recent cases I've had, it has happened when Evolution was just starting, straight after logging in. It was attempting to display the oldest message in my Inbox. If I try and start it again after an abort it just does the same thing again. In all cases it displays in the preview pane that it is retrieving the oldest message (item 3 out of interest). However, if I start with --disable-preview it starts fine, and once it is all running I can enable the preview pane and even display the message that it is failing on. As such I don't think it is a problem with the message, but something happening during start up. Also, I'm now running evolution-3.6.4-2.fc18.x86_64 and webkit webkitgtk3-1.10.2-3.fc18.x86_64 and still seeing it.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.