Application: akonadi_googlecalendar_resource (4.9) KDE Platform Version: 4.9.2 Qt Version: 4.8.3 Operating System: Linux 3.5.0-18-generic i686 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: Starting up Kubuntu from powered off. Kmail is set to run automatically on startup. I get several messages saying that an akonadi gmail component has crashed. However, after closing 3-4 of the crash reports, kmail starts and is functional as normal. The crash can be reproduced every time. -- Backtrace: Application: Google Calendars and Tasks (akonadi_googlecalendar_resource), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xb770f424 in __kernel_vsyscall () #8 0xb5bbf1df in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0xb5bc2825 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0xb5da58ad in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0xb5da34f3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0xb5da352f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0xb5da3825 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0xb727d7e7 in QEventLoop::exec (this=0xbffd0cd8, flags=...) at kernel/qeventloop.cpp:218 #15 0xb7282cba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #16 0xb676cfc4 in QApplication::exec () at kernel/qapplication.cpp:3823 #17 0xb75e1611 in Akonadi::ResourceBase::init (r=0xa0f89a8) at ../../akonadi/resourcebase.cpp:451 #18 0x0805baab in Akonadi::ResourceBase::init<CalendarResource> (argc=argc@entry=3, argv=argv@entry=0xbffd0e54) at /usr/include/KDE/Akonadi/../../akonadi/resourcebase.h:188 #19 0x080527eb in main (argc=3, argv=0xbffd0e54) at ../../../../resources/google/calendar/calendarresource.cpp:659 Possible duplicates by query: bug 310179, bug 310096, bug 310054, bug 309824, bug 309788. Reported using DrKonqi
This particular crash should be fixed in KDE 4.9.3. *** This bug has been marked as a duplicate of bug 305584 ***