Bug 134883

Version:            (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs
OS:                Linux

Sorry I cannot reproduce it yet.

What had happened:
Using the newest Suse packages for KDE 3.5.4 on updated Suse 10.1.

Some surfing inner my file system with the file manager, then it crashes completely. After this it restarts without problems and the crashmanager pops up with the following output:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230551376 (LWP 4062)]
[KCrash handler]
#6  0xb607dd59 in TaskContainer::updateKickerTip ()
   from /opt/kde3/lib/libtaskbar.so.1
#7  0xb676dbd2 in KickerTip::display () from /opt/kde3/lib/libkickermain.so.1
#8  0xb676e14f in KickerTip::qt_invoke () from /opt/kde3/lib/libkickermain.so.1
#9  0xb758ff1d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb7590b7d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb78cad09 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb75b373f in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb7530f07 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb7531cd1 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb7ba0de3 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#16 0xb7526095 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb74e08e0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb7547d28 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb7547bbe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb7530abf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb6814ab2 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so
#22 0xb730b534 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so
#23 0x0804e2ff in launch ()
#24 0x0804eb8a in handle_launcher_request ()
#25 0x0804ef0f in handle_requests ()
#26 0x0805010c in main ()

Hope someone can reproduce it or can find this crash bug.

Best Regards
Haeber