Version:            (using KDE 4.2.2)
OS:                Linux

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb60b38d0 (LWP 8272)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f07430 in __kernel_vsyscall ()
[Current thread is 0 (process 8272)]

Thread 1 (Thread 0xb60b38d0 (LWP 8272)):
#0  0xb7f07430 in __kernel_vsyscall ()
#1  0xb7e0adc0 in sleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb79bf612 in ?? () from /usr/lib/libkdeui.so.5
#3  0xb79c0014 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0xb73d42a4 in QString::operator== () from /usr/lib/libQtCore.so.4
#6  0xb7bfa88d in ?? () from /usr/lib/libkio.so.5
#7  0xb7bfab3b in ?? () from /usr/lib/libkio.so.5
#8  0xb7497a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb74987e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb74d2633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#11 0xb749d637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#12 0xb6a158ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#13 0xb6a1d72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0xb7951d1d in KApplication::notify () from /usr/lib/libkdeui.so.5
#15 0xb7482e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#16 0xb74ad70a in ?? () from /usr/lib/libQtCore.so.4
#17 0xb64446f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0x0817a798 in ?? ()
#19 0xb6447da3 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb6447f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00000001 in ?? ()
#22 0xb74ad478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#23 0xb6aafea5 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb748152a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb74816ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7483da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6a15767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0xb7ed6ec6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#29 0x080485a2 in _start ()
#0  0xb7f07430 in __kernel_vsyscall ()


**That's what was shown in details, it caused a signal 11 kded4