knetworkmanager crashed with SIGSEGV in __dynamic_cast() after resume from suspend

[Vladimir Korenev]

Binary package hint: plasma-widget-networkmanagement

 Network manager crashed when waking up after suspend.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 5 01:11:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/knetworkmanager
NonfreeKernelModules: nvidia
Package: plasma-widget-networkmanagement 0.1~svn1017841-0ubuntu2
ProcCmdline: /usr/bin/knetworkmanager
ProcEnviron:
 PATH=(custom, user)
 LANG=ru_UA.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x7f04aacbf803 <__dynamic_cast+67>: mov -0x8(%rax),%rdi
 PC (0x7f04aacbf803) ok
 source "-0x8(%rax)" (0x730062002d0066) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plasma-widget-networkmanagement
StacktraceTop:
 __dynamic_cast () from /usr/lib/libstdc++.so.6
 NetworkInterfaceActivatableProvider::handleUpdate(Knm::Connection*) () from /usr/lib/libknmservice.so.4
 ConnectionList::updateConnection(Knm::Connection*)
 ConnectionUsageMonitor::handleActivationStateChange(Knm::InterfaceConnection::ActivationState) () from /usr/lib/libknmservice.so.4
 ConnectionUsageMonitor::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libknmservice.so.4
Title: knetworkmanager crashed with SIGSEGV in __dynamic_cast()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:__dynamic_cast (src_ptr=0x1770e00, src_type=0x7f04aca62000,
NetworkInterfaceActivatableProvider::handleUpdate (
ConnectionList::updateConnection (
ConnectionUsageMonitor::handleActivationStateChange (
ConnectionUsageMonitor::qt_metacall (this=0x16cc420,

[hasi (whynot-nurfuerspam)]

I see this on a Dell Latitude E6400, kubuntu karmic (32bit), with all updates applied as of today. This may be related to bug 420924 (crash/lockup after resume from suspend-to-ram, can be prevented by switching compositing off). This bug appeared with alpha5. Knetworkmanager can be restarted after the crash and works then fine.

[Jonathan Thomas (echidnaman)]

Fix committed in upstream svn. The fix will be released next time we update the svn snapshot.

[Jithin Emmanuel (jithin1987)]

Hi. Can some one please provide an updated package, now that fix has been committed.

[Jonathan Thomas (echidnaman)]

Fix released to Karmic.

[Bernie Bernstein (bernie9998)]

Any plans on releasing this fix into the jaunty backports ppa (found at http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu)?

If it had been released, I am still experiencing the same issues and am currently up to date on updates.

[Jonathan Thomas (echidnaman)]

Yeah, but the build failed. Somebody'll have to look in to fixing it.

[Treris (treris)]

All I can add is that I still have this problem in Jaunty and I am up to date on updates from the kubuntu-ppa backports.

Upon restart knetworkmanager works like a charm.

[avlas (avlas)]

Jaunty is still the stable release, is it not worth to fix this problem in it?

[Andreas Wenning (andreas-wenning)]

Well, this problem is not present in official jaunty (as knetworkmanager is not part of jaunty at all). It does only exist for jaunty in a PPA...