20110601 nm09 snapshot crashes

[Rex Dieter]

I'm seeing kded4 (and applet) crashes trying to use a recent nm09 snapshot
(against kde-4.6.3) on my fedora 15 box using
NetworkManager-0.8.9997-1.git20110531

(full backtrace appended).

what I find interesting/odd is the jump between:

#12 0x00007f711cf690f2 in NMNetworkManager::createNetworkInterface
(this=0x7fff91ec0f10, uni=...) at /usr/src/debug/kdebase-
workspace-4.6.3/solid/networkmanager-0.7/manager.cpp:116
#13 0x00007f711da51ceb in
Solid::Control::NetworkManagerNm09Private::networkInterfaces
(this=0x16c7400) at
/usr/src/debug/networkmanagement-0.9/solidcontrolfuture/libs/solid/control/networkmanager.cpp:109


Should solidcontrolfuture be linking the older solidcontrol at all (I guess
it's for the modemmanager pieces, but ... )?

-- Rex


Application: KDE Daemon (kded4), signal: Segmentation fault
[KCrash Handler]
#6 0x0000003f1732f420 in __memcpy_ssse3 () from /lib64/libc.so.6
#7 0x0000003f216b87bb in ?? () from /usr/lib64/libQtCore.so.4
#8 0x0000003f216b895d in QString::arg(QString const&, int, QChar const&)
const () from /usr/lib64/libQtCore.so.4
#9 0x0000003f2342e6a5 in ?? () from /usr/lib64/libQtDBus.so.4
#10 0x0000003f2343158c in
QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString
const&, char const*, QDBusConnection const&, QObject*) () from
/usr/lib64/libQtDBus.so.4
#11 0x00007f711cf77556 in
OrgFreedesktopNetworkManagerDeviceInterface::OrgFreedesktopNetworkManagerDeviceInterface
(this=0x7fff91ec0ea0, service=<optimized out>, path=<optimized out>,
connection=<optimized out>, parent=<optimized out>) at
/usr/src/debug/kdebase-workspace-4.6.3/solid/networkmanager-0.7/dbus/nm-
deviceinterface.cpp:19
#12 0x00007f711cf690f2 in NMNetworkManager::createNetworkInterface
(this=0x7fff91ec0f10, uni=...) at /usr/src/debug/kdebase-
workspace-4.6.3/solid/networkmanager-0.7/manager.cpp:116
#13 0x00007f711da51ceb in
Solid::Control::NetworkManagerNm09Private::networkInterfaces
(this=0x16c7400) at
/usr/src/debug/networkmanagement-0.9/solidcontrolfuture/libs/solid/control/networkmanager.cpp:109
#14 0x00007f711da51d7c in
Solid::Control::NetworkManagerNm09::networkInterfaces () at
/usr/src/debug/networkmanagement-0.9/solidcontrolfuture/libs/solid/control/networkmanager.cpp:119
#15 0x00007f711def33e4 in ConnectionUsageMonitor::ConnectionUsageMonitor
(this=0x16c6cb0, connectionList=<optimized out>, activatableList=0x16c6670,
parent=<optimized out>) at
/usr/src/debug/networkmanagement-0.9/libs/service/connectionusagemonitor.cpp:55
#16 0x00007f711e35482d in NetworkManagementService::NetworkManagementService
(this=0x16c5970, parent=<optimized out>) at
/usr/src/debug/networkmanagement-0.9/kded/service.cpp:90
#17 0x00007f711e354ac7 in
KPluginFactory::createInstance<NetworkManagementService, QObject>
(parentWidget=<optimized out>, parent=<optimized out>, args=...) at
/usr/include/kde4/kpluginfactory.h:473
#18 0x0000003f25820559 in KPluginFactory::create (this=0x169b310,
iface=0x3f2586f980 "KDEDModule", parentWidget=0x0, parent=0x14b2740,
args=..., keyword=<optimized out>) at
/usr/src/debug/kdelibs-4.6.3/kdecore/util/kpluginfactory.cpp:203
#19 0x0000003f23c090a4 in create<KDEDModule> (args=..., parent=0x14b2740,
this=<optimized out>) at
/usr/src/debug/kdelibs-4.6.3/kdecore/util/kpluginfactory.h:503
#20 Kded::loadModule (this=0x14b2740, s=..., onDemand=false) at
/usr/src/debug/kdelibs-4.6.3/kded/kded.cpp:410
#21 0x0000003f23c0a1e7 in Kded::initModules (this=0x14b2740) at
/usr/src/debug/kdelibs-4.6.3/kded/kded.cpp:269
#22 0x0000003f23c0c101 in newInstance (this=<optimized out>) at
/usr/src/debug/kdelibs-4.6.3/kded/kded.cpp:847
#23 KDEDApplication::newInstance (this=<optimized out>) at
/usr/src/debug/kdelibs-4.6.3/kded/kded.cpp:804
#24 0x0000003f27247bb2 in KUniqueApplicationAdaptor::newInstance
(this=0x1567eb0, asn_id=<optimized out>, args=...) at
/usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kuniqueapplication.cpp:436
#25 0x0000003f27247c52 in KUniqueApplicationAdaptor::qt_metacall
(this=0x1567eb0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff91ec1870)
at /usr/src/debug/kdelibs-4.6.3/x86_64-redhat-linux-
gnu/kdeui/kuniqueapplication_p.moc:81
#26 0x0000003f234205fb in ?? () from /usr/lib64/libQtDBus.so.4
#27 0x0000003f2342167d in ?? () from /usr/lib64/libQtDBus.so.4
#28 0x0000003f23422012 in ?? () from /usr/lib64/libQtDBus.so.4
#29 0x0000003f234220e8 in ?? () from /usr/lib64/libQtDBus.so.4
#30 0x0000003f21770aaa in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#31 0x0000003f241bb2b4 in QApplication::event(QEvent*) () from
/usr/lib64/libQtGui.so.4
#32 0x0000003f241b73e4 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib64/libQtGui.so.4
#33 0x0000003f241bc271 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#34 0x0000003f27241806 in KApplication::notify (this=0x7fff91ec25c0,
receiver=0x7fff91ec25c0, event=0x15594b0) at
/usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kapplication.cpp:311
#35 0x0000003f2175a1dc in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib64/libQtCore.so.4
#36 0x0000003f2175d7a4 in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
from /usr/lib64/libQtCore.so.4
#37 0x0000003f217848e3 in ?? () from /usr/lib64/libQtCore.so.4
#38 0x0000003f19242b6d in g_main_dispatch (context=0x14ba9b0) at
gmain.c:2440
#39 g_main_context_dispatch (context=0x14ba9b0) at gmain.c:3013
#40 0x0000003f19243348 in g_main_context_iterate (context=0x14ba9b0,
block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3091
#41 0x0000003f192435dc in g_main_context_iteration (context=0x14ba9b0,
may_block=1) at gmain.c:3154
#42 0x0000003f21784d3f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib64/libQtCore.so.4
#43 0x0000003f24259f3e in ?? () from /usr/lib64/libQtGui.so.4
#44 0x0000003f217596f2 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#45 0x0000003f217598ef in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#46 0x0000003f2175da37 in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#47 0x0000003f23c08a95 in kdemain (argc=1, argv=0x7fff91ec2998) at
/usr/src/debug/kdelibs-4.6.3/kded/kded.cpp:925
#48 0x0000003f1722143d in __libc_start_main () from /lib64/libc.so.6
#49 0x0000000000400741 in _start ()

[Lamarque Vieira Souza]

Post by Rex Dieter
I'm seeing kded4 (and applet) crashes trying to use a recent nm09 snapshot
(against kde-4.6.3) on my fedora 15 box using
NetworkManager-0.8.9997-1.git20110531
(full backtrace appended).
#12 0x00007f711cf690f2 in NMNetworkManager::createNetworkInterfaceof
(this=0x7fff91ec0f10, uni=...) at /usr/src/debug/kdebase-
workspace-4.6.3/solid/networkmanager-0.7/manager.cpp:116
#13 0x00007f711da51ceb in
Solid::Control::NetworkManagerNm09Private::networkInterfaces
(this=0x16c7400) at
/usr/src/debug/networkmanagement-0.9/solidcontrolfuture/libs/solid/control/
networkmanager.cpp:109
Should solidcontrolfuture be linking the older solidcontrol at all (I
guess it's for the modemmanager pieces, but ... )?

Yes, it should link because of ModemManager backend. But, of course, the
nm09 branch stuff should not use the old networkmanager-0.7 backend.

It seems for some reason your networkmanager-0.7 backend has higher
priority than the networkmanager-0.9 backend. You can change that in
systemsettings -> Infomation Source -> Network Manager Infrastructure (or
something like that, my desktop is not in English).

[Rex Dieter]

Post by Lamarque Vieira Souza
Yes, it should link because of ModemManager backend. But, of course, the
nm09 branch stuff should not use the old networkmanager-0.7 backend.
It seems for some reason your networkmanager-0.7 backend has higher
priority than the networkmanager-0.9 backend. You can change that in
systemsettings -> Infomation Source -> Network Manager Infrastructure
(or something like that, my desktop is not in English).

That was indeed that case, thanks!

-- Rex

[Rex Dieter]

Post by Rex Dieter

Post by Lamarque Vieira Souza
Yes, it should link because of ModemManager backend. But, of course, the
nm09 branch stuff should not use the old networkmanager-0.7 backend.
It seems for some reason your networkmanager-0.7 backend has higher
priority than the networkmanager-0.9 backend. You can change that in
systemsettings -> Infomation Source -> Network Manager Infrastructure
(or something like that, my desktop is not in English).

That was indeed that case, thanks!

With that in mind, wouldn't it be prudent, then, to bump the nm-0.9
provider's priority to be higher?

say, using something like the attached patch...

-- Rex


-------------- next part --------------
A non-text attachment was scrubbed...
Name: networkmanager-0.9-solid_networkmanager09_priority.patch
Type: text/x-patch
Size: 753 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-networkmanager/attachments/20110603/cd93e481/attachment.patch

[Lamarque Vieira Souza]

Post by Rex Dieter

Post by Rex Dieter

Post by Lamarque Vieira Souza
Yes, it should link because of ModemManager backend. But, of course, the
nm09 branch stuff should not use the old networkmanager-0.7 backend.
It seems for some reason your networkmanager-0.7 backend has higher
priority than the networkmanager-0.9 backend. You can change that in
systemsettings -> Infomation Source -> Network Manager Infrastructure
(or something like that, my desktop is not in English).

That was indeed that case, thanks!

With that in mind, wouldn't it be prudent, then, to bump the nm-0.9
provider's priority to be higher?
say, using something like the attached patch...
-- Rex

I already did that yesterday. Thanks for pointing the problem out.