Application: akonadi_googlecalendar_resource (4.11) KDE Platform Version: 4.11.3 Qt Version: 4.8.6 Operating System: Linux 3.11-2-amd64 i686 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I had Kontact running on the second virtual desktop of IceWM, in a Debian unstable installation, and was working in an uxterm on the first virtual desktop, when the Krash handler popped up. That means “it must have been doing something in the background”, as Kontact was idling for a while. - Unusual behavior I noticed: This is Debian unstable. I cannot provide a complete backtrace for the following reason: tglase@tglase:~ $ dpkg -S /usr/bin/akonadi_googlecalendar_resource kdepim-runtime: /usr/bin/akonadi_googlecalendar_resource tglase@tglase:~ $ dpkg -L kdepim-runtime-dbg | fgrep -c akonadi_googlecalendar_resource 0 Basically, the -dbg package is missing symbols for some components. Ever since the upgrade to KDE 4.11(.3) in Debian unstable, the system has been behaving even worse than before – for example, I could not mark messages as read any more: http://thread.gmane.org/gmane.comp.kde.users.pim/22033 Also, since a few days, I’ve been having lots of zombies in the system: tglase@tglase:~ $ ps ax | fgrep ' Z ' 2965 ? Z 0:00 [virtuoso-t] <defunct> 2981 ? Z 0:00 [virtuoso-t] <defunct> 3145 ? Z 0:00 [virtuoso-t] <defunct> 3158 ? Z 0:00 [virtuoso-t] <defunct> 3172 ? Z 0:00 [virtuoso-t] <defunct> 3190 ? Z 0:00 [virtuoso-t] <defunct> 3217 ? Z 0:00 [virtuoso-t] <defunct> 3230 ? Z 0:00 [virtuoso-t] <defunct> 3237 ? Z 0:00 [virtuoso-t] <defunct> 3261 ? Z 0:00 [virtuoso-t] <defunct> 3271 ? Z 0:00 [virtuoso-t] <defunct> 3289 ? Z 0:00 [virtuoso-t] <defunct> 3817 ? Z 0:00 [virtuoso-t] <defunct> 3832 ? Z 0:00 [virtuoso-t] <defunct> 13379 pts/7 S+ 0:00 fgrep Z 25590 ? Z 0:00 [virtuoso-t] <defunct> 25601 ? Z 0:00 [virtuoso-t] <defunct> 25642 ? Z 0:00 [virtuoso-t] <defunct> 25678 ? Z 0:00 [virtuoso-t] <defunct> 25743 ? Z 0:00 [virtuoso-t] <defunct> 25969 ? Z 0:00 [virtuoso-t] <defunct> 26012 ? Z 0:00 [virtuoso-t] <defunct> 26056 ? Z 0:00 [virtuoso-t] <defunct> 26075 ? Z 0:00 [virtuoso-t] <defunct> 26686 ? Z 0:00 [virtuoso-t] <defunct> 27505 ? Z 0:00 [virtuoso-t] <defunct> 28267 ? Z 0:00 [virtuoso-t] <defunct> This goes along with Konqueror freezing for several minutes at a time, after which all currently-running downloads obviously abort. (Happened at least twice.) Then it recovers and is usable (and much faster than M*zilla) again. - Custom settings of the application: Stock Debian unstable, except /usr/lib/i386-linux-gnu/qt4/plugins/sqldrivers/libqsqlpsql.so which I had to downgrade to libqt4-sql-psql (src:qt4-x11) 4:4.8.4+dfsg-4 because otherwise Akonadi won’t work with PostgreSQL at all (known bug, should be in the KDE tracker). Using KDM but not a full KDE session, rather IceWM (with the usual stuff like dbus that KDE/Debian adds). Kontact is set up with a Google account for calendars and eMail, a locally-running uw-imapd so I have actual folders, and three Kolab accounts I need to use for testing on two separate servers. -- Backtrace: Application: Google Calendars and Tasks (t.glaser@tarent.de) of type Google Calendars and Tasks (akonadi_googlecalendar_resource), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [KCrash Handler] #7 0xf7734425 in __kernel_vsyscall () #8 0xf58c881f in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #9 0xf58cbcd3 in __GI_abort () at abort.c:90 #10 0xf5ab2595 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0xf5ab0203 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0xf5ab023f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0xf5ab04f5 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0xf71d3a15 in QEventLoop::exec (this=this@entry=0xffd787e8, flags=...) at kernel/qeventloop.cpp:218 #15 0xf71d961e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #16 0xf66ddd34 in QApplication::exec () at kernel/qapplication.cpp:3828 #17 0xf7600088 in Akonadi::ResourceBase::init (r=r@entry=0x82e21b0) at ../../akonadi/resourcebase.cpp:548 #18 0x080617bd in Akonadi::ResourceBase::init<CalendarResource> (argc=argc@entry=3, argv=argv@entry=0xffd78954) at /usr/include/KDE/Akonadi/../../akonadi/resourcebase.h:192 #19 0x0805357b in main (argc=3, argv=0xffd78954) at ../../../../resources/google/calendar/calendarresource.cpp:774 Reported using DrKonqi
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.