[Bug 304593] kmail starts in offline-mode, when akonadi is not running

Franz Fellner alpine.art.de at googlemail.com
Sat Aug 11 09:26:48 BST 2012


https://bugs.kde.org/show_bug.cgi?id=304593

--- Comment #1 from Franz Fellner <alpine.art.de at googlemail.com> ---
Additionally KMail crashes when closing when in offline mode:

Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f87d1e1f780 (LWP 3872))]

Thread 4 (Thread 0x7f87b6ef5700 (LWP 3873)):
#0  0x00007f87cf14cf23 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f87cfa76391 in QProcessManager::run (this=0x7f87cfded4a0) at
io/qprocess_unix.cpp:245
#2  0x00007f87cf99fc3b in QThreadPrivate::start (arg=0x7f87cfded4a0) at
thread/qthread_unix.cpp:307
#3  0x00007f87ccf49e2c in start_thread () from /lib64/libpthread.so.0
#4  0x00007f87cf1534ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7f87b4f63700 (LWP 3889)):
#0  0x00007f87ccf4dd6c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007f87c367134c in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/qt4/libQtWebKit.so.4
#2  0x00007f87c3671479 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x00007f87ccf49e2c in start_thread () from /lib64/libpthread.so.0
#4  0x00007f87cf1534ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f87b2308700 (LWP 3967)):
#0  0x00007f87ccf4e0eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007f87cf9a009f in wait (time=30000, this=0x4160f10) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x4162458, time=30000) at
thread/qwaitcondition_unix.cpp:158
#3  0x00007f87cf993f8f in QThreadPoolThread::run (this=0x4161f80) at
concurrent/qthreadpool.cpp:141
#4  0x00007f87cf99fc3b in QThreadPrivate::start (arg=0x4161f80) at
thread/qthread_unix.cpp:307
#5  0x00007f87ccf49e2c in start_thread () from /lib64/libpthread.so.0
#6  0x00007f87cf1534ad in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f87d1e1f780 (LWP 3872)):
[KCrash Handler]
#6  0x00007f87c7fb6902 in lockInline (this=0xf5c518) at
/usr/include/qt4/QtCore/qmutex.h:187
#7  QMutexLocker (m=0xf5c518, this=<synthetic pointer>) at
/usr/include/qt4/QtCore/qmutex.h:109
#8  Nepomuk::Resource::~Resource (this=0x7f87ac0242e0, __in_chrg=<optimized
out>) at
/var/tmp/paludis/kde-base-kdelibs-4.9.0/work/kdelibs-4.9.0/nepomuk/core/resource.cpp:142
#9  0x00007f87c7fb6b89 in Nepomuk::Resource::~Resource (this=0x7f87ac0242e0,
__in_chrg=<optimized out>) at
/var/tmp/paludis/kde-base-kdelibs-4.9.0/work/kdelibs-4.9.0/nepomuk/core/resource.cpp:147
#10 0x00007f87cfaac039 in QMetaCallEvent::~QMetaCallEvent (this=0x7f87ac0247d0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:509
#11 0x00007f87cfaac099 in QMetaCallEvent::~QMetaCallEvent (this=0x7f87ac0247d0,
__in_chrg=<optimized out>) at kernel/qobject.cpp:518
#12 0x00007f87cfa9dd89 in QCoreApplicationPrivate::~QCoreApplicationPrivate
(this=0x98dc70, __in_chrg=<optimized out>) at kernel/qcoreapplication.cpp:449
#13 0x00007f87cffc7c99 in QApplicationPrivate::~QApplicationPrivate
(this=0x98dc70, __in_chrg=<optimized out>) at kernel/qapplication.cpp:223
#14 0x00007f87cfab4240 in cleanup (pointer=<optimized out>) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#15 ~QScopedPointer (this=0x7fff88da53f8, __in_chrg=<optimized out>) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#16 QObject::~QObject (this=0x7fff88da53f0, __in_chrg=<optimized out>) at
kernel/qobject.cpp:817
#17 0x00007f87cffc77f7 in QApplication::~QApplication (this=0x7fff88da53f0,
__in_chrg=<optimized out>) at kernel/qapplication.cpp:1095
#18 0x000000000040307b in main (argc=<optimized out>, argv=<optimized out>) at
/var/tmp/paludis/kde-base-kmail-4.9.0/work/kmail-4.9.0/kmail/main.cpp:149

I configured my IMAP-Accounts to be offline when kmail is not running, mainly
because that's the easiest solution to "fix" kdebug #257722 (which is still
present in kde-4.9.0).

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list