kontact crashes when quitting while sending mail

Bug #378232 reported by Christian González
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE PIM
Unknown
High
kdepim (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kontact

using kontact 1.4.3 (kubuntu kde-experimental package 4:4.2.3-0ubuntu1~jaunty1~ppa1), I can reproducible crash kontact when I do the following:

* 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.

What I expect:
Kontact hides it's window, but keeps on sending the mail in the background, or shows me that he is still sending, or at LEAST doesn't send the mail until next time.

What happens:
Kontact crashes (report included)

This does NOT happen with kmail, only in connection with kontact.

Revision history for this message
In , Oliver Putz (regnaron) wrote :

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 ()

Revision history for this message
In , Mcguire-c (mcguire-c) wrote :

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 ***

Revision history for this message
In , Mcguire-c (mcguire-c) wrote :

Hmm, I think this one is a different bug after all.

Revision history for this message
In , Oliver Putz (regnaron) wrote :

Still valid in a current SVN version

Revision history for this message
In , Jaroslaw Staniek (staniek) wrote :

Still valid in a current SVN version, also on Windows.

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

*** Bug 166024 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Mueller-kde (mueller-kde) wrote :

*** Bug 169471 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Mueller-kde (mueller-kde) wrote :

I can confirm this crash, happens quite frequently

Revision history for this message
In , Jtamate (jtamate) wrote :

*** Bug 174816 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Jtamate (jtamate) wrote :

*** Bug 176571 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Oliver Putz (regnaron) wrote :

*** Bug 176690 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Luka Renko (lure) wrote :

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?

Revision history for this message
In , Luka Renko (lure) wrote :

Created attachment 29924
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).

Revision history for this message
In , Jtamate (jtamate) wrote :

*** Bug 179632 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Daniel Franke (franke-daniel) wrote :

Same backtrace here (v4.1.4) when closing Kontact during send operation (disconnected IMAP).

Revision history for this message
In , Daniel Franke (franke-daniel) wrote :

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!

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

*** Bug 182649 has been marked as a duplicate of this bug. ***

Revision history for this message
In , FiNeX (finex) wrote :

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.

Revision history for this message
In , Martin Fitzpatrick (mfitzp) wrote :

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.

Revision history for this message
In , FiNeX (finex) wrote :

Thanks for double checking Martin.

Revision history for this message
Christian González (droetker) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugs.kde.org/show_bug.cgi?id=156991

Changed in kdepim (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
In , Jonathan Thomas (echidnaman) wrote :
Download full text (5.5 KiB)

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=0xabba...

Read more...

Revision history for this message
In , Jonathan Thomas (echidnaman) wrote :

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.

Revision history for this message
In , Thiago Macieira (thiago-kde) wrote :

Can you ask the reporter if he's using Qt 4.5?

I think it's abug already fixed there.

Revision history for this message
In , Jonathan Thomas (echidnaman) wrote :

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.

Changed in kdepim:
status: Unknown → Confirmed
Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

*** Bug 197241 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

*** Bug 196930 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Gökçen Eraslan (gkcn) wrote :

I can still reproduce the bug with KDE 4.3.4 and Qt4.5.3.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing in favor of KDE bug report, please refer there for updates. Thanks.

Changed in kdepim (Ubuntu):
status: Triaged → Invalid
Changed in kdepim:
importance: Unknown → High
Revision history for this message
In , Myriam Schweingruber (myriam) wrote :

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

Changed in kdepim:
status: Confirmed → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.