Description of problem: I tried to start Akregator but it never opened. When I got back to the computer there was a notification and the ABRT icon on my panel. I clicked on the notification and the message said that ABRT had detected a crash in kdepim. I submitted a report on the kdepim crash by clicking on the "report" button in the panel notification message. After that I clicked on the ABRT icon on the panel and found this Akregator crash notification in ABRT. Version-Release number of selected component: kdepim-4.11.3-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/bin/akregator --icon akregator -caption Akregator crash_function: WebCore::FrameLoader::loadResourceSynchronously(WebCore::ResourceRequest const&, WebCore::StoredCredentials, WebCore::ResourceError&, WebCore::ResourceResponse&, WTF::Vector<char, 0ul>&) executable: /usr/bin/akregator kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 WebCore::FrameLoader::loadResourceSynchronously(WebCore::ResourceRequest const&, WebCore::StoredCredentials, WebCore::ResourceError&, WebCore::ResourceResponse&, WTF::Vector<char, 0ul>&) at /lib64/libQtWebKit.so.4 #1 WebCore::DocumentThreadableLoader::loadRequest(WebCore::ResourceRequest const&, WebCore::SecurityCheckPolicy) at /lib64/libQtWebKit.so.4 #2 WebCore::DocumentThreadableLoader::DocumentThreadableLoader(WebCore::Document*, WebCore::ThreadableLoaderClient*, WebCore::DocumentThreadableLoader::BlockingBehavior, WebCore::ResourceRequest const&, WebCore::ThreadableLoaderOptions const&) at /lib64/libQtWebKit.so.4 #3 WebCore::DocumentThreadableLoader::loadResourceSynchronously(WebCore::Document*, WebCore::ResourceRequest const&, WebCore::ThreadableLoaderClient&, WebCore::ThreadableLoaderOptions const&) at /lib64/libQtWebKit.so.4 #4 WebCore::XMLHttpRequest::createRequest(int&) at /lib64/libQtWebKit.so.4 #5 WebCore::XMLHttpRequest::send(WTF::String const&, int&) at /lib64/libQtWebKit.so.4 #6 WebCore::XMLHttpRequest::send(int&) at /lib64/libQtWebKit.so.4 #7 WebCore::JSXMLHttpRequest::send(JSC::ExecState*) at /lib64/libQtWebKit.so.4 #8 WebCore::jsXMLHttpRequestPrototypeFunctionSend(JSC::ExecState*) at /lib64/libQtWebKit.so.4 #9 ??
Created attachment 840947 [details] File: backtrace
Created attachment 840948 [details] File: cgroup
Created attachment 840949 [details] File: core_backtrace
Created attachment 840950 [details] File: dso_list
Created attachment 840951 [details] File: environ
Created attachment 840952 [details] File: limits
Created attachment 840953 [details] File: maps
Created attachment 840954 [details] File: open_fds
Created attachment 840955 [details] File: proc_pid_status
Created attachment 840956 [details] File: var_log_messages
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.