Application: akonadi_googlecalendar_resource (4.8) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-23-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: Nothing, had rebooted and akonadi-google was running in the background - Unusual behavior I noticed: akonadi-google crashes, so contacts and calendar aren't syncronized - Custom settings of the application: None The crash can be reproduced every time. -- Backtrace: Application: Google Calendars and Tasks (akonadi_googlecalendar_resource), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x00007fbafbd5d445 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007fbafbd60bab in __GI_abort () at abort.c:91 #8 0x00007fbafc3b169d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007fbafc3af846 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00007fbafc3af873 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x00007fbafc3af9b6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x00007fbafe47516c in QEventLoop::exec (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007fbafe479f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #14 0x00007fbafebe5bf6 in Akonadi::ResourceBase::init (r=0x114b9d0) at ../../akonadi/resourcebase.cpp:412 #15 0x0000000000416216 in int Akonadi::ResourceBase::init<CalendarResource>(int, char**) () #16 0x00007fbafbd4876d in __libc_start_main (main=0x40d9d0, argc=3, ubp_av=0x7ffffe765878, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffffe765868) at libc-start.c:226 #17 0x000000000040da01 in _start () Possible duplicates by query: bug 298005, bug 297031, bug 296744, bug 296435, bug 296407. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 297824 ***
*** Bug 299750 has been marked as a duplicate of this bug. ***