KDE bug report in gnome

Bug #317787 reported by Michael Jones
This bug report is a duplicate of:  Bug #277619: kded4 crashed at update. Edit Remove
2
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I got this while running the jaunty updater last night.

Application: KDE Daemon (kded4), signal SIGABRT

Thread 1 (Thread 0xb613b700 (LWP 5779)):
[KCrash Handler]
#6 0xb7ff6430 in __kernel_vsyscall ()
#7 0xb66c66a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb66c8068 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67041ed in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0xb670a5a4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#11 0xb670c556 in free () from /lib/tls/i686/cmov/libc.so.6
#12 0xb68ec111 in operator delete () from /usr/lib/libstdc++.so.6
#13 0xb68ec16d in operator delete[] () from /usr/lib/libstdc++.so.6
#14 0xb6ad6e59 in QHashData::destroyAndFree () from /usr/lib/libQtCore.so.4
#15 0xb6b3a563 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb6b39a97 in ?? () from /usr/lib/libQtCore.so.4
#17 0xb6b24a5d in QAbstractFileEngineIterator::currentFileInfo () from /usr/lib/libQtCore.so.4
#18 0xb6b7b789 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb6b30e8b in ?? () from /usr/lib/libQtCore.so.4
#20 0xb6b318e3 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb6b31d0f in QDirIterator::hasNext () from /usr/lib/libQtCore.so.4
#22 0xb6b246b8 in QAbstractFileEngine::entryList () from /usr/lib/libQtCore.so.4
#23 0xb6b78fef in QFSFileEngine::entryList () from /usr/lib/libQtCore.so.4
#24 0xb6b29978 in QDir::entryInfoList () from /usr/lib/libQtCore.so.4
#25 0xb6b29baf in QDir::entryInfoList () from /usr/lib/libQtCore.so.4
#26 0xb7e4a1e6 in ?? () from /usr/lib/libkio.so.5
#27 0xb7e4a8b3 in KDirWatch::addDir () from /usr/lib/libkio.so.5
#28 0xb7fcee87 in ?? () from /usr/lib/libkdeinit4_kded4.so
#29 0xb7fcf007 in ?? () from /usr/lib/libkdeinit4_kded4.so
#30 0xb7fd2750 in ?? () from /usr/lib/libkdeinit4_kded4.so
#31 0xb7fd27e9 in ?? () from /usr/lib/libkdeinit4_kded4.so
#32 0xb7fd4c83 in ?? () from /usr/lib/libkdeinit4_kded4.so
#33 0xb6bbac10 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#34 0xb6bbb992 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#35 0xb6bf5ab7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#36 0xb6bc15be in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#37 0xb6bb56ef in QObject::event () from /usr/lib/libQtCore.so.4
#38 0xb706e87c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#39 0xb70766fe in QApplication::notify () from /usr/lib/libQtGui.so.4
#40 0xb7b8e00d in KApplication::notify () from /usr/lib/libkdeui.so.5
#41 0xb6ba5ff1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#42 0xb6bd3f31 in ?? () from /usr/lib/libQtCore.so.4
#43 0xb6bd06d0 in ?? () from /usr/lib/libQtCore.so.4
#44 0xb6471b18 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#45 0xb64751c3 in ?? () from /usr/lib/libglib-2.0.so.0
#46 0xb6475381 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#47 0xb6bd0628 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#48 0xb7108ee5 in ?? () from /usr/lib/libQtGui.so.4
#49 0xb6ba46ba in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#50 0xb6ba487a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#51 0xb6ba6f35 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#52 0xb706e6f7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#53 0xb7fd5996 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#54 0x080486b2 in _start ()

why wasn't this reported using apport? the notification happened through some kde application.

before you ask, I can't provide any additional information. I wiped my system this afternoon (as part of scheduled cyclical maintenance)
I'm just reporting the bug how it came up like it asked me to.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.