Bug 209834

Summary:	crash in handleUpdate method after wakeup out of hibernation
Product:	[Unmaintained] knetworkmanager	Reporter:	Michael Krüger <info>
Component:	general	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, kde, rjohnson
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michael Krüger 2009-10-08 06:40:03 UTC

Version:           Not sure - Version that comes with kubuntu KDE 4.3.2 (using KDE 4.3.1)
OS:                Linux
Installed from:    Ubuntu Packages

There are similar bugs reported for 4.3.1 and it is claimed that this one is fixed, but yesterday I installed the latest release 4.3.2 Kubuntu packages and the problem is still there:
Application: KNetworkManager (knetworkmanager), signal: Segmentation fault
[KCrash Handler]
#6  0xb6c0930b in __dynamic_cast () from /usr/lib/libstdc++.so.6
#7  0xb79258f1 in NetworkInterfaceActivatableProvider::handleUpdate () from /usr/lib/libknmservice.so.4
#8  0xb791e65c in ConnectionList::updateConnection () from /usr/lib/libknmservice.so.4
#9  0xb792eec6 in ConnectionUsageMonitor::handleActivationStateChange () from /usr/lib/libknmservice.so.4
#10 0xb791d1c1 in ConnectionUsageMonitor::qt_metacall () from /usr/lib/libknmservice.so.4
#11 0xb6d981b8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb6d98e42 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb794f9d3 in Knm::InterfaceConnection::activationStateChanged () from /usr/lib/libknminternals.so.4
#14 0xb79685ec in Knm::InterfaceConnection::setActivationState () from /usr/lib/libknminternals.so.4
#15 0xb790278c in NMDBusActiveConnectionMonitor::activeConnectionChangedInternal () from /usr/lib/libknm_nm.so
#16 0xb7902a3b in NMDBusActiveConnectionMonitor::activeConnectionChanged () from /usr/lib/libknm_nm.so
#17 0xb78ccdd2 in NMDBusActiveConnectionMonitor::qt_metacall () from /usr/lib/libknm_nm.so
#18 0xb6d981b8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb6d98e42 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0xb78cc7f3 in ?? () from /usr/lib/libknm_nm.so
#21 0xb78cd626 in ?? () from /usr/lib/libknm_nm.so
#22 0xb6e99e5a in ?? () from /usr/lib/libQtDBus.so.4
#23 0xb6ea1eb7 in ?? () from /usr/lib/libQtDBus.so.4
#24 0xb6d933b0 in QObject::event () from /usr/lib/libQtCore.so.4
#25 0xb700ed3c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#26 0xb701703e in QApplication::notify () from /usr/lib/libQtGui.so.4
#27 0xb7b5349d in KApplication::notify () from /usr/lib/libkdeui.so.5
#28 0xb6d82bcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#29 0xb6d83825 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#30 0xb6d83a1d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#31 0xb6dae6af in ?? () from /usr/lib/libQtCore.so.4
#32 0xb640cb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#33 0xb64100eb in ?? () from /usr/lib/libglib-2.0.so.0
#34 0xb6410268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#35 0xb6dae2f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#36 0xb70b0a75 in ?? () from /usr/lib/libQtGui.so.4
#37 0xb6d811fa in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#38 0xb6d81642 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#39 0xb6d83ae9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#40 0xb700ebb7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#41 0x080526f3 in _start ()

Comment 1 Dario Andres 2009-10-08 23:30:41 UTC

Fixed recently. Thanks

*** This bug has been marked as a duplicate of bug 205955 ***

Comment 2 Will Stephenson 2009-10-12 16:41:27 UTC

This bug has been fixed for over a month; Kubuntu have been told several times that they need to update their packages; they say they have done so, but for some reason they are still being installed.  Please take this to Kubuntu.

Comment 3 Scott Kitterman 2009-10-12 19:35:16 UTC

I'm unable to reproduce this on Kubuntu Karmic.  Currently we have 0.9~svn1029786.  Since, according to the parent bug this was fixed in 1021166, either the reporter's packages are not up to date or it's a different issue.

Comment 4 Rich Johnson 2009-10-12 19:36:05 UTC

Will, this has been fixed in Karmic. The problem he is seeing might be due to the backend being the version from jaunty and not karmic. In karmic this issue has been fixed since you told us to update a month ago.