Bug 1038282

Summary: [abrt] kde-baseapps-4.11.3-1.fc19: ref: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Phil V <pv.bugzilla>
Component: kwebkitpartAssignee: nucleo <alekcejk>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alekcejk, dvratil, jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/89480839a34d80f459ebadeb30c3871ee9eb1a27
Whiteboard: abrt_hash:b0ae1d01dc7ddac1acab5927f61033506b1a801a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:23:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Phil V 2013-12-04 19:35:37 UTC 
Description of problem:
when used as a browser, konqueror crashes frequently with no discernable pattern.

Version-Release number of selected component:
kde-baseapps-4.11.3-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        konqueror -mimetype text/html http://its.baylor.edu/index.php?id=43351
crash_function: ref
executable:     /usr/bin/konqueror
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ref at ../../src/corelib/arch/qatomic_x86_64.h:121
 #1 QtSharedPointer::ExternalRefCountData::getAndRef at tools/qsharedpointer.cpp:1257
 #2 QWeakPointer<QObject> at ../../src/corelib/tools/qsharedpointer_impl.h:595
 #3 operator=<QObject> at ../../src/corelib/tools/qsharedpointer_impl.h:600
 #4 QNetworkRequest::setOriginatingObject at access/qnetworkrequest.cpp:565
 #5 WebCore::ResourceRequest::toNetworkRequest at /lib64/libQtWebKit.so.4
 #6 WebCore::QNetworkReplyHandler::redirect at /lib64/libQtWebKit.so.4
 #7 WebCore::QNetworkReplyHandler::sendResponseIfNeeded at /lib64/libQtWebKit.so.4
 #8 flush at /lib64/libQtWebKit.so.4
 #9 WebCore::QNetworkReplyWrapper::receiveMetaData at /lib64/libQtWebKit.so.4
Comment 1 Phil V 2013-12-04 19:35:45 UTC 
Created attachment 832839 [details]
File: backtrace
Comment 2 Phil V 2013-12-04 19:35:49 UTC 
Created attachment 832840 [details]
File: cgroup
Comment 3 Phil V 2013-12-04 19:35:53 UTC 
Created attachment 832841 [details]
File: core_backtrace
Comment 4 Phil V 2013-12-04 19:35:56 UTC 
Created attachment 832842 [details]
File: dso_list
Comment 5 Phil V 2013-12-04 19:36:00 UTC 
Created attachment 832843 [details]
File: environ
Comment 6 Phil V 2013-12-04 19:36:03 UTC 
Created attachment 832844 [details]
File: limits
Comment 7 Phil V 2013-12-04 19:36:06 UTC 
Created attachment 832845 [details]
File: maps
Comment 8 Phil V 2013-12-04 19:36:12 UTC 
Created attachment 832846 [details]
File: open_fds
Comment 9 Phil V 2013-12-04 19:36:15 UTC 
Created attachment 832847 [details]
File: proc_pid_status
Comment 10 Phil V 2013-12-04 19:36:18 UTC 
Created attachment 832848 [details]
File: var_log_messages
Comment 11 Phil V 2013-12-04 19:58:07 UTC 
Note: The specific webpage that was loaded before the crash is no longer available.
Comment 12 Kevin Kofler 2013-12-04 22:08:48 UTC 
This crashes somewhere when QtWebKit tries to access QNetworkAccess. When using KWebKitPart, the QNetworkAccess implementation is provided by KWebKitPart (based on KIO), so that is my first suspect as to the culprit.
Comment 13 Phil V 2014-06-27 23:11:59 UTC 
Any hope for the future stability of konqueror ? 
It was / is a great application
Comment 14 Rex Dieter 2014-06-29 01:50:50 UTC 
Do you have a reproducible trigger?  If not, debugging this particular issue will be difficult.
Comment 15 Fedora End Of Life 2015-05-29 09:55:11 UTC 
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.
Comment 16 Fedora End Of Life 2015-06-29 13:23:48 UTC 
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.