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 1058804

Summary: [abrt] kdelibs: KCrash::defaultCrashHandler(int)(): kdeinit4 killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Martin <mholec>
Component: kde-plasma-networkmanagementAssignee: Jan Grulich <jgrulich>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: than, tpelka
Target Milestone: rc   
Target Release: 7.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2a0abcee2abca3124d8db544d71cf626ed34a298
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-11 14:49:42 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:
Bug Depends On:    
Bug Blocks: 916275    
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 Martin 2014-01-28 14:44:33 UTC
Version-Release number of selected component:
kdelibs-4.10.5-4.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        'kdeinit4: kded4 [kdeinit]' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
crash_function: KCrash::defaultCrashHandler(int)
executable:     /usr/bin/kdeinit4
kernel:         3.10.0-79.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler(int) at /lib64/libkdeui.so.5
 #3 WirelessNetworkInterfaceActivatableProvider::handleAdd(Knm::Connection*) at /lib64/libknmservice.so.4
 #4 ConnectionList::addConnection(Knm::Connection*) at /lib64/libknmservice.so.4
 #5 NMDBusSettingsConnectionProvider::initialiseAndRegisterRemoteConnection(QString const&) at /lib64/libknm_nm.so
 #6 NMDBusSettingsConnectionProvider::initConnections() at /lib64/libknm_nm.so
 #7 NMDBusSettingsConnectionProvider::serviceOwnerChanged(QString const&, QString const&, QString const&) at /lib64/libknm_nm.so
 #8 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) at /lib64/libQtCore.so.4
 #9 QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) at /lib64/libQtDBus.so.4
 #10 QDBusConnectionInterface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) at /lib64/libQtDBus.so.4
 #11 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) at /lib64/libQtCore.so.4

Comment 1 Martin 2014-01-28 14:44:38 UTC
Created attachment 856643 [details]
File: backtrace

Comment 2 Martin 2014-01-28 14:44:41 UTC
Created attachment 856644 [details]
File: cgroup

Comment 3 Martin 2014-01-28 14:44:44 UTC
Created attachment 856645 [details]
File: core_backtrace

Comment 4 Martin 2014-01-28 14:44:47 UTC
Created attachment 856646 [details]
File: dso_list

Comment 5 Martin 2014-01-28 14:44:50 UTC
Created attachment 856647 [details]
File: environ

Comment 6 Martin 2014-01-28 14:44:52 UTC
Created attachment 856648 [details]
File: limits

Comment 7 Martin 2014-01-28 14:44:54 UTC
Created attachment 856649 [details]
File: maps

Comment 8 Martin 2014-01-28 14:44:56 UTC
Created attachment 856650 [details]
File: open_fds

Comment 9 Martin 2014-01-28 14:45:03 UTC
Created attachment 856651 [details]
File: proc_pid_status

Comment 10 Martin 2014-01-28 14:45:05 UTC
Created attachment 856652 [details]
File: var_log_messages

Comment 11 Martin 2014-01-28 14:45:14 UTC
Created attachment 856653 [details]
File: sosreport.tar.xz

Comment 14 Jan Grulich 2014-01-29 16:44:45 UTC
This is probably related to #1058843. I think I was able to reproduce it only when NetworkManager crashed as first. Let's see whether this will be fixed after a new NetworkManager update.

Comment 15 Martin 2014-01-29 17:08:06 UTC
(In reply to Jan Grulich from comment #14)
> This is probably related to #1058843. I think I was able to reproduce it
> only when NetworkManager crashed as first. Let's see whether this will be
> fixed after a new NetworkManager update.

Yes, it's related, but NM crash shouldn't affect kdeinit4.

Comment 16 Jan Grulich 2014-02-11 14:49:42 UTC
It's not a bug in kde-plasma-networkmanagement and will be fixed in NetworkManager. Crash affects the applet (kdeinit4), because we get a wrong info from NetworkManager about non-existing device or active connection.