Application: akonadi_ical_resource (0.1) KDE Platform Version: 4.5.85 (4.6 Beta2) Qt Version: 4.7.1 Operating System: Linux 2.6.37-9-generic i686 Distribution: Ubuntu natty (development branch) -- Information about the crash: - What I was doing when the application crashed: I have two ical files configured, one local and one fetched via HTTP (read-only). Since updating to KDE 4.6 Beta I get three crash reports on every startup, and the data from those two files is not available in Kontact. An additional vCard resource for contacts works. You may use http://hogsmeade.lieberbiber.de/~sturmflut/tv.vcal as an example, it contains TV show dates and is updated three times a day. The other ical file is private. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_ical_resource), signal: Aborted [KCrash Handler] #7 0x00b45416 in __kernel_vsyscall () #8 0x00d31941 in raise () from /lib/libc.so.6 #9 0x00d34e42 in abort () from /lib/libc.so.6 #10 0x00bf40d5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #11 0x00bf1fc5 in ?? () from /usr/lib/libstdc++.so.6 #12 0x00bf2002 in std::terminate() () from /usr/lib/libstdc++.so.6 #13 0x00bf21cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #14 0x05aac984 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #15 0x00fa8844 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #16 0x00fad34e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x0094890a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x05a9760b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #19 0x05a9b1c9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #20 0x05a9b35d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #21 0x05ac48f4 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/libQtCore.so.4 #22 0x01b3fb18 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x01b402e0 in ?? () from /lib/libglib-2.0.so.0 #24 0x01b40594 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x05ac4a6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #26 0x0105aad5 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtGui.so.4 #27 0x05a967d9 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #28 0x05a96a72 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #29 0x05a9b41c in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #30 0x00fa66e7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #31 0x0067a2c3 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #32 0x08059713 in init<ICalResource> (argc=) at /usr/include/akonadi/resourcebase.h:188 #33 main (argc=) at ../../../resources/ical/icalresourcemain.cpp:22 Possible duplicates by query: bug 260344, bug 260304, bug 260298, bug 260273, bug 260264. Reported using DrKonqi
Created attachment 55060 [details] New crash information added by DrKonqi akonadi_ical_resource (0.1) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.1 - What I was doing when the application crashed: I maked a update of opensuse KDE Factory. After reboot I started Kontakt and choosed Kadressbook. akonadi crash. Since that time akonadi_ical_recource crashes at every start. -- Backtrace (Reduced): #14 0xb5ef2b87 in QEventLoop::exec (this=0xbfcddc74, flags=...) at kernel/qeventloop.cpp:214 #15 0xb5ef7570 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #16 0xb6428114 in QApplication::exec () at kernel/qapplication.cpp:3719 #17 0xb766e0b4 in Akonadi::ResourceBase::init (r=0x80ce4e8) at /usr/src/debug/kdepimlibs-4.5.85/akonadi/resourcebase.cpp:283 #18 0x0805a433 in init<ICalResource> (argc=) at /usr/include/akonadi/resourcebase.h:188
*** This bug has been marked as a duplicate of bug 258754 ***