Summary: | plasma-desktop crashes repeatedly [QListData::remove, takeAt, Akonadi::EntityTreeModelPrivate::monitoredItemRemoved, CalendarSupport::CalendarModel::*] | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Thomas Tanghus <thomas> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andreas.hencke, andresbajotierra, ar_howard, eric, greg, gregpitta19, iprmaster, proog, sebas.rau, t.kijas, thomas, tian.tian098 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Thomas Tanghus
2011-08-01 22:21:26 UTC
fwiw plasma-desktop hasn't crashed since I removed the CalDAV resources. Hi Thomas, Have you found a way to replicate this issue? Were items removed on the server before the crash? Have you deleted items locally? Apparently the dav resource is doing something wrong, but this is going a little too far in Akonadi's internals to diagnose by just looking at a BT (at least for me), so I'd like to replicate this to debug. Cheers, Grégory (In reply to comment #2) > Have you found a way to replicate this issue? Were items removed on the server > before the crash? Have you deleted items locally? Nothing should have happened serverside. I might have added event(s) to KOrganizer which would then have been synced to memotoo.com via the traditional Calendar in remote file resource. BTW: the two CalDAV resources where disabled (not checked in KOrganizer) when the crashes occurred. > Apparently the dav resource is doing something wrong, but this is going a > little too far in Akonadi's internals to diagnose by just looking at a BT (at > least for me), so I'd like to replicate this to debug. As it took a while (several logins/reboots) for the crash to appear it might take a while to see if I can reproduce it. I'll add the CalDAV resources one by one and wait to see what happens :-) Created attachment 62736 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2
- What I was doing when the application crashed:
I was away from the box but had Kontact open and KMail would have checked for mail during that time. One thing I did change was that I had earlier today removed and readded an Akonadi IMAP ressource for Gmail because it had stopped fetching new mails.
One KAlarm was triggered but that isn't even Akonadified yet? Basically I have no idea what triggered it.
-- Backtrace (Reduced):
#15 0x01a9ed73 in KJob::result (this=0xbf1d058, _t1=0xbf1d058) at ./kjob.moc:194
#16 0x01a9edc8 in KJob::emitResult (this=0xbf1d058) at ../../kdecore/jobs/kjob.cpp:312
#17 0x06c29eae in Akonadi::JobPrivate::handleResponse (this=0xb2ed010, tag=..., data=...) at ../../akonadi/job.cpp:66
#18 0x06c603d7 in Akonadi::SessionPrivate::dataReceived (this=0xa30cc48) at ../../akonadi/session.cpp:218
#19 0x06c63206 in Akonadi::Session::qt_metacall (this=0x9edcfe0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfaa4bfc) at ./session.moc:96
Created attachment 63071 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2
- What I was doing when the application crashed:
Same as last time - nothing ;-)
Sorry that I can't give any better feedback. I had Kontact running, the same resources configured. I really don't know how to reproduce it. The intervals can be 2 minutes or 2 weeks.
Now I will remove the CalDAV resources which I suppose is the reason for the crash. Feel free to suggest any other way I can give better feedback.
I haven't done any C++ programming for 15 years, but isn't it possible to catch an exception (or whatever it's called; I only do Python now) and fail a bit more graceful?
-- Backtrace (Reduced):
#15 0x029aed73 in KJob::result (this=0xba4e7f8, _t1=0xba4e7f8) at ./kjob.moc:194
#16 0x029aedc8 in KJob::emitResult (this=0xba4e7f8) at ../../kdecore/jobs/kjob.cpp:312
#17 0x081bfeae in Akonadi::JobPrivate::handleResponse (this=0xb648f60, tag=..., data=...) at ../../akonadi/job.cpp:66
#18 0x081f63d7 in Akonadi::SessionPrivate::dataReceived (this=0xa1cf620) at ../../akonadi/session.cpp:218
#19 0x081f9206 in Akonadi::Session::qt_metacall (this=0xa4fe970, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfb25abc) at ./session.moc:96
*** Bug 282498 has been marked as a duplicate of this bug. *** [Comment from a bug triager] From bug 283111 (KDE SC 4.7.1): "plasma crash during google calendar refresh in kontact." - What I was doing when the application crashed: refreshing the calendar. - Custom settings of the application: set calendar in kontact to sync with google calendar using kdepim. on refresh, plasma desktop crashes. either refreshing the calendar manual or automatic (every 5 minutes as default) will cause the crash. *** Bug 283111 has been marked as a duplicate of this bug. *** *** Bug 284223 has been marked as a duplicate of this bug. *** I have the same problem with adding ang synchronising google calendar, plasma crashes. I had some crashes again using CalDAV/CardDAV resources against an ownCloud instance. Will test some more. Maybe I can get some server error logs and see if there's a pattern there. *** Bug 285777 has been marked as a duplicate of this bug. *** *** Bug 285571 has been marked as a duplicate of this bug. *** *** Bug 285471 has been marked as a duplicate of this bug. *** *** Bug 280916 has been marked as a duplicate of this bug. *** *** Bug 286990 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 279322 *** |