Bug 163430

Created attachment 25183 [details]
Back trace of plasma crash

Sorry, can u get a backtrace with installed -dbg packages? 

Lukas

Backtrace as it happens on opeNSUSE: https://bugzilla.novell.com/show_bug.cgi?id=402244

[Thread debugging using libthread_db enabled]
[New Thread 0xb552a6f0 (LWP 2233)]
[New Thread 0xb18e0b90 (LWP 2291)]
[New Thread 0xb39e0b90 (LWP 2234)]
[KCrash handler]
#6  0x00000019 in ?? ()
#7  0xb30f7979 in PlasmaKGet::loadTransferGraph (this=0x0, type=1)
    at /usr/src/debug/kdenetwork-4.0.4/kget/plasma/applet/plasma-kget.cpp:142
#8  0xb30f9001 in PlasmaKGet::dataUpdated (this=0x80fa370, source=@0xbff99558,
    data=@0x8162c70)
    at /usr/src/debug/kdenetwork-4.0.4/kget/plasma/applet/plasma-kget.cpp:95
#9  0xb30f9876 in PlasmaKGet::qt_metacall (this=0x80fa370,
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff994c8)
    at /usr/src/debug/kdenetwork-4.0.4/build/kget/plasma/applet/plasma-kget.moc:72
#10 0xb77043fa in QMetaObject::activate (sender=0x82ccef8,
    from_signal_index=4, to_signal_index=4, argv=0xbff994c8)
    at kernel/qobject.cpp:3007
#11 0xb7704972 in QMetaObject::activate (sender=0x82ccef8, m=0xb7f2b6f8,
    local_signal_index=0, argv=0xbff994c8) at kernel/qobject.cpp:3080
#12 0xb7e7cbc9 in Plasma::DataContainer::dataUpdated (this=0x82ccef8,
    _t1=@0xbff99558, _t2=@0x8162c70)
    at /usr/src/debug/kdebase-workspace-4.0.4/build/libs/plasma/datacontainer.moc:94
#13 0xb7e7e663 in Plasma::DataContainer::checkForUpdate (this=0x82ccef8)
    at /usr/src/debug/kdebase-workspace-4.0.4/libs/plasma/datacontainer.cpp:74
#14 0xb7e80419 in Plasma::DataEngine::checkForUpdates (this=0x843d8c0)
    at /usr/src/debug/kdebase-workspace-4.0.4/libs/plasma/dataengine.cpp:487
#15 0xb7e80595 in Plasma::DataEngine::timerEvent (this=0x843d8c0,
    event=0xbff999fc)
    at /usr/src/debug/kdebase-workspace-4.0.4/libs/plasma/dataengine.cpp:469
#16 0xb7700d1f in QObject::event (this=0x843d8c0, e=0xbff999fc)
    at kernel/qobject.cpp:1105
#17 0xb6928ecc in QApplicationPrivate::notify_helper (this=0x8067ef0,
    receiver=0x843d8c0, e=0xbff999fc) at kernel/qapplication.cpp:3772
#18 0xb692f31e in QApplication::notify (this=0x805e830, receiver=0x843d8c0,
    e=0xbff999fc) at kernel/qapplication.cpp:3366
#19 0xb7c6c36d in KApplication::notify (this=0x805e830, receiver=0x843d8c0,
    event=0xbff999fc)
    at /usr/src/debug/kdelibs-4.0.4/kdeui/kernel/kapplication.cpp:314
#20 0xb76f2b51 in QCoreApplication::notifyInternal (this=0x805e830,
    receiver=0x843d8c0, event=0xbff999fc) at kernel/qcoreapplication.cpp:583
#21 0xb771b181 in QTimerInfoList::activateTimers (this=0x8068a04)
#22 0xb771b3fb in QEventDispatcherUNIX::processEvents (this=0x8055c68, flags=
      {i = -1074160904}) at kernel/qeventdispatcher_unix.cpp:899
#23 0xb69b30a2 in QEventDispatcherX11::processEvents (this=0x8055c68, flags=
      {i = -1074160456}) at kernel/qeventdispatcher_x11.cpp:154
#24 0xb76f12ca in QEventLoop::processEvents (this=0xbff99d20, flags=
      {i = -1074160392}) at kernel/qeventloop.cpp:149
#25 0xb76f148a in QEventLoop::exec (this=0xbff99d20, flags={i = -1074160344})
    at kernel/qeventloop.cpp:196
#26 0xb76f366d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#27 0xb6928d47 in QApplication::exec () at kernel/qapplication.cpp:3304
#28 0xb7f39671 in kdemain (argc=1, argv=0xbff99ef4)
    at /usr/src/debug/kdebase-workspace-4.0.4/plasma/plasma/main.cpp:54
#29 0x080487c2 in main (argc=-1290766744, argv=0x8245c80)
    at /usr/src/debug/kdebase-workspace-4.0.4/build/plasma/plasma/plasma-qgv_dummy.cpp:3
#0  0xffffe430 in __kernel_vsyscall ()

I think the problem is not initializing m_transferGraph(0) in the constructor... someone wants to change and test? Sorry I have no 4.0-branch checkout here :(

Lukas

Well this is fixed in 4.1...

Lukas