Version: (using KDE 4.2.1) OS: Linux Installed from: Fedora RPMs Here's the following per your request "Please help us improve the software you use by filing a report at http://bugs.kde.org." Application: KDE Daemon (kded4), signal SIGABRT [Current thread is 1 (Thread 0xb7ef1770 (LWP 4380))] Thread 3 (Thread 0xae2afb90 (LWP 4527)): #0 0x005ee416 in __kernel_vsyscall () #1 0x007761f3 in __lll_lock_wait_private () from /lib/libc.so.6 #2 0x006f7cfd in _L_lock_4593 () from /lib/libc.so.6 #3 0x006f434a in free () from /lib/libc.so.6 #4 0x00cfb591 in operator delete () from /usr/lib/libstdc++.so.6 #5 0x052d275f in QEventDispatcherGlib::unregisterSocketNotifier () from /usr/lib/libQtCore.so.4 #6 0x052c285d in QSocketNotifier::setEnabled () from /usr/lib/libQtCore.so.4 #7 0x052d2b4f in ?? () from /usr/lib/libQtCore.so.4 #8 0x009f8e48 in g_main_context_check () from /lib/libglib-2.0.so.0 #9 0x009f97cd in ?? () from /lib/libglib-2.0.so.0 #10 0x009f9aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #11 0x052d2817 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #12 0x052a688a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #13 0x052a6a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #14 0x051b44d9 in QThread::exec () from /usr/lib/libQtCore.so.4 #15 0x0528abeb in ?? () from /usr/lib/libQtCore.so.4 #16 0x051b775e in ?? () from /usr/lib/libQtCore.so.4 #17 0x0083151f in start_thread () from /lib/libpthread.so.0 #18 0x0076704e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb1ed7b90 (LWP 4620)): #0 0x005ee416 in __kernel_vsyscall () #1 0x0075f3d1 in select () from /lib/libc.so.6 #2 0x05287627 in ?? () from /usr/lib/libQtCore.so.4 #3 0x051b775e in ?? () from /usr/lib/libQtCore.so.4 #4 0x0083151f in start_thread () from /lib/libpthread.so.0 #5 0x0076704e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb7ef1770 (LWP 4380)): [KCrash Handler] #6 0x005ee416 in __kernel_vsyscall () #7 0x006ae460 in raise () from /lib/libc.so.6 #8 0x006afe28 in abort () from /lib/libc.so.6 #9 0x006ebfed in __libc_message () from /lib/libc.so.6 #10 0x006f23a4 in malloc_printerr () from /lib/libc.so.6 #11 0x006f4356 in free () from /lib/libc.so.6 #12 0x051b1fed in qFree () from /usr/lib/libQtCore.so.4 #13 0x05c91e30 in ?? () from /usr/lib/libkio.so.5 #14 0x05c8f3aa in ?? () from /usr/lib/libkio.so.5 #15 0x05c90d73 in ?? () from /usr/lib/libkio.so.5 #16 0x05c90e9b in ?? () from /usr/lib/libkio.so.5 #17 0x052bcdf0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #18 0x052bdb72 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #19 0x052f7ac3 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4 #20 0x052c29c7 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4 #21 0x0653b68c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #22 0x065434ce in QApplication::notify () from /usr/lib/libQtGui.so.4 #23 0x058a80fd in KApplication::notify () from /usr/lib/libkdeui.so.5 #24 0x052a81c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #25 0x052d2a8a in ?? () from /usr/lib/libQtCore.so.4 #26 0x009f6238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #27 0x009f98e3 in ?? () from /lib/libglib-2.0.so.0 #28 0x009f9aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #29 0x052d27f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #30 0x065d4515 in ?? () from /usr/lib/libQtGui.so.4 #31 0x052a688a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #32 0x052a6a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #33 0x052a9105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #34 0x0653b507 in QApplication::exec () from /usr/lib/libQtGui.so.4 #35 0x00da3520 in kdemain () from /usr/lib/libkdeinit4_kded4.so #36 0x08048692 in _start ()
What were you doing when the application crashed ?
I was running yumex and had one term open watching top, this is a fresh install of FC10 as well (20 mins prior to setting up this ws)
What's yumex? Some software that installs packages, I assume? Then this is most probably another instance of bug 165548. *** This bug has been marked as a duplicate of bug 165548 ***