Bug 298182 - Crash when Akonadi is started
Summary: Crash when Akonadi is started
Status: RESOLVED DUPLICATE of bug 297824
Alias: None
Product: libkgapi
Classification: Frameworks and Libraries
Component: calendar (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-15 13:29 UTC by Frédéric COIFFIER
Modified: 2012-04-15 14:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric COIFFIER 2012-04-15 13:29:17 UTC
Application: akonadi_googlecalendar_resource (4.8)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.3.1-gentoo x86_64
Distribution: "Gentoo Base System release 2.1"

-- Information about the crash:
- What I was doing when the application crashed:

Each time akonadi starts, the plugin akonadi google calendar crashes. It didn't occur during the first days after the installation.

The crash can be reproduced every time.

-- Backtrace:
Application: Google Calendar - Mon agenda of type Google Calendars and Tasks (akonadi_googlecalendar_resource), signal: Aborted
[KCrash Handler]
#6  0x0000003e6e035a35 in raise () from /lib64/libc.so.6
#7  0x0000003e6e036d35 in abort () from /lib64/libc.so.6
#8  0x0000003d11cb96ed in __gnu_cxx::__verbose_terminate_handler () at /hdf/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libstdc++-v3/libsupc++/vterminate.cc:93
#9  0x0000003d11cb7926 in __cxxabiv1::__terminate (handler=<optimized out>) at /hdf/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0x0000003d11cb7953 in std::terminate () at /hdf/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0x0000003d11cb7aa5 in __cxxabiv1::__cxa_rethrow () at /hdf/tmp/portage/sys-devel/gcc-4.5.3-r2/work/gcc-4.5.3/libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x0000003d9df80539 in QEventLoop::exec (this=0x7fff558be1f0, flags=...) at kernel/qeventloop.cpp:218
#13 0x0000003d9df84abb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x00007f15108d57c6 in Akonadi::ResourceBase::init (r=0x1098b90) at /hdf/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2/akonadi/resourcebase.cpp:412
#15 0x0000000000414c08 in init<CalendarResource> (argv=<optimized out>, argc=<optimized out>) at /usr/include/KDE/Akonadi/../../akonadi/resourcebase.h:188
#16 main (argc=<optimized out>, argv=<optimized out>) at /hdf/tmp/portage/kde-misc/akonadi-google-0.3/work/akonadi-google-0.3/calendar/calendarresource.cpp:594

Possible duplicates by query: bug 296407, bug 293802, bug 289446, bug 284551, bug 284493.

Reported using DrKonqi
Comment 1 Daniel Vrátil 2012-04-15 13:44:27 UTC

*** This bug has been marked as a duplicate of bug 297824 ***
Comment 2 Daniel Vrátil 2012-04-15 14:01:29 UTC
Please try to provide backtrace of where the exception has been thrown using following guides:

http://techbase.kde.org/Projects/PIM/Akonadi/Development_Tools#Debugging_Akonadi_Agents

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash

Please post the backtrace to the main tracking bug (bug #297824). Thank you