Bug 220178 - Kmail crashed when quitting
Summary: Kmail crashed when quitting
Status: RESOLVED DUPLICATE of bug 199375
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: 2009-12-26 22:43 UTC by Magnus Johansson
Modified: 2009-12-28 00:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Johansson 2009-12-26 22:43:21 UTC 
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.30.5-mactelpatches-macbook-core2duo i686

What I was doing when the application crashed:
Kmail crashed when quitting. There was some IMAP activity going on that had been going on for quite some time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0xb65ca717 in qDeleteAll<QList<KIO::Slave*>::const_iterator> (begin=@0xbfab32d4, end=@0xbfab32d8) at /usr/include/qt4/QtCore/qalgorithms.h:350
#7  0xb65cb3a9 in qDeleteAll<QHash<QString, KIO::SchedulerPrivate::ProtocolInfo*>::const_iterator> (begin={i = 0xa2ec9f0}, end={i = 0x9db40c0}) at /usr/include/qt4/QtCore/qalgorithms.h:358
#8  0xb65c721c in destroy () at /usr/include/qt4/QtCore/qalgorithms.h:358
#9  0xb65c3f38 in __tcf_0 () at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdecore/kernel/kglobal.h:62
#10 0xb56c9bbc in exit () from /lib/libc.so.6
#11 0xb56b3704 in __libc_start_main () from /lib/libc.so.6
#12 0x0804a011 in _start ()

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

Reported using DrKonqi
Comment 1 Magnus Johansson 2009-12-26 22:45:35 UTC 
I couldn't figure out if the fix for bug 199375 is included in KDE 4.3.4. If it is not, please close this bug. Otherwise this is either not a duplicate of bug 199375, or the suggested fix does not work.
Comment 2 Dario Andres 2009-12-27 23:16:11 UTC 
Mh, the possible fix was indeed included into 4.3.4..., so it is unfixed or this is a different issue.
@Thomas: what do you think ?
Thanks
Comment 3 Thomas McGuire 2009-12-27 23:44:07 UTC 
@Thomas: what do you think ?

Looks like the same crash. Probably the commit in bug 199375 didn't fully fix this issue. So I think bug 199375 should be reopened, and this one marked as a duplicate.
Comment 4 Dario Andres 2009-12-28 00:23:30 UTC 
Ok. Reopened. Merging.
Thanks

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