Bug 257216 - KDE Daemon (kded4), signal: Segmentation fault [KCrash Handler] - Network Manager
Summary: KDE Daemon (kded4), signal: Segmentation fault [KCrash Handler] - Network Man...
Status: RESOLVED DUPLICATE of bug 254120
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-18 07:12 UTC by dev2000bugs
Modified: 2010-11-18 08:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dev2000bugs 2010-11-18 07:12:54 UTC
Application: kded4 ($Id: kded.cpp 1156841 2010-07-29 19:59:05Z zander $)
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.35.6-48.fc14.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Browsing the Web.  3G Mobile Broadband Modem underwent disconnection/reconnection process at time of crash.

-- Backtrace:
Application: KDE Daemon (kded4), signal: Segmentation fault
[KCrash Handler]
#7  0x071480f6 in isSignalConnected (sender=0x9729920, m=0x562f6e4, local_signal_index=1, argv=0x0) at kernel/qobject_p.h:220
#8  QMetaObject::activate (sender=0x9729920, m=0x562f6e4, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3195
#9  0x056045b8 in Knm::Activatable::changed (this=0x9729920) at /usr/src/debug/networkmanagement-0.9/i686-redhat-linux-gnu/libs/internals/moc_activatable.cpp:124
#10 0x0561b24e in Knm::InterfaceConnection::setActivationState (this=0x9729920, state=Knm::InterfaceConnection::Unknown) at /usr/src/debug/networkmanagement-0.9/libs/internals/interfaceconnection.cpp:82
#11 0x018ab729 in NMDBusActiveConnectionProxy::~NMDBusActiveConnectionProxy (this=0x96d2ac0, __in_chrg=<value optimized out>) at /usr/src/debug/networkmanagement-0.9/backends/NetworkManager/nmdbusactiveconnectionmonitor.cpp:58
#12 0x018ab773 in NMDBusActiveConnectionProxy::~NMDBusActiveConnectionProxy (this=0x96d2ac0, __in_chrg=<value optimized out>) at /usr/src/debug/networkmanagement-0.9/backends/NetworkManager/nmdbusactiveconnectionmonitor.cpp:60
#13 0x018ace1d in NMDBusActiveConnectionMonitor::activeConnectionListChanged (this=0x9679b78) at /usr/src/debug/networkmanagement-0.9/backends/NetworkManager/nmdbusactiveconnectionmonitor.cpp:163
#14 0x0187f6b2 in NMDBusActiveConnectionMonitor::qt_metacall (this=0x9679b78, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa74f3c) at /usr/src/debug/networkmanagement-0.9/i686-redhat-linux-gnu/backends/NetworkManager/moc_nmdbusactiveconnectionmonitor.cpp:77
#15 0x07138e3b in QMetaObject::metacall (object=0x9679b78, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbfa74f3c) at kernel/qmetaobject.cpp:237
#16 0x07148327 in QMetaObject::activate (sender=0x967a3b0, m=0x6d22040, local_signal_index=6, argv=0x0) at kernel/qobject.cpp:3272
#17 0x06d01888 in Solid::Control::NetworkManager::Notifier::activeConnectionsChanged (this=0x967a3b0) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/libs/solid/control/networkmanager.moc:144
#18 0x06d018f3 in Solid::Control::NetworkManager::Notifier::qt_metacall (this=0x967a3b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa7508c) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/libs/solid/control/networkmanager.moc:91
#19 0x06d01d9b in Solid::Control::NetworkManagerPrivate::qt_metacall (this=0x967a3b0, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfa7508c) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/libs/solid/control/networkmanager_p.moc:76
#20 0x07138e3b in QMetaObject::metacall (object=0x967a3b0, cl=QMetaObject::InvokeMetaMethod, idx=10, argv=0xbfa7508c) at kernel/qmetaobject.cpp:237
#21 0x07148327 in QMetaObject::activate (sender=0x967af78, m=0xfe8bf0, local_signal_index=6, argv=0x0) at kernel/qobject.cpp:3272
#22 0x00fe4188 in Solid::Control::Ifaces::NetworkManager::activeConnectionsChanged (this=0x967af78) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/libs/solid/control/ifaces/networkmanager.moc:152
#23 0x0103f96d in NMNetworkManager::propertiesChanged (this=0x967af78, properties=...) at /usr/src/debug/kdebase-workspace-4.5.3/solid/networkmanager-0.7/manager.cpp:264
#24 0x0104055d in NMNetworkManager::qt_metacall (this=0x967af78, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa75328) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/solid/networkmanager-0.7/manager.moc:98
#25 0x07138e3b in QMetaObject::metacall (object=0x967af78, cl=QMetaObject::InvokeMetaMethod, idx=19, argv=0xbfa75328) at kernel/qmetaobject.cpp:237
#26 0x07148327 in QMetaObject::activate (sender=0x967afb8, m=0x1059560, local_signal_index=2, argv=0xbfa75328) at kernel/qobject.cpp:3272
#27 0x0104a954 in OrgFreedesktopNetworkManagerInterface::PropertiesChanged (this=0x967afb8, _t1=...) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/solid/networkmanager-0.7/nm-manager-clientinterface.moc:175
#28 0x0104af1d in OrgFreedesktopNetworkManagerInterface::qt_metacall (this=0x967afb8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfa7558c) at /usr/src/debug/kdebase-workspace-4.5.3/i686-redhat-linux-gnu/solid/networkmanager-0.7/nm-manager-clientinterface.moc:107
#29 0x0728fb55 in QDBusConnectionPrivate::deliverCall (this=0x96724b8, object=0x967afb8, msg=..., metaTypes=..., slotIdx=7) at qdbusintegrator.cpp:919
#30 0x0729b3e8 in QDBusCallDeliveryEvent::placeMetaCall (this=0x965c6a0, object=0x967afb8) at qdbusintegrator_p.h:103
#31 0x07147e2f in QObject::event (this=0x967afb8, e=0x965c6a0) at kernel/qobject.cpp:1211
#32 0x02144d5c in QApplicationPrivate::notify_helper (this=0x959aaf0, receiver=0x967afb8, e=0x965c6a0) at kernel/qapplication.cpp:4396
#33 0x021498f2 in QApplication::notify (this=0xbfa75e30, receiver=0x967afb8, e=0x965c6a0) at kernel/qapplication.cpp:3798
#34 0x0647fddb in KApplication::notify (this=0xbfa75e30, receiver=0x967afb8, event=0x965c6a0) at /usr/src/debug/kdelibs-4.5.3/kdeui/kernel/kapplication.cpp:310
#35 0x07132633 in QCoreApplication::notifyInternal (this=0xbfa75e30, receiver=0x967afb8, event=0x965c6a0) at kernel/qcoreapplication.cpp:732
#36 0x07136355 in sendEvent (receiver=0x0, event_type=0, data=0x957a8b8) at kernel/qcoreapplication.h:215
#37 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x957a8b8) at kernel/qcoreapplication.cpp:1373
#38 0x0713652e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#39 0x07160195 in sendPostedEvents (s=0x959cf10) at kernel/qcoreapplication.h:220
#40 postEventSourceDispatch (s=0x959cf10) at kernel/qeventdispatcher_glib.cpp:277
#41 0x00a1e192 in g_main_dispatch (context=0x959ce90) at gmain.c:2149
#42 g_main_context_dispatch (context=0x959ce90) at gmain.c:2702
#43 0x00a1e978 in g_main_context_iterate (context=0x959ce90, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780
#44 0x00a1ec35 in g_main_context_iteration (context=0x959ce90, may_block=1) at gmain.c:2843
#45 0x0716030d in QEventDispatcherGlib::processEvents (this=0x957a368, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#46 0x021f6ad6 in QGuiEventDispatcherGlib::processEvents (this=0x957a368, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#47 0x071317ca in QEventLoop::processEvents (this=0xbfa75d84, flags=...) at kernel/qeventloop.cpp:149
#48 0x07131a7a in QEventLoop::exec (this=0xbfa75d84, flags=...) at kernel/qeventloop.cpp:201
#49 0x071365f7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#50 0x02142b98 in QApplication::exec () at kernel/qapplication.cpp:3672
#51 0x069e4efb in kdemain (argc=1, argv=0xbfa76054) at /usr/src/debug/kdelibs-4.5.3/kded/kded.cpp:894
#52 0x080486cc in main (argc=1, argv=0xbfa76054) at /usr/src/debug/kdelibs-4.5.3/i686-redhat-linux-gnu/kded/kded4_dummy.cpp:3

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-11-18 08:14:15 UTC
Thanks for the bug report! This looks like an issue which has been reported already.

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