Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1136967

Summary: [abrt] kdelibs: KCrash::defaultCrashHandler(int)(): kdeinit4 killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Jeff Bastian <jbastian>
Component: kdelibsAssignee: Than Ngo <than>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:bc8cf7107130291b3bccbe128b95b08afc7f28b1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-11 14:38:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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
File: sosreport.tar.xz none

Description Jeff Bastian 2014-09-03 17:06:20 UTC
Description of problem:
I'm not sure what happened.  I was just going about my work when KDE flickered and some process(es) restarted and everything went back to normal.

Version-Release number of selected component:
kdelibs-4.10.5-6.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        'kdeinit4: plasma-desktop [kdeinit]' '' '' '' '' '' '' '' '' '' '' '' '' ''
crash_function: KCrash::defaultCrashHandler(int)
executable:     /usr/bin/kdeinit4
kernel:         3.10.0-123.6.3.el7.x86_64
runlevel:       unknown
type:           CCpp
uid:            12257

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler(int) at /lib64/libkdeui.so.5
 #3 QMetaObject::addGuard(QObject**) at /lib64/libQtCore.so.4
 #4 QDeclarativeRepeater::itemsRemoved(int, int) at /lib64/libQtDeclarative.so.4
 #5 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) at /lib64/libQtCore.so.4
 #6 QDeclarativeVisualModel::itemsRemoved(int, int) at /lib64/libQtDeclarative.so.4
 #7 QDeclarativeVisualDataModel::_q_itemsRemoved(int, int) at /lib64/libQtDeclarative.so.4
 #8 QDeclarativeVisualDataModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) at /lib64/libQtDeclarative.so.4
 #9 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) at /lib64/libQtCore.so.4
 #10 QListModelInterface::itemsRemoved(int, int) at /lib64/libQtDeclarative.so.4
 #11 QDeclarativeListModel::remove(int) at /lib64/libQtDeclarative.so.4

Comment 1 Jeff Bastian 2014-09-03 17:06:21 UTC
Created attachment 934168 [details]
File: backtrace

Comment 2 Jeff Bastian 2014-09-03 17:06:22 UTC
Created attachment 934169 [details]
File: cgroup

Comment 3 Jeff Bastian 2014-09-03 17:06:23 UTC
Created attachment 934170 [details]
File: core_backtrace

Comment 4 Jeff Bastian 2014-09-03 17:06:24 UTC
Created attachment 934171 [details]
File: dso_list

Comment 5 Jeff Bastian 2014-09-03 17:06:25 UTC
Created attachment 934172 [details]
File: environ

Comment 6 Jeff Bastian 2014-09-03 17:06:25 UTC
Created attachment 934173 [details]
File: limits

Comment 7 Jeff Bastian 2014-09-03 17:06:27 UTC
Created attachment 934174 [details]
File: maps

Comment 8 Jeff Bastian 2014-09-03 17:06:28 UTC
Created attachment 934175 [details]
File: open_fds

Comment 9 Jeff Bastian 2014-09-03 17:06:29 UTC
Created attachment 934176 [details]
File: proc_pid_status

Comment 10 Jeff Bastian 2014-09-03 17:06:29 UTC
Created attachment 934177 [details]
File: var_log_messages

Comment 11 Jeff Bastian 2014-09-03 17:07:24 UTC
Created attachment 934178 [details]
File: sosreport.tar.xz

Comment 13 Than Ngo 2014-09-11 13:45:02 UTC
could you please add a testcase how to reprpduce this issue?

thanks

Comment 14 Jeff Bastian 2014-09-11 14:21:48 UTC
I'm not really sure what happened so I don't know how to reproduce it.  It's possible it was a one time fluke.  Feel free to close the bug for now as INSUFFICIENT_DATA and at least the abrt hash will be in bugzilla in case it ever happens again.

Comment 15 Than Ngo 2014-09-11 14:38:00 UTC
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.

thanks