Bug 1031224

Summary: [abrt] kde-workspace-4.10.5-3.fc18: KCrash::defaultCrashHandler: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Sullivan <davidsinaus>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dandreadante, dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, than, viktor.matveenko
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3150b86551566ffc55f20cbddb53e5f3473f3fd6
Whiteboard: abrt_hash:6343064aec0f05feb3fe0bb53b31c7201d26fa9c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:32:32 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description David Sullivan 2013-11-15 23:16:44 UTC
Version-Release number of selected component:
kde-workspace-4.10.5-3.fc18

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/plasma-desktop --nocrashhandler
crash_function: KCrash::defaultCrashHandler
executable:     /usr/bin/plasma-desktop
kernel:         3.11.7-100.fc18.x86_64
runlevel:       N 3
type:           CCpp
uid:            226

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler at /usr/src/debug/kdelibs-4.10.5/kdeui/util/kcrash.cpp:346
 #3 QMetaObject::addGuard at kernel/qobject.cpp:400
 #4 QPointer at ../../src/corelib/kernel/qpointer.h:62
 #5 takeAt at ../../src/corelib/tools/qlist.h:486
 #6 QDeclarativeRepeater::itemsRemoved at graphicsitems/qdeclarativerepeater.cpp:407
 #7 QMetaObject::activate at kernel/qobject.cpp:3547
 #8 QDeclarativeVisualModel::itemsRemoved at .moc/release-shared/moc_qdeclarativevisualitemmodel_p.cpp:160
 #9 QDeclarativeVisualDataModel::_q_itemsRemoved at graphicsitems/qdeclarativevisualitemmodel.cpp:1314
 #10 QDeclarativeVisualDataModel::qt_static_metacall at .moc/release-shared/moc_qdeclarativevisualitemmodel_p.cpp:400
 #11 QMetaObject::activate at kernel/qobject.cpp:3547

Potential duplicate: bug 951987

Comment 1 David Sullivan 2013-11-15 23:16:53 UTC
Created attachment 824733 [details]
File: backtrace

Comment 2 David Sullivan 2013-11-15 23:16:57 UTC
Created attachment 824734 [details]
File: cgroup

Comment 3 David Sullivan 2013-11-15 23:17:01 UTC
Created attachment 824735 [details]
File: core_backtrace

Comment 4 David Sullivan 2013-11-15 23:17:05 UTC
Created attachment 824736 [details]
File: dso_list

Comment 5 David Sullivan 2013-11-15 23:17:09 UTC
Created attachment 824737 [details]
File: environ

Comment 6 David Sullivan 2013-11-15 23:17:13 UTC
Created attachment 824738 [details]
File: exploitable

Comment 7 David Sullivan 2013-11-15 23:17:16 UTC
Created attachment 824739 [details]
File: limits

Comment 8 David Sullivan 2013-11-15 23:17:20 UTC
Created attachment 824740 [details]
File: maps

Comment 9 David Sullivan 2013-11-15 23:17:24 UTC
Created attachment 824741 [details]
File: open_fds

Comment 10 David Sullivan 2013-11-15 23:17:27 UTC
Created attachment 824742 [details]
File: proc_pid_status

Comment 11 David Sullivan 2013-11-15 23:17:30 UTC
Created attachment 824743 [details]
File: var_log_messages

Comment 12 David Sullivan 2013-11-15 23:26:57 UTC
System is a Dell Precision T7400 workstation running Fedora 18 x86_64.  Nvidia Quadro video w/latest binary driver (331.20).  Dell PERC 6i RAID controller.  Adaptec 39160 SCSI controller w/two LTO-3 tape drives.

System had been running fine under Fedora 17.  I recently upgraded to Fedora 18 using FedUp.  Crashes began a week or so after upgrading.  System was rock solid under F17.

Comment 13 Rex Dieter 2013-11-16 04:53:56 UTC
This is indeed a dup of bug #951987 , and a workaround was included in kde-4.11.3 per https://bugs.kde.org/show_bug.cgi?id=311871#c141

we could consider backporting it for f18/kde-4.10.x

Comment 14 Fedora End Of Life 2013-12-21 14:45:23 UTC
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.

Comment 15 Fedora End Of Life 2014-02-05 22:32:32 UTC
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.