Bug 296993 - akonadi kolabproxy crash after editing a calendar event
Summary: akonadi kolabproxy crash after editing a calendar event
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2012-03-28 21:40 UTC by Thorsten Schnebeck
Modified: 2018-09-19 14:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (4.91 KB, text/plain)
2012-04-10 20:24 UTC, Matija Šuklje
Details
New crash information added by DrKonqi (4.91 KB, text/plain)
2012-04-10 21:46 UTC, Matija Šuklje
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Schnebeck 2012-03-28 21:40:17 UTC
Application: akonadi_kolabproxy_resource (4.8)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
I changed an event and pressed RMB+resync on Korganizer-kpart in Kontact
Restart of ressource seems to lead to duplicates of events in akonadi cache but not on server(!)

The crash can be reproduced every time.

-- Backtrace:
Application: Kolab vom Typ Kolab Groupware-Server (akonadi_kolabproxy_resource), signal: Segmentation fault
[KCrash Handler]
#6  KolabProxyResource::retrieveItems (this=0xe0a2f0, collection=...) at ../../../resources/kolabproxy/kolabproxyresource.cpp:186
#7  0x00007f14dcbd0da8 in Akonadi::ResourceBasePrivate::slotSynchronizeCollection (this=0xe08e20, col=...) at ../../akonadi/resourcebase.cpp:693
#8  0x00007f14dcbd363d in Akonadi::ResourceBase::qt_metacall (this=0xe0a2f0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffa0585310) at ./moc_resourcebase.cpp:148
#9  0x0000000000421345 in KolabProxyResource::qt_metacall (this=0xe0a2f0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffa0585310) at ./kolabproxyresource.moc:122
#10 0x00007f14d9987c09 in QMetaObject::activate (sender=0xe03250, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa0585310) at kernel/qobject.cpp:3566
#11 0x00007f14dcbd50c5 in Akonadi::ResourceScheduler::executeCollectionSync (this=<optimized out>, _t1=<optimized out>) at ./resourcescheduler_p.moc:147
#12 0x00007f14dcbdae24 in Akonadi::ResourceScheduler::executeNext (this=0xe03250) at ../../akonadi/resourcescheduler.cpp:299
#13 0x00007f14dcbdc108 in Akonadi::ResourceScheduler::qt_metacall (this=0xe03250, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x4b577a0) at ./resourcescheduler_p.moc:122
#14 0x00007f14d998cbc6 in QObject::event (this=0xe03250, e=<optimized out>) at kernel/qobject.cpp:1195
#15 0x00007f14da367104 in notify_helper (e=0x4cb6990, receiver=0xe03250, this=0xc730f0) at kernel/qapplication.cpp:4555
#16 QApplicationPrivate::notify_helper (this=0xc730f0, receiver=0xe03250, e=0x4cb6990) at kernel/qapplication.cpp:4527
#17 0x00007f14da36bf83 in QApplication::notify (this=0x7fffa0586060, receiver=0xe03250, e=0x4cb6990) at kernel/qapplication.cpp:4416
#18 0x00007f14db0999a6 in KApplication::notify (this=0x7fffa0586060, receiver=0xe03250, event=0x4cb6990) at ../../kdeui/kernel/kapplication.cpp:311
#19 0x00007f14d997361c in QCoreApplication::notifyInternal (this=0x7fffa0586060, receiver=0xe03250, event=0x4cb6990) at kernel/qcoreapplication.cpp:876
#20 0x00007f14d99773ea in sendEvent (event=0x4cb6990, receiver=0xe03250) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xc3e2b0) at kernel/qcoreapplication.cpp:1500
#22 0x00007f14d99a2793 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#24 0x00007f14d51cba5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f14d51cc258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f14d51cc429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f14d99a2bbf in QEventDispatcherGlib::processEvents (this=0xc3f770, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#28 0x00007f14da40c28e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f14d9972402 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f14d9972657 in QEventLoop::exec (this=0x7fffa0585fe0, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007f14d99776e7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#32 0x00007f14dcbcdfd6 in Akonadi::ResourceBase::init (r=0xe0a2f0) at ../../akonadi/resourcebase.cpp:412
#33 0x0000000000422946 in Akonadi::ResourceBase::init<KolabProxyResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:188
#34 0x00007f14d8f5c30d in __libc_start_main (main=0x417140 <main(int, char**)>, argc=3, ubp_av=0x7fffa0586178, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa0586168) at libc-start.c:226
#35 0x00000000004172f5 in _start ()

Reported using DrKonqi
Comment 1 Matija Šuklje 2012-04-10 20:24:33 UTC
Created attachment 70295 [details]
New crash information added by DrKonqi

akonadi_kolabproxy_resource (4.8) on KDE Platform 4.8.2 (4.8.2) using Qt 4.7.4

- What I was doing when the application crashed:

In Zanshin I was moving a project which falsly got shown (many of them were!) in the Inbox to the appropriate Kolab resource.

-- Backtrace (Reduced):
#6  KolabProxyResource::retrieveItems (this=0x1e59930, collection=<optimized out>) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.2/work/kdepim-runtime-4.8.2/resources/kolabproxy/kolabproxyresource.cpp:186
#7  0x00007f137390aa77 in Akonadi::ResourceBasePrivate::slotSynchronizeCollection (this=0x1ee09d0, col=<optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2/akonadi/resourcebase.cpp:693
#8  0x00007f137390d1bd in Akonadi::ResourceBase::qt_metacall (this=0x1e59930, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd5692cd0) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/akonadi/moc_resourcebase.cpp:148
#9  0x00000000004245e5 in KolabProxyResource::qt_metacall (this=0x1e59930, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffd5692cd0) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.2/work/kdepim-runtime-4.8.2_build/resources/kolabproxy/kolabproxyresource.moc:122
[...]
#11 0x00007f137390ed85 in Akonadi::ResourceScheduler::executeCollectionSync (this=<optimized out>, _t1=<optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/akonadi/resourcescheduler_p.moc:147
Comment 2 Matija Šuklje 2012-04-10 21:46:51 UTC
Created attachment 70297 [details]
New crash information added by DrKonqi

akonadi_kolabproxy_resource (4.8) on KDE Platform 4.8.2 (4.8.2) using Qt 4.7.4

- What I was doing when the application crashed:

In Zanshin I triggered a Kolab sync by running File → Synchronise all. Then KolabSync crashed.

I can replicate this everytime.

-- Backtrace (Reduced):
#6  KolabProxyResource::retrieveItems (this=0x1f5d960, collection=<optimized out>) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.2/work/kdepim-runtime-4.8.2/resources/kolabproxy/kolabproxyresource.cpp:186
#7  0x00007f022d462a77 in Akonadi::ResourceBasePrivate::slotSynchronizeCollection (this=0x1f5d530, col=<optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2/akonadi/resourcebase.cpp:693
#8  0x00007f022d4651bd in Akonadi::ResourceBase::qt_metacall (this=0x1f5d960, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffe6948e70) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/akonadi/moc_resourcebase.cpp:148
#9  0x00000000004245e5 in KolabProxyResource::qt_metacall (this=0x1f5d960, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffe6948e70) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.2/work/kdepim-runtime-4.8.2_build/resources/kolabproxy/kolabproxyresource.moc:122
[...]
#11 0x00007f022d466d85 in Akonadi::ResourceScheduler::executeCollectionSync (this=<optimized out>, _t1=<optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/akonadi/resourcescheduler_p.moc:147
Comment 3 Christian Mollekopf 2012-06-08 16:02:54 UTC
I cannot reproduce this issue and assume this is fixed. Can anyone reproduce this with master or a 4.9 beta?
Comment 4 Andrew Crouthamel 2018-09-19 14:28:27 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.