Description of problem: updated kernel-3.11.6-302.fc20.x86_64 Version-Release number of selected component: evolution-3.10.1-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: evolution crash_function: WebCore::Style::determineChange executable: /usr/bin/evolution kernel: 3.11.6-302.fc20.x86_64 runlevel: N 5 type: CCpp Truncated backtrace: Thread no. 1 (10 frames) #0 WebCore::Style::determineChange at Source/WebCore/style/StyleResolveTree.cpp:61 #1 WebCore::Style::resolveTree at Source/WebCore/style/StyleResolveTree.cpp:474 #2 WebCore::Document::recalcStyle at Source/WebCore/dom/Document.cpp:1777 #3 WebCore::Document::styleResolverChanged at Source/WebCore/dom/Document.cpp:3193 #4 WebCore::Document::didRemoveAllPendingStylesheet at Source/WebCore/dom/Document.cpp:2795 #5 WebCore::DocumentStyleSheetCollection::removePendingSheet at Source/WebCore/dom/DocumentStyleSheetCollection.cpp:232 #6 WebCore::InlineStyleSheetOwner::sheetLoaded at Source/WebCore/dom/InlineStyleSheetOwner.cpp:179 #7 WebCore::StyleSheetContents::checkLoaded at Source/WebCore/css/StyleSheetContents.cpp:361 #8 WebCore::InlineStyleSheetOwner::createSheet at Source/WebCore/dom/InlineStyleSheetOwner.cpp:163 #9 WebCore::InlineStyleSheetOwner::createSheetFromTextContents at Source/WebCore/dom/InlineStyleSheetOwner.cpp:107
Created attachment 819106 [details] File: backtrace
Created attachment 819107 [details] File: cgroup
Created attachment 819108 [details] File: core_backtrace
Created attachment 819109 [details] File: dso_list
Created attachment 819110 [details] File: environ
Created attachment 819111 [details] File: limits
Created attachment 819112 [details] File: maps
Created attachment 819113 [details] File: open_fds
Created attachment 819114 [details] File: proc_pid_status
Created attachment 819115 [details] File: var_log_messages
Thanks for a bug report. I move this to webkitgtk3, because it's the place where the crash happened. From the backtrace, the 'settings' variable is NULL for some reason, thus its dereferencing causes the crash.
I see exactly the same (SIGSEGV from the same place in the same file). This only started for me after I installed the flash plugin /usr/lib64/mozilla/plugins/libflashplayer.so (which is a symlink to /usr/lib64/flash-plugin/libflashplayer.so. It looks like webkit automagically searches for browser plugins to load (confirmed with strace). Here is the really weird bit. Copying /usr/lib64/mozilla/plugins/libflashplayer.so to ~/.mozilla/plugins stops the crashes. Yes, webkit finds ~/.mozilla/plugins/libflashplayer.so (lsof confirms this) but for some reason the bug depends on where the plugin is found!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.