Bug 284551 - korganizer crash when adding Zimbra account
Summary: korganizer crash when adding Zimbra account
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: DAV Resource (show other bugs)
Version: 4.7
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-20 14:34 UTC by Jeffrey Bastian
Modified: 2011-10-31 17:03 UTC (History)
1 user (show)

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 Jeffrey Bastian 2011-10-20 14:34:41 UTC
Application: akonadi_davgroupware_resource (4.7)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.8.0
Operating System: Linux 3.1.0-0.rc9.git0.0.fc16.x86_64 x86_64
Distribution: "Fedora release 16 (Verne)"

-- Information about the crash:
- What I was doing when the application crashed:
I was doing the intial setup for KOrganizer and it crashed as soon as I finished configuring it for my Zimbra CalDAV and ContactDAV account.

-- Backtrace:
Application: Zimbra of type DAV groupware resource (akonadi_davgroupware_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x0000003d7da362c5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x0000003d7da37bdb in __GI_abort () at abort.c:91
#8  0x0000003d81ebbfbd in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x0000003d81eba176 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x0000003d81eba1a3 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:50
#11 0x0000003d81eba2e6 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x0000003d89f7715c in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:218
#13 0x0000003d89f7b8c5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#14 0x0000003d8cf4c426 in Akonadi::ResourceBase::init (r=0x1c36f80) at /usr/src/debug/kdepimlibs-4.7.2/akonadi/resourcebase.cpp:393
#15 0x0000000000439816 in int Akonadi::ResourceBase::init<DavGroupwareResource>(int, char**) ()
#16 0x0000003d7da2169d in __libc_start_main (main=0x410740, argc=3, ubp_av=0x7ffff4cf39f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff4cf39e8) at libc-start.c:226
#17 0x0000000000410771 in _start ()

Possible duplicates by query: bug 284524, bug 284453, bug 284369, bug 284280, bug 284118.

Reported using DrKonqi
Comment 1 Grégory Oestreicher 2011-10-29 17:51:26 UTC
Hi,

Can you check in your ~/.xsession-errors for errors like 'MimeType tree is not a DAG'?

Cheers,
Grégory
Comment 2 Jeffrey Bastian 2011-10-31 17:03:02 UTC
I've tried multiple times to reproduce this and unfortunately (or fortunately!) it has not crashed again.  I've removed and re-added my calendar, and I've tried both MySQL and SQLite backends for Akonadi, and it's all working fine now.

I guess I'll close this as WORKSFORME now and, if I manage to reproduce it, I'll re-open it.

The only MIME messages in my ~/.xsession-errors are:

checking table  "MimeTypeTable" 
checking relation  "CollectionMimeTypeRelation" 
akonadi.collectionmimetyperelation                 OK
akonadi.mimetypetable                              OK
checking table  "MimeTypeTable" 
checking relation  "CollectionMimeTypeRelation"