Bug 1034423 - [abrt] kde-baseapps-4.11.3-1.fc19: Process /usr/bin/konqueror was killed by signal 11 (SIGSEGV)
Summary: [abrt] kde-baseapps-4.11.3-1.fc19: Process /usr/bin/konqueror was killed by s...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: qtwebkit
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:c16b48ed9bd433ecf5175bb3547...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 19:41 UTC by Phil V
Modified: 2015-02-17 19:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:23:56 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (147.52 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: cgroup (141 bytes, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: core_backtrace (106.86 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: dso_list (29.26 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: environ (2.06 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: limits (1.29 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: maps (182.50 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: open_fds (1.99 KB, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: proc_pid_status (944 bytes, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details
File: var_log_messages (588 bytes, text/plain)
2013-11-25 19:42 UTC, Phil V
no flags Details

Description Phil V 2013-11-25 19:41:55 UTC
Description of problem:
konqueror fails regularly without any evident pattern.
It might have to do with more media-intensive webpages like news sites but I am not sure. 
Typically this happens when I have opened a half dozen tabs or more, but this may be just statistical correlation not causation.

Many times the abrt problem description is 

"File Manager - Super User Mode crashed
Process /usr/bin/konqueror was killed by signal 11

I have been getting these crashes ever since i installed Fedora 19 kde, and despite all updates.

I have removed my .kde directory to see if there was a configuration problem but the problem continues.

I've loved using konqueror in the past and hope it can return to stabile reliability. 

Let me know how I can help.

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

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/konqueror --silent
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 ??
 #1 QMetaObject::cast at kernel/qmetaobject.cpp:274
 #2 WebCore::FrameNetworkingContextQt::networkAccessManager at /lib64/libQtWebKit.so.4
 #3 WebCore::thirdPartyCookiePolicyPermits at /lib64/libQtWebKit.so.4
 #4 WebCore::ResourceRequest::toNetworkRequest at /lib64/libQtWebKit.so.4
 #5 WebCore::QNetworkReplyHandler::redirect at /lib64/libQtWebKit.so.4
 #6 WebCore::QNetworkReplyHandler::sendResponseIfNeeded at /lib64/libQtWebKit.so.4
 #7 flush at /lib64/libQtWebKit.so.4
 #8 WebCore::QNetworkReplyWrapper::receiveMetaData at /lib64/libQtWebKit.so.4
 #9 QMetaObject::activate at kernel/qobject.cpp:3547

Comment 1 Phil V 2013-11-25 19:42:04 UTC
Created attachment 828831 [details]
File: backtrace

Comment 2 Phil V 2013-11-25 19:42:07 UTC
Created attachment 828832 [details]
File: cgroup

Comment 3 Phil V 2013-11-25 19:42:12 UTC
Created attachment 828833 [details]
File: core_backtrace

Comment 4 Phil V 2013-11-25 19:42:21 UTC
Created attachment 828834 [details]
File: dso_list

Comment 5 Phil V 2013-11-25 19:42:25 UTC
Created attachment 828835 [details]
File: environ

Comment 6 Phil V 2013-11-25 19:42:28 UTC
Created attachment 828836 [details]
File: limits

Comment 7 Phil V 2013-11-25 19:42:32 UTC
Created attachment 828837 [details]
File: maps

Comment 8 Phil V 2013-11-25 19:42:37 UTC
Created attachment 828838 [details]
File: open_fds

Comment 9 Phil V 2013-11-25 19:42:42 UTC
Created attachment 828839 [details]
File: proc_pid_status

Comment 10 Phil V 2013-11-25 19:42:46 UTC
Created attachment 828840 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-01-09 20:41:38 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 12 Fedora End Of Life 2015-02-17 19:23:56 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


Note You need to log in before you can comment on or make changes to this bug.