Application: akonadi_birthdays_resource (0.1) KDE Platform Version: 4.4.00 (KDE 4.4.0) Qt Version: 4.6.1 Operating System: Linux 2.6.31-20-generic x86_64 Distribution: Ubuntu 9.10 -- Information about the crash: I have just updated to KDE SC 4.4 from RC3 on Kubuntu 9.10 AMD64. I now get this message repeatedly from the CRA every time I login of close the previous message. I followed the directions for the "Nepomuk Indexing Agents have been Disabled" on the Akonadi user base page and it got Nepomuk/Strigi running but didn't solve this issue . -- Backtrace: Application: Akonadi Resource (akonadi_birthdays_resource), signal: Aborted [KCrash Handler] #5 0x00007f010936e4b5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007f0109371f50 in *__GI_abort () at abort.c:92 #7 0x00007f0109989cc5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x00007f01099880f6 in ?? () from /usr/lib/libstdc++.so.6 #9 0x00007f0109988123 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x00007f010998821e in __cxa_throw () from /usr/lib/libstdc++.so.6 #11 0x00007f0109c420f2 in qBadAlloc () at global/qglobal.cpp:2004 #12 0x00007f010aa2e80d in QX11PixmapData::toImage (this=0x1679a40) at image/qpixmap_x11.cpp:1482 #13 0x00007f010aa15ee0 in QPixmap::toImage (this=0x7fffb5755190) at image/qpixmap.cpp:488 #14 0x00007f010b6c12d3 in KPixmapCache::Private::writeData (this=0x161c3f0, key=<value optimized out>, pix=<value optimized out>) at ../../kdeui/util/kpixmapcache.cpp:1444 #15 0x00007f010b6c206b in KPixmapCache::insert (this=0x15932c0, key=..., pix=...) at ../../kdeui/util/kpixmapcache.cpp:1410 #16 0x00007f010b606df4 in KIconLoader::loadIcon (this=0x1550d10, _name=<value optimized out>, group=<value optimized out>, size=128, state=<value optimized out>, overlays=..., path_store=0x0, canReturnNull=true) at ../../kdeui/icons/kiconloader.cpp:1005 #17 0x00007f010b606b34 in KIconLoader::loadIcon (this=0x1550d10, _name=<value optimized out>, group=<value optimized out>, size=128, state=<value optimized out>, overlays=..., path_store=0x0, canReturnNull=false) at ../../kdeui/icons/kiconloader.cpp:1130 #18 0x00007f010b5fd74d in KIconEngine::pixmap (this=<value optimized out>, size=..., mode=<value optimized out>, state=<value optimized out>) at ../../kdeui/icons/kiconengine.cpp:119 #19 0x00007f010a9e5995 in QIcon::pixmap (this=<value optimized out>, size=..., mode=4294967295, state=10) at image/qicon.cpp:669 #20 0x00007f010a9d2364 in QWidgetPrivate::setWindowIcon_sys (this=<value optimized out>, forceReset=<value optimized out>) at kernel/qwidget_x11.cpp:1458 #21 0x00007f010a98b5e8 in QWidget::create (this=0x15aa0e0, window=0, initializeWindow=<value optimized out>, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1351 #22 0x00007f010a9c2a47 in setupOwner () at kernel/qclipboard_x11.cpp:131 #23 0x00007f010a9c3471 in QClipboard (this=0x15a9b80, parent=0x10f) at kernel/qclipboard_x11.cpp:458 #24 0x00007f010a9341d7 in QApplication::clipboard () at kernel/qapplication.cpp:3088 #25 0x00007f010b6443ee in KClipboardSynchronizer::Private::setupSignals (this=0xbb5) at ../../kdeui/kernel/kclipboard.cpp:94 #26 0x00007f010b6447a2 in KClipboardSynchronizer (this=0x15a9980, parent=<value optimized out>) at ../../kdeui/kernel/kclipboard.cpp:84 #27 0x00007f010b644934 in operator-> () at ../../kdeui/kernel/kclipboard.cpp:73 #28 operator KClipboardSynchronizer* () at ../../kdeui/kernel/kclipboard.cpp:73 #29 KClipboardSynchronizer::self () at ../../kdeui/kernel/kclipboard.cpp:74 #30 0x00007f010b63f721 in KApplicationPrivate::init (this=0x159e840, GUIenabled=true) at ../../kdeui/kernel/kapplication.cpp:463 #31 0x00007f010b640da9 in KApplication (this=0x7fffb5756530, GUIenabled=<value optimized out>) at ../../kdeui/kernel/kapplication.cpp:343 #32 0x0000000000409a97 in _start () This bug may be a duplicate of or related to bug 225168. Possible duplicates by query: bug 225168, bug 224295, bug 222155. Reported using DrKonqi
This issue is being tracked at bug 222155. Thanks *** This bug has been marked as a duplicate of bug 222155 ***