Application: accountwizard (0.1) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-14-generic-pae i686 Distribution: Ubuntu 11.10 -- Information about the crash: I entered the account details with a single IMAP mail server. The wizard reported that it couldn't contact the server (probably quite true, network is flaky) and then crashed. -- Backtrace: Application: Account Assistant (accountwizard), signal: Aborted [Current thread is 1 (Thread 0xb484f710 (LWP 3913))] Thread 3 (Thread 0xb1931b70 (LWP 3924)): #0 0xb773f424 in __kernel_vsyscall () #1 0xb59b440e in __GI___poll (fds=0x9b0c0a8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb4f0c34b in g_poll (fds=0x9b0c0a8, nfds=1, timeout=-1) at /build/buildd/glib2.0-2.30.0/./glib/gpoll.c:132 #3 0xb4efd896 in g_main_context_poll (n_fds=1, fds=0x9b0c0a8, timeout=<optimized out>, context=0x9b03b48, priority=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3402 #4 g_main_context_iterate (context=0x9b03b48, block=-1259289824, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3084 #5 0xb4efdc2a in g_main_context_iteration (context=0x9b03b48, may_block=1) at /build/buildd/glib2.0-2.30.0/./glib/gmain.c:3152 #6 0xb5d0ab37 in QEventDispatcherGlib::processEvents (this=0x9ad4ef8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0xb5cdb1dd in QEventLoop::processEvents (this=0xb19312b0, flags=...) at kernel/qeventloop.cpp:149 #8 0xb5cdb421 in QEventLoop::exec (this=0xb19312b0, flags=...) at kernel/qeventloop.cpp:201 #9 0xb5bde90b in QThread::exec (this=0x9b025d0) at thread/qthread.cpp:498 #10 0xb5cbbe2d in QInotifyFileSystemWatcherEngine::run (this=0x9b025d0) at io/qfilesystemwatcher_inotify.cpp:248 #11 0xb5be17b3 in QThreadPrivate::start (arg=0x9b025d0) at thread/qthread_unix.cpp:331 #12 0xb566ad31 in start_thread (arg=0xb1931b70) at pthread_create.c:304 #13 0xb59c30ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb089ab70 (LWP 3936)): #0 0xb773f424 in __kernel_vsyscall () #1 0xb566ea5c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169 #2 0xb59d0cfc in __pthread_cond_wait (cond=0xb5600a50, mutex=0xb5600a38) at forward.c:139 #3 0xb54fb9a9 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0xb55fb960) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0xb54fb9ef in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0xb55fb960) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0xb566ad31 in start_thread (arg=0xb089ab70) at pthread_create.c:304 #6 0xb59c30ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb484f710 (LWP 3913)): [KCrash Handler] #7 0xb773f424 in __kernel_vsyscall () #8 0xb591ec8f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0xb59222b5 in __GI_abort () at abort.c:92 #10 0xb5b3c4ed in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95 #11 0xb5b3a283 in __cxxabiv1::__terminate (handler=0xb5b3c3a0 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:40 #12 0xb5b3a2bf in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:50 #13 0xb5b3a464 in __cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116 #14 0xb5cdb569 in QEventLoop::exec (this=0xbfcdbc34, flags=...) at kernel/qeventloop.cpp:214 #15 0xb5ce019d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #16 0xb64d98f4 in QApplication::exec () at kernel/qapplication.cpp:3760 #17 0x080746a3 in main (argc=) at ../../accountwizard/main.cpp:76 Possible duplicates by query: bug 287966, bug 286203, bug 285381, bug 284551, bug 284118. 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.