| Summary: | Network-Manager crashes in loop when enabled IPv6 | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | Arthur Brownlee IV <a.e.brownlee.iv> |
| Component: | KDED Module | Assignee: | Lamarque V. Souza <lamarque> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 0.9 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Arthur Brownlee IV
2013-03-13 02:30:22 UTC
Which Plasma NM version do you use? You can see the version string in "Manage Connections" -> "Other". This crashlog does not give much information. Can you install the package containing the debug symbols and reproduce the problem? Version 0.9.0.7 (nm09 20130127) I'll install the debug symbols and crash it again. The interesting thing to note was that when I was running KDE installed from Ubuntu 13.04, I never had this issue. However when doing a clean wipe and re-install using Kubuntu 13.04 Alpha 2, this issue arose. Application: KDE Daemon (kdeinit4), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59b44c97c0 (LWP 1813))] Thread 5 (Thread 0x7f599481d700 (LWP 1822)): #0 0x00007fffbf365af7 in ?? () #1 0x000000000126cd80 in ?? () #2 0x00000002bf2a07a0 in ?? () #3 0x00007f5990002860 in ?? () #4 0x00007f599481cbb0 in ?? () #5 0x00007f599481cc68 in ?? () #6 0x0000000000000000 in ?? () Thread 4 (Thread 0x7f598ffff700 (LWP 1827)): #0 0x00007fffbf365af7 in ?? () #1 0x0000000000000000 in ?? () Thread 3 (Thread 0x7f597f9e0700 (LWP 1840)): #0 0x00007f59af550075 in __GI___pthread_mutex_lock (mutex=0x7f5974000a60) at pthread_mutex_lock.c:95 #1 0x00007f59aeeb8881 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f59aee79270 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f59b3163026 in QEventDispatcherGlib::processEvents (this=0x7f59740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f59b313337f in QEventLoop::processEvents (this=this@entry=0x7f597f9dfd80, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f59b3133608 in QEventLoop::exec (this=0x7f597f9dfd80, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f59b3035410 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #7 0x00007f5996c126e5 in KCupsConnection::run() () from /usr/lib/libkcupslib.so #8 0x00007f59b3037bec in QThreadPrivate::start (arg=0x1274b50) at thread/qthread_unix.cpp:338 #9 0x00007f59af54df8e in start_thread (arg=0x7f597f9e0700) at pthread_create.c:311 #10 0x00007f59b1d3de1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f597f1df700 (LWP 1841)): #0 0x00007fffbf365af7 in ?? () #1 0x0000000001228fb0 in ?? () #2 0x00000002bf2a07a0 in ?? () #3 0x00007f596c002860 in ?? () #4 0x00007f597f1debb0 in ?? () #5 0x00007f597f1dec68 in ?? () #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f59b44c97c0 (LWP 1813)): [KCrash Handler] #6 0x00007f598d0f8612 in WirelessNetworkInterfaceActivatableProvider::handleAdd(Knm::Connection*) () from /usr/lib/libknmservice.so.4 #7 0x00007f598d0e77dc in ConnectionList::addConnection(Knm::Connection*) () from /usr/lib/libknmservice.so.4 #8 0x00007f598cea3e53 in NMDBusSettingsConnectionProvider::initialiseAndRegisterRemoteConnection(QString const&) () from /usr/lib/libknm_nm.so #9 0x00007f598cea3790 in NMDBusSettingsConnectionProvider::initConnections() () from /usr/lib/libknm_nm.so #10 0x00007f598cea458b in NMDBusSettingsConnectionProvider::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libknm_nm.so #11 0x00007f598ce75451 in NMDBusSettingsConnectionProvider::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libknm_nm.so #12 0x00007f59b31490df in QMetaObject::activate (sender=0x1220f00, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffbf29f5f0) at kernel/qobject.cpp:3539 #13 0x00007f59b053243f in QDBusConnectionInterface::serviceOwnerChanged (this=<optimized out>, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:224 #14 0x00007f59b0532671 in QDBusConnectionInterface::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7fffbf29f870) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:114 #15 0x00007f59b31490df in QMetaObject::activate (sender=0x1220f00, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffbf29f870) at kernel/qobject.cpp:3539 #16 0x00007f59b053250f in QDBusConnectionInterface::NameOwnerChanged (this=<optimized out>, _t1=..., _t2=..., _t3=...) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:252 #17 0x00007f59b05326d1 in QDBusConnectionInterface::qt_static_metacall (_o=_o@entry=0x1220f00, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=6, _a=_a@entry=0x7fffbf29fba0) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:118 #18 0x00007f59b0532eaf in QDBusConnectionInterface::qt_metacall (this=0x1220f00, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffbf29fba0) at .moc/release-shared/moc_qdbusconnectioninterface.cpp:177 #19 0x00007f59b04f7063 in QDBusConnectionPrivate::deliverCall (this=0x1221c40, object=0x1220f00, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:951 #20 0x00007f59b314e5ae in QObject::event (this=0x1220f00, e=<optimized out>) at kernel/qobject.cpp:1194 #21 0x00007f59b24da8ec in QApplicationPrivate::notify_helper (this=this@entry=0x1066430, receiver=receiver@entry=0x1220f00, e=e@entry=0x1138610) at kernel/qapplication.cpp:4567 #22 0x00007f59b24dd25b in QApplication::notify (this=0x7fffbf2a07a0, receiver=0x1220f00, e=0x1138610) at kernel/qapplication.cpp:4428 #23 0x00007f59b3eb7af6 in KApplication::notify (this=0x7fffbf2a07a0, receiver=0x1220f00, event=0x1138610) at ../../kdeui/kernel/kapplication.cpp:311 #24 0x00007f59b313462e in QCoreApplication::notifyInternal (this=0x7fffbf2a07a0, receiver=receiver@entry=0x1220f00, event=event@entry=0x1138610) at kernel/qcoreapplication.cpp:946 #25 0x00007f59b3138161 in sendEvent (event=0x1138610, receiver=0x1220f00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xfd1150) at kernel/qcoreapplication.cpp:1570 #27 0x00007f59b3162e73 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #28 postEventSourceDispatch (s=0x1064a00) at kernel/qeventdispatcher_glib.cpp:279 #29 0x00007f59aee78e85 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x00007f59aee791c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x00007f59aee79284 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x00007f59b3163006 in QEventDispatcherGlib::processEvents (this=0xfd3670, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #33 0x00007f59b25801ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #34 0x00007f59b313337f in QEventLoop::processEvents (this=this@entry=0x7fffbf2a0520, flags=...) at kernel/qeventloop.cpp:149 #35 0x00007f59b3133608 in QEventLoop::exec (this=0x7fffbf2a0520, flags=...) at kernel/qeventloop.cpp:204 #36 0x00007f59b3138ce6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #37 0x00007f599f058050 in kdemain (argc=1, argv=0x1049130) at ../../kded/kded.cpp:924 #38 0x00000000004084ea in launch (argc=argc@entry=1, _name=_name@entry=0x40b167 "kded4", args=args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=reset_env@entry=false, tty=tty@entry=0x0, avoid_loops=avoid_loops@entry=false, startup_id_str=startup_id_str@entry=0x40aff6 "0") at ../../kinit/kinit.cpp:738 #39 0x0000000000405b69 in main (argc=4, argv=<optimized out>, envp=0x7fffbf2a11a0) at ../../kinit/kinit.cpp:1853 Also adding possible relevant dmesg: [ 944.524745] wlan1: authenticate with 0e:27:22:d5:XX:XX [ 944.533533] wlan1: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded [ 944.540114] wlan1: send auth to 0e:27:22:d5:XX:XX (try 1/3) [ 944.543479] wlan1: authenticated [ 944.544998] wlan1: associate with 0e:27:22:d5:XX:XX (try 1/3) [ 944.549096] wlan1: RX AssocResp from 0e:27:22:d5:XX:XX (capab=0x431 status=0 aid=3) [ 944.549189] wlan1: associated [ 944.805483] NetworkManager[4194]: segfault at 8 ip 0000000000483549 sp 00007fffa65b2850 error 4 in NetworkManager[400000+fa000] [ 945.042728] init: network-manager main process (4194) killed by SEGV signal [ 945.042772] init: network-manager main process ended, respawning [ 945.533629] wlan1: deauthenticating from 0e:27:22:d5:XX:XX by local choice (reason=3) [ 945.560337] cfg80211: Calling CRDA to update world regulatory domain [ 945.566920] cfg80211: World regulatory domain updated: [ 945.566926] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 945.566930] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 945.566933] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 945.566936] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 945.566939] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 945.566943] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > #6 0x00007f598d0f8612 in WirelessNetworkInterfaceActivatableProvider::handleAdd(Knm::Connection*) () from /usr/lib/libknmservice.so.4
# apt-get install plasma-widget-networkmanagement-dbg
That is actually with the debugging package installed: Package: plasma-widget-networkmanagement-dbg Status: install ok installed Priority: extra Section: debug Installed-Size: 1742 Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com> Architecture: amd64 Source: networkmanagement Version: 0.9.0.7-0ubuntu1 Depends: plasma-widget-networkmanagement (= 0.9.0.7-0ubuntu1) Recommends: kdelibs5-dbg Suggests: kde-workspace-dbg Description: debugging symbols for KDE Network Management This package provides debugging symbols for all binary packages built from the plasma-widget-networkmanagement source package. It's highly recommended to have this package installed before reporting any crashes. Original-Maintainer: Debian KDE Extras Team <pkg-kde-extras@lists.alioth.debian.org> (In reply to comment #3) > [ 944.805483] NetworkManager[4194]: segfault at 8 ip 0000000000483549 sp > 00007fffa65b2850 error 4 in NetworkManager[400000+fa000] > [ 945.042728] init: network-manager main process (4194) killed by SEGV > signal > [ 945.042772] init: network-manager main process ended, respawning That is probably what caused the crash. Plasma NM caches some pointers which becomes stale when NetworkManager crashes. I plan to fix that when I have more time since the changes required to do that are quite extense. Until there the workaround is making sure NetworkManager does not crash :-P *** This bug has been marked as a duplicate of bug 314200 *** (In reply to comment #6) > That is probably what caused the crash. Plasma NM caches some pointers which > becomes stale when NetworkManager crashes. I plan to fix that when I have > more time since the changes required to do that are quite extense. Until > there the workaround is making sure NetworkManager does not crash :-P > > *** This bug has been marked as a duplicate of bug 314200 *** So with enabling IPv6 DHCP Client, should I take that bug up with the Network-Manager team in the meantime? I'm just a bit confused as to why I didn't have the issue when I installed KDE from packages on Ubuntu 13.04, but now have the issue on Kubuntu 13.04. The Network-Manager version is the same between the two. Thank you for your time! (In reply to comment #7) > So with enabling IPv6 DHCP Client, should I take that bug up with the > Network-Manager team in the meantime? I'm just a bit confused as to why I > didn't have the issue when I installed KDE from packages on Ubuntu 13.04, > but now have the issue on Kubuntu 13.04. The Network-Manager version is the > same between the two. If you can consistently reproduce this NetworkManager crash then yes, you should contact the NetworkManager team about it. Which NetworkManager version do you use? Maybe there is an update to fix this crash. > Thank you for your time! You are welcome. (In reply to comment #8) > If you can consistently reproduce this NetworkManager crash then yes, you > should contact the NetworkManager team about it. Which NetworkManager > version do you use? Maybe there is an update to fix this crash. Architecture: amd64 Version: 0.9.8.0-0ubuntu1 I believe this is the newest version from what I've been able to tell, although at one point I did recall seeing a 0.9.8.0-0ubuntu2 somewhere. |