Bug 156991 - assertion !transferInProgress( serNum ) failed
Summary: assertion !transferInProgress( serNum ) failed
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: SVN trunk (KDE 4)
Platform: Compiled Sources All
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 166024 169471 176690 179632 182649 196930 197241 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-30 22:59 UTC by Oliver Putz
Modified: 2012-08-19 10:54 UTC (History)
15 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kontact-crash.txt (2.71 KB, application/octet-stream)
2009-01-05 11:33 UTC, Luka Renko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Putz 2008-01-30 22:59:44 UTC
Version:           1.9.50 (using 4.00.60 (KDE 4.0.60 >= 20080129), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.23-gentoo-r3

Steps to reproduce:

1) save mail
2) right click on mail -> open with -> other -> type "kmail"
3) Save mail in Draft folder (is on IMAP account)
4) You are asked for username / password of the IMAP account
5) Hit "Cancel" on that popup twice
6) See kmail crash with the following backtrace:

Application: KMail (kmail), signal SIGABRT
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb4ad36d0 (LWP 21649)]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb50931f1 in *__GI_raise (sig=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0xb50949b8 in *__GI_abort () at abort.c:88
#9  0xb7dd8265 in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbf9e6e8c "ASSERT: \"!transferInProgress( serNum )\" in file /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/messageproperty.cpp, line 164") at global/qglobal.cpp:2160
#10 0xb7dd832a in qFatal (msg=0xb7edf87c "ASSERT: \"%s\" in file %s, line %d")
    at global/qglobal.cpp:2392
#11 0xb7dd8555 in qt_assert (
    assertion=0xb7963c41 "!transferInProgress( serNum )", 
    file=0xb7963bec "/var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/messageproperty.cpp", line=164) at global/qglobal.cpp:1917
#12 0xb76fdea1 in KMail::MessageProperty::forget (msgBase=0x841ac80)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/messageproperty.cpp:164
#13 0xb77483bd in ~KMMsgBase (this=0x841ac80)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmmsgbase.cpp:88
#14 0xb760e215 in ~KMMessage (this=0x841ac80)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmmessage.cpp:216
#15 0xb7748d13 in KMMsgList::clear (this=0x820863c, doDelete=true, 
    syncDict=false)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmmsglist.cpp:41
#16 0xb77978ea in KMFolderMaildir::close (this=0x82085e8, aForced=true)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmfoldermaildir.cpp:258
#17 0xb76d5666 in KMFolder::close (this=0x81fb028, 
    owner=0xb7976a19 "kmkernel", force=true)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmfolder.cpp:502
#18 0xb77a835b in KMKernel::cleanup (this=0xbf9e9030)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmkernel.cpp:1617
#19 0x0804a8e8 in main (argc=)
    at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/main.cpp:133
#20 0xb507ffdc in __libc_start_main (main=0x804a720 <main>, argc=4, 
    ubp_av=0xbf9e91c4, init=0x804af60 <__libc_csu_init>, 
    fini=0x804af50 <__libc_csu_fini>, rtld_fini=0xb7f6e100 <_dl_fini>, 
    stack_end=0xbf9e91bc) at libc-start.c:229
#21 0x0804a021 in _start ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Thomas McGuire 2008-02-04 18:15:08 UTC
Same backtrace as in bug 156293.
Before posting crash reports, please check if you've already reported a bug with the same backtrace.

*** This bug has been marked as a duplicate of 156293 ***
Comment 2 Thomas McGuire 2008-02-10 19:04:02 UTC
Hmm, I think this one is a different bug after all.
Comment 3 Oliver Putz 2008-03-19 01:56:59 UTC
Still valid in a current SVN version
Comment 4 Jarosław Staniek 2008-05-06 21:24:25 UTC
Still valid in a current SVN version, also on Windows.
Comment 5 Christophe Marin 2008-07-08 12:42:31 UTC
*** Bug 166024 has been marked as a duplicate of this bug. ***
Comment 6 Dirk Mueller 2008-08-20 12:05:13 UTC
*** Bug 169471 has been marked as a duplicate of this bug. ***
Comment 7 Dirk Mueller 2008-08-20 12:05:43 UTC
I can confirm this crash, happens quite frequently
Comment 8 Jaime Torres 2008-11-11 16:34:11 UTC
*** Bug 174816 has been marked as a duplicate of this bug. ***
Comment 9 Jaime Torres 2008-12-01 17:25:27 UTC
*** Bug 176571 has been marked as a duplicate of this bug. ***
Comment 10 Oliver Putz 2008-12-02 12:45:57 UTC
*** Bug 176690 has been marked as a duplicate of this bug. ***
Comment 11 Luka Renko 2008-12-10 11:58:13 UTC
I get this crash at least couple of times per day if I use Disconnected IMAP. Did not see this when using regular IMAP (on same MS Exchange 2003 IMAP server).

I am running up-to-date KDE 4.2 from SVN. Is there anything I can do to help fix this problem? 
Comment 12 Luka Renko 2009-01-05 11:33:34 UTC
Created attachment 29924 [details]
kontact-crash.txt

With recent SVN, I get a bit less of crashes (one per week), but I still get some.
Mostly it looks like it is related with large operations. 
Last crash (today) happened when I did "Move all messages to Trash" on my Junk Mail folder.
After restart, Junk mail folder was empty (local dimap cache), but was filled with all e-mails after sync with IMAP server (MS Exchange 2003).
Comment 13 Jaime Torres 2009-01-08 10:11:41 UTC
*** Bug 179632 has been marked as a duplicate of this bug. ***
Comment 14 Daniel Franke 2009-01-21 20:43:46 UTC
Same backtrace here (v4.1.4) when closing Kontact during send operation (disconnected IMAP).
Comment 15 Daniel Franke 2009-01-22 23:13:48 UTC
Addition to comment #14:
I never got this crash with 4.1.2 or 4.1.3, but since the first crash yesterday on 4.1.4, I get this quite regularly now. Even if the machine is unattended and kmail is only supposed to check for mail every now and then. Argh!
Comment 16 Christophe Marin 2009-02-01 14:36:19 UTC
*** Bug 182649 has been marked as a duplicate of this bug. ***
Comment 17 FiNeX 2009-04-03 10:26:29 UTC
I'm not able to reproduce it: on step 3 (Save mail in Draft folder on the IMAP) the mail il saved and no password are asked. Kmail is still running and there is no crash.
Comment 18 Martin Fitzpatrick 2009-04-04 02:45:44 UTC
Cannot reproduce on KDE 4.2.2 (Kubuntu). As for FiNeX saving to the IMAP Draft folder does not ask for password, saves normally, no crash.
Comment 19 FiNeX 2009-04-04 11:03:07 UTC
Thanks for double checking Martin.
Comment 20 Jonathan Thomas 2009-05-19 14:24:28 UTC
We have received a report about this crash at https://launchpad.net/bugs/378232 in regards to KDE 4.2.3.
Steps to reproduce are:
* write a mail with an attachement that is greater than approx 1MB, just to ensure the sending process needs some time.
* click on send, the mail comes into the outbox, kmail/kontact starts sending.
* close Kontact WHILE sending the mail.

Anwendung: Kontact (kontact), Signal SIGABRT
[Current thread is 0 (LWP 4242)]

Thread 2 (Thread 0xab4a2b90 (LWP 4277)):
#0  0xb80ca430 in __kernel_vsyscall ()
#1  0xb5a567b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5d213d0 in QProcessManager::run (this=0x9ab2de8) at io/qprocess_unix.cpp:305
#3  0xb5c4f56e in QThreadPrivate::start (arg=0x9ab2de8) at thread/qthread_unix.cpp:189
#4  0xb52544ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5a5e49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb49709c0 (LWP 4242)):
[KCrash Handler]
#6  0xb80ca430 in __kernel_vsyscall ()
#7  0xb59a56d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb59a7098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb5c471e5 in qt_message_output (msgType=QtFatalMsg, buf=0x9fcdd48 "ASSERT: \"!transferInProgress( serNum )\" in file /build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp, line 180")
    at global/qglobal.cpp:2017
#10 0xb5c472d1 in qFatal (msg=0xb5d960d8 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2216
#11 0xb5c473c5 in qt_assert (assertion=0xb1442c6b "!transferInProgress( serNum )", file=0xb1442c18 "/build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp", line=180) at global/qglobal.cpp:1786
#12 0xb0f73cf0 in KMail::MessageProperty::forget (msgBase=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/messageproperty.cpp:180
#13 0xb0fd87da in ~KMMsgBase (this=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/kmmsgbase.cpp:125
#14 0xb0e37624 in ~KMMessage (this=0xab08ba8) at /build/buildd/kdepim-4.2.3/kmail/kmmessage.cpp:225
#15 0xb0fe1919 in KMMsgList::clear (this=0x9f37c70, doDelete=true, syncDict=false) at /build/buildd/kdepim-4.2.3/kmail/kmmsglist.cpp:37
#16 0xb105741f in KMFolderMaildir::reallyDoClose (this=0x9f37c20) at /build/buildd/kdepim-4.2.3/kmail/kmfoldermaildir.cpp:203
#17 0xb0f60f7d in FolderStorage::close (this=0x6, aForced=146) at /build/buildd/kdepim-4.2.3/kmail/folderstorage.cpp:110
#18 0xb0f2ed06 in KMFolder::close (this=0x9f29538, owner=0xb145d142 "kmkernel", force=<value optimized out>) at /build/buildd/kdepim-4.2.3/kmail/kmfolder.cpp:542
#19 0xb1073803 in KMKernel::cleanup (this=0x9e96840) at /build/buildd/kdepim-4.2.3/kmail/kmkernel.cpp:1678
#20 0xb15d783b in ~KMailPart (this=0x9e43950) at /build/buildd/kdepim-4.2.3/kmail/kmail_part.cpp:141
#21 0xb79660e9 in ~Plugin (this=0x9e1c1b0, __vtt_parm=0x1092) at /build/buildd/kdepim-4.2.3/kontactinterfaces/plugin.cpp:86
#22 0xb1a0776c in ~KMailPlugin (this=0x9e1c1b0) at /build/buildd/kdepim-4.2.3/kontact/plugins/kmail/kmail_plugin.cpp:150
#23 0xb7980fce in ~MainWindow (this=0x9b6bad0) at /build/buildd/kdepim-4.2.3/kontact/src/mainwindow.cpp:271
#24 0xb5d528d5 in qDeleteInEventHandler (o=0x6) at kernel/qobject.cpp:3822
#25 0xb5d5417b in QObject::event (this=0x9b6bad0, e=0xabba6f8) at kernel/qobject.cpp:1101
#26 0xb624b1c0 in QWidget::event (this=0x9b6bad0, event=0xabba6f8) at kernel/qwidget.cpp:7918
#27 0xb6646a07 in QMainWindow::event (this=0x9b6bad0, event=0xabba6f8) at widgets/qmainwindow.cpp:1402
#28 0xb6ef9a67 in KMainWindow::event (this=0x9b6bad0, ev=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/widgets/kmainwindow.cpp:1094
#29 0xb6f3e84c in KXmlGuiWindow::event (this=0x9b6bad0, ev=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/xmlgui/kxmlguiwindow.cpp:131
#30 0xb61f4bcc in QApplicationPrivate::notify_helper (this=0x9ab8330, receiver=0x9b6bad0, e=0xabba6f8) at kernel/qapplication.cpp:4057
#31 0xb61fcfc2 in QApplication::notify (this=0xbfde72a8, receiver=0x9b6bad0, e=0xabba6f8) at kernel/qapplication.cpp:4022
#32 0xb6e15e5d in KApplication::notify (this=0xbfde72a8, receiver=0x9b6bad0, event=0xabba6f8) at /build/buildd/kde4libs-4.2.3/kdeui/kernel/kapplication.cpp:307
#33 0xb5d437ab in QCoreApplication::notifyInternal (this=0xbfde72a8, receiver=0x9b6bad0, event=0xabba6f8) at kernel/qcoreapplication.cpp:610
#34 0xb5d44405 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9a93428) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#35 0xb5d445fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#36 0xb5d6f58f in postEventSourceDispatch (s=0x9ab9ed8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#37 0xb4e26b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0xb4e2a0eb in ?? () from /usr/lib/libglib-2.0.so.0
#39 0xb4e2a268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#40 0xb5d6f1d8 in QEventDispatcherGlib::processEvents (this=0x9a981b8, flags={i = -1075941000}) at kernel/qeventdispatcher_glib.cpp:324
#41 0xb6296765 in QGuiEventDispatcherGlib::processEvents (this=0x9a981b8, flags={i = -1075940952}) at kernel/qguieventdispatcher_glib.cpp:202
#42 0xb5d41dda in QEventLoop::processEvents (this=0xbfde7220, flags={i = -1075940888}) at kernel/qeventloop.cpp:149
#43 0xb5d4221a in QEventLoop::exec (this=0xbfde7220, flags={i = -1075940824}) at kernel/qeventloop.cpp:200
#44 0xb5d446c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#45 0xb61f4a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#46 0x0804c072 in main (argc=1, argv=0xbfde75a4) at /build/buildd/kdepim-4.2.3/kontact/src/main.cpp:218
Comment 21 Jonathan Thomas 2009-05-19 14:29:06 UTC
Oh, and it should be pointed out that in the downstream bug, the reporter said that this only happens with kontact + kmail, and not kmail on its own.
Comment 22 Thiago Macieira 2009-05-19 18:16:31 UTC
Can you ask the reporter if he's using Qt 4.5?

I think it's abug already fixed there.
Comment 23 Jonathan Thomas 2009-05-19 18:53:00 UTC
The repository containing the KDE 4.2 packages also contains Qt 4.5.1 packages, so it is pretty safe to say that he is using Qt 4.5.1 since an upgrade with those repos available would upgrade both Qt and KDE.
Comment 24 Christophe Marin 2009-07-04 15:48:13 UTC
*** Bug 197241 has been marked as a duplicate of this bug. ***
Comment 25 Christophe Marin 2009-07-06 18:17:45 UTC
*** Bug 196930 has been marked as a duplicate of this bug. ***
Comment 26 Gökçen Eraslan 2009-12-16 12:29:18 UTC
I can still reproduce the bug with KDE 4.3.4 and  Qt4.5.3.
Comment 27 Myriam Schweingruber 2012-08-19 10:54:22 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding