Summary: | Crash of the IMAP resource (Akonadi::Entity::Entity, assignEntityPrivate) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | LuHe <lukas.hetzenecker> |
Component: | libakonadi | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | abychko, achim.herwig, andreas.hencke, b7792105, bartoschek, bz-acc, cfeck, christopherheiny, ecs.eco, faure, info, jgorkos, kai, kb, kde-bugreport, kdepim-bugs, leggis, lothar, luis.davila.pc, mail.rage, mhaindl, pcn, radu_cs85, renda.krell, richarddevries, rkayondo, roemer-lilienthal, romanhppi, sebelk, sorcieredordinateur, spearhead2k3, thomas, vkrause |
Priority: | NOR | ||
Version: | 4.9 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
LuHe
2010-10-02 16:05:47 UTC
I can't reproduce this bug in kde 4.6 beta 1, on openSuse 11.4 Milestone 4. It might have been fixed. *** Bug 259924 has been marked as a duplicate of this bug. *** Created attachment 55976 [details]
New crash information added by DrKonqi
akonadi_imap_resource (0.1) on KDE Platform 4.6.41 (4.7 >= 20110106) using Qt 4.7.1
- What I was doing when the application crashed:
start with IMAP gmail disconnected account, only 1 fail of 3 account, same config for 3 accounts. In my INBOX of fail account I have "nothing" even that is marked like i have e-mails (with another email reader there's no problem to read that INBOX).
- Custom settings of the application:
IMAP disconnected gmail account, with KDE snapshot 4.6.41
-- Backtrace (Reduced):
#7 QSharedDataPointer (one=..., other=...) at /usr/include/QtCore/qshareddata.h:93
#8 assignEntityPrivate (one=..., other=...) at /home/build/build/i686/kdepimlibs/src/kdepimlibs/akonadi/entity.cpp:49
#9 0xb75d0b2a in Akonadi::Entity::Entity (this=0xbfac176c, other=...) at /home/build/build/i686/kdepimlibs/src/kdepimlibs/akonadi/entity.cpp:56
#10 0xb75fe6f4 in Akonadi::Collection::Collection (this=0xbfac176c, other=...) at /home/build/build/i686/kdepimlibs/src/kdepimlibs/akonadi/collection.cpp:72
#11 0x080654b2 in ImapResource::onIdleCollectionFetchDone (this=0x8cc9550, job=0x8e49170) at /home/build/build/i686/kdepim/src/kdepim/runtime/resources/imap/imapresource.cpp:503
*** Bug 275893 has been marked as a duplicate of this bug. *** *** Bug 266108 has been marked as a duplicate of this bug. *** *** Bug 280149 has been marked as a duplicate of this bug. *** *** Bug 280961 has been marked as a duplicate of this bug. *** Is it still happening for you with 4.7.x? I've been unable to reproduce that one, it just works for me. In case you still experience this please feel free to reopen. In such a case, we would need much more information like the actual IMAP server used and so on. In that report it is actually unclear if the problem happens on the GMail or Exchange resource. Regarding GMail, there's an actual bug (bug:258635 but with different symptom) patch is coming, but apart from that I could download 40k from several folders just fine and read them. Well, the last two duplicates are from 4.7, so it is still happening. It obviously (as the last duplicate shows) crashes for me with 4.7.x, the current, still crashing version, is 4.7.1. The IMAP server i'm using is cyrus imapd 2.3.16. I have 3 accounts simultanously on the server and the only account crashing is the one providing kolab resources (calendar, contacts, notes). Created attachment 64005 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4
- What I was doing when the application crashed:
system login -> entered kwallet password -> akonadi resource crashed. actually
actually, gmail account in kmail settings has "can't start" state. so, unable to sync imap folders
-- Backtrace (Reduced):
#7 0x00007f08057eb064 in Akonadi::Entity::Entity(Akonadi::Entity const&) () from /usr/lib64/libakonadi-kde.so.4
#8 0x000000000041bcc6 in ImapResource::onIdleCollectionFetchDone (this=0x13f35f0, job=<optimized out>) at /var/tmp/portage/kde-base/kdepim-runtime-4.7.1/work/kdepim-runtime-4.7.1/resources/imap/imapresource.cpp:504
#9 0x000000000041c445 in ImapResource::qt_metacall (this=0x13f35f0, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fff3e840f60) at /var/tmp/portage/kde-base/kdepim-runtime-4.7.1/work/kdepim-runtime-4.7.1_build/resources/imap/imapresource.moc:135
[...]
#11 0x00007f0802082bc2 in KJob::result(KJob*) () from /usr/lib64/libkdecore.so.5
#12 0x00007f0802082c00 in KJob::emitResult() () from /usr/lib64/libkdecore.so.5
> In case you still experience this please feel free to reopen. In such a case,
> we would need much more information like the actual IMAP server used and so on.
> In that report it is actually unclear if the problem happens on the GMail or
> Exchange resource.
I can't reopen, please someone being authorized to do so please reopen this bug. I'll gladly provide more information, as long as this will be resolved rather sooner than later, since it is really annoying.
it works for me for several days after deleting gmail imap account and re-creating *** Bug 283341 has been marked as a duplicate of this bug. *** Created attachment 65001 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
I used the wizard to set up KMail for Gmail. This produced this bug. I then tried several other things, like removing the account and setting it up manually. Sometimes it fetches all mail headers, sometimes it doesn't, but it crashes everytime. After the crash, KMail shows the mailheaders it has retrieved, but it won't fetch the content or update mail folders. It just does nothing (no error messages, for example).
I should perhaps add that I installed Kubuntu from the mac-iso.
-- Backtrace (Reduced):
#6 QSharedDataPointer (o=..., this=0x7fffd50ecee0) at /usr/include/qt4/QtCore/qshareddata.h:93
#7 assignEntityPrivate (one=..., other=...) at ../../akonadi/entity.cpp:49
#8 0x00007f7ca7979934 in Akonadi::Entity::Entity (this=<optimized out>, other=<optimized out>) at ../../akonadi/entity.cpp:56
#9 0x000000000041959f in ImapResource::onIdleCollectionFetchDone (this=0x90dba0, job=0xb590d0) at ../../../resources/imap/imapresource.cpp:504
#10 0x000000000041a235 in ImapResource::qt_metacall (this=0x90dba0, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fffd50ed0e0) at ./imapresource.moc:135
*** Bug 258430 has been marked as a duplicate of this bug. *** *** Bug 264994 has been marked as a duplicate of this bug. *** (In reply to comment #15) > Created an attachment (id=65001) [details] > New crash information added by DrKonqi > > akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 > > - What I was doing when the application crashed: > > I used the wizard to set up KMail for Gmail. This produced this bug. I then > tried several other things, like removing the account and setting it up > manually. Sometimes it fetches all mail headers, sometimes it doesn't, but it > crashes everytime. After the crash, KMail shows the mailheaders it has > retrieved, but it won't fetch the content or update mail folders. It just does > nothing (no error messages, for example). > I should perhaps add that I installed Kubuntu from the mac-iso. > > -- Backtrace (Reduced): > #6 QSharedDataPointer (o=..., this=0x7fffd50ecee0) at > /usr/include/qt4/QtCore/qshareddata.h:93 > #7 assignEntityPrivate (one=..., other=...) at ../../akonadi/entity.cpp:49 > #8 0x00007f7ca7979934 in Akonadi::Entity::Entity (this=<optimized out>, > other=<optimized out>) at ../../akonadi/entity.cpp:56 > #9 0x000000000041959f in ImapResource::onIdleCollectionFetchDone > (this=0x90dba0, job=0xb590d0) at ../../../resources/imap/imapresource.cpp:504 > #10 0x000000000041a235 in ImapResource::qt_metacall (this=0x90dba0, > _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0x7fffd50ed0e0) at > ./imapresource.moc:135 After trying a few times more, I got my gmail-account to work. I have no idea as to what I did right this time, or whether some component was updated resolving the issue. 'Interval mail checking' is not working, though; I have to manually check my mail. This may be an unrelated issue, of course. *** Bug 288785 has been marked as a duplicate of this bug. *** *** Bug 290342 has been marked as a duplicate of this bug. *** *** Bug 290134 has been marked as a duplicate of this bug. *** *** Bug 282060 has been marked as a duplicate of this bug. *** *** Bug 283593 has been marked as a duplicate of this bug. *** *** Bug 292983 has been marked as a duplicate of this bug. *** *** Bug 293311 has been marked as a duplicate of this bug. *** *** Bug 297038 has been marked as a duplicate of this bug. *** *** Bug 294453 has been marked as a duplicate of this bug. *** *** Bug 293820 has been marked as a duplicate of this bug. *** *** Bug 299330 has been marked as a duplicate of this bug. *** *** Bug 301006 has been marked as a duplicate of this bug. *** *** Bug 301110 has been marked as a duplicate of this bug. *** *** Bug 284022 has been marked as a duplicate of this bug. *** *** Bug 306555 has been marked as a duplicate of this bug. *** Confirmed by duplicates. Did anyone reproduce this crash with kdepim-runtime 4.9 ? Yes, I just verified (i Kmail, by trying to save a new mail as a draft), that the bug is still alive and kicking and easy to reproduce. This was done on a Kubuntu 12:10 Beta 1 system. % dpkg -l kmail ii kmail 4:4.9.1-0ubuntu1 amd64 full featured graphical email client *** Bug 308691 has been marked as a duplicate of this bug. *** *** Bug 331499 has been marked as a duplicate of this bug. *** *** Bug 338338 has been marked as a duplicate of this bug. *** 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. |