Bug 229936 - kmail-editor crashed after sending; the e-mail has actually been sent correctly
Summary: kmail-editor crashed after sending; the e-mail has actually been sent correctly
Status: RESOLVED DUPLICATE of bug 218974
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-08 12:38 UTC by knurz
Modified: 2010-03-14 01:17 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 knurz 2010-03-08 12:38:12 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-generic i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7875aa0 (LWP 4710))]

Thread 3 (Thread 0xb3741b70 (LWP 4751)):
#0  0x005ab422 in __kernel_vsyscall ()
#1  0x0113d142 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0x082d98d4 in __pthread_cond_timedwait (cond=0x98ca470, mutex=0x98ca458, abstime=0xb37412d0) at forward.c:152
#3  0x03a369ff in ?? () from /usr/lib/libxine.so.1
#4  0x0113880e in start_thread (arg=0xb3741b70) at pthread_create.c:300
#5  0x082cc8de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xb2f40b70 (LWP 4752)):
#0  0x089e2e06 in *__GI_clock_gettime (clock_id=144601076, tp=0xb2f3ff98) at ../sysdeps/unix/clock_gettime.c:100
#1  0x07279bf3 in QTimerInfoList::getTime (this=0x975fd8c, t=...) at kernel/qeventdispatcher_unix.cpp:339
#2  0x07279de1 in QTimerInfoList::updateCurrentTime (this=0x975fd8c) at kernel/qeventdispatcher_unix.cpp:297
#3  0x0727a88c in QTimerInfoList::timerWait (this=0x975fd8c, tm=...) at kernel/qeventdispatcher_unix.cpp:420
#4  0x07278210 in timerSourcePrepare (source=0x975fd58, timeout=0xb2f4008c) at kernel/qeventdispatcher_glib.cpp:141
#5  0x07ddcf90 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#6  0x07ddd351 in ?? () from /lib/libglib-2.0.so.0
#7  0x07ddd863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#8  0x07278067 in QEventDispatcherGlib::processEvents (this=0x974c780, flags=...) at kernel/qeventdispatcher_glib.cpp:329
#9  0x0724bc79 in QEventLoop::processEvents (this=0xb2f40254, flags=) at kernel/qeventloop.cpp:149
#10 0x0724c0ca in QEventLoop::exec (this=0xb2f40254, flags=...) at kernel/qeventloop.cpp:201
#11 0x07159b73 in QThread::exec (this=0x8d36970) at thread/qthread.cpp:487
#12 0x04f5620a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#13 0x0715ce32 in QThreadPrivate::start (arg=0x8d36970) at thread/qthread_unix.cpp:188
#14 0x0113880e in start_thread (arg=0xb2f40b70) at pthread_create.c:300
#15 0x082cc8de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7875aa0 (LWP 4710)):
[KCrash Handler]
#6  0x00933f3a in KMMessage::transferInProgress (this=0x98702e8) at ../../kmail/kmmessage.cpp:270
#7  0x00af0147 in KMAcctImap::killAllJobs (this=0x8d06428, disconnectSlave=true) at ../../kmail/kmacctimap.cpp:161
#8  0x00af070f in ~KMAcctImap (this=0x8d06428, __in_chrg=<value optimized out>) at ../../kmail/kmacctimap.cpp:86
#9  0x00a7210e in qDeleteAll<QList<KMAccount*>::const_iterator> (this=0x8d19268, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:350
#10 qDeleteAll<AccountList> (this=0x8d19268, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qalgorithms.h:358
#11 ~AccountManager (this=0x8d19268, __in_chrg=<value optimized out>) at ../../kmail/accountmanager.cpp:39
#12 0x00b5e541 in KMKernel::cleanup (this=0xbfea7b3c) at ../../kmail/kmkernel.cpp:1758
#13 0x0804a70c in main (argc=2, argv=0xbfea7db4) at ../../kmail/main.cpp:148
The current source language is "auto; currently c".

This bug may be a duplicate of or related to bug 201701

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-03-14 01:17:16 UTC

*** This bug has been marked as a duplicate of bug 218974 ***