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 1091985

Summary: [abrt] kdelibs: type(): kdeinit4 killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Dolezal <todoleza>
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:6b45db73da9f903fe5f85aac82b5524f0627b399
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-15 14:33: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 Tomas Dolezal 2014-04-28 12:45:24 UTC 
Version-Release number of selected component:
kdelibs-4.10.5-6.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        'kdeinit4: konqueror [kdeinit] http://hostcode' '' ''
crash_function: type
executable:     /usr/bin/kdeinit4
kernel:         3.10.0-121.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            19436

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 type at /usr/src/debug/kdelibs-4.10.5/kjs/value.h:452
 #1 KJS::cloneInternal at /usr/src/debug/kdelibs-4.10.5/khtml/ecma/kjs_data.cpp:37
 #2 KJS::encapsulateMessageEventData at /usr/src/debug/kdelibs-4.10.5/khtml/ecma/kjs_data.cpp:117
 #3 KJS::DelayedPostMessage::execute at /usr/src/debug/kdelibs-4.10.5/khtml/ecma/kjs_data.cpp:169
 #4 KJS::Window::afterScriptExecution at /usr/src/debug/kdelibs-4.10.5/khtml/ecma/kjs_window.cpp:1337
 #5 KJS::JSEventListener::handleEvent at /usr/src/debug/kdelibs-4.10.5/khtml/ecma/kjs_events.cpp:121
 #6 DOM::EventTargetImpl::handleLocalEvents at /usr/src/debug/kdelibs-4.10.5/khtml/xml/dom2_eventsimpl.cpp:62
 #7 DOM::NodeImpl::dispatchGenericEvent at /usr/src/debug/kdelibs-4.10.5/khtml/xml/dom_nodeimpl.cpp:469
 #8 DOM::NodeImpl::dispatchWindowEvent at /usr/src/debug/kdelibs-4.10.5/khtml/xml/dom_nodeimpl.cpp:542
 #10 KHTMLPart::closeUrl at /usr/src/debug/kdelibs-4.10.5/khtml/khtml_part.cpp:928
Comment 1 Tomas Dolezal 2014-04-28 12:45:27 UTC 
Created attachment 890457 [details]
File: backtrace
Comment 2 Tomas Dolezal 2014-04-28 12:45:29 UTC 
Created attachment 890458 [details]
File: cgroup
Comment 3 Tomas Dolezal 2014-04-28 12:45:31 UTC 
Created attachment 890459 [details]
File: core_backtrace
Comment 4 Tomas Dolezal 2014-04-28 12:45:34 UTC 
Created attachment 890460 [details]
File: dso_list
Comment 5 Tomas Dolezal 2014-04-28 12:45:36 UTC 
Created attachment 890461 [details]
File: environ
Comment 6 Tomas Dolezal 2014-04-28 12:45:38 UTC 
Created attachment 890462 [details]
File: limits
Comment 7 Tomas Dolezal 2014-04-28 12:45:40 UTC 
Created attachment 890463 [details]
File: maps
Comment 8 Tomas Dolezal 2014-04-28 12:45:42 UTC 
Created attachment 890464 [details]
File: open_fds
Comment 9 Tomas Dolezal 2014-04-28 12:45:46 UTC 
Created attachment 890465 [details]
File: proc_pid_status
Comment 10 Tomas Dolezal 2014-04-28 12:45:48 UTC 
Created attachment 890466 [details]
File: var_log_messages
Comment 11 Tomas Dolezal 2014-04-28 12:46:30 UTC 
Created attachment 890467 [details]
File: sosreport.tar.xz
Comment 13 Than Ngo 2014-04-28 13:49:25 UTC 
could you please provide a testcase to reproduce this issue?

thanks
Comment 14 Tomas Dolezal 2014-04-30 11:46:50 UTC 
Hello Ngo,
unfortunately I don't know how this have happened. It was probably when I started the KDE for the first time. It was freshly installed to my system after using Gnome, probably something was missing and now it is not.
Comment 15 Tomas Dolezal 2014-04-30 11:50:28 UTC 
Also, gnome-abrt now states under the problem that:
>The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit this problem. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly.

After reading it I don't understand why it was reported by abrt in the first place. Regardless if the report is found to be somewhat sufficient it shouldn't be closed immediately.
Comment 16 Than Ngo 2014-07-15 14:33:00 UTC 
feel free to reopen it again when you have a testcase to reproduce this issue.
thank!