Bug 101288 - crash after deleting accounts.
Summary: crash after deleting accounts.
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-11 10:04 UTC by Mathieu Jobin
Modified: 2009-09-03 23:34 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 Mathieu Jobin 2005-03-11 10:04:39 UTC
Version:           unknown (using KDE 3.4.0, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.9

delete two kmail imap accounts, clicked ok and kontact crashed.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 8305)]
[KCrash handler]
#5  0x42d858b5 in KMail::ImapAccountBase::listOnlyOpenFolders() const (
    this=0x0) at imapaccountbase.h:91
#6  0x42d839d5 in KMFolderTree::qt_invoke(int, QUObject*) (this=0x85a5460, 
    _id=150759528, _o=0x8fc6890) at kmfoldertree.moc:459
#7  0x41818794 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x85a5460, clist=0x85a95b8, o=0xbfffdd40) at kernel/qobject.cpp:2357
#8  0x41c11a22 in QListView::expanded(QListViewItem*) (this=0x85a5460, 
    t0=0x8fc6890) at .moc/debug-shared-mt/moc_qlistview.cpp:547
#9  0x41920b86 in QListViewItem::setOpen(bool) (this=0x8fc6890, o=true)
    at widgets/qlistview.cpp:1500
#10 0x42d7e67c in KMFolderTree::addDirectory(KMFolderDir*, KMFolderTreeItem*) (
    this=0x85a5460, fdir=0x84970a4, parent=0x0) at kmfoldertree.cpp:657
#11 0x42d7ddf3 in KMFolderTree::reload(bool) (this=0x85a5460, 
    openFolders=false) at kmfoldertree.cpp:503
#12 0x42d7e86a in KMFolderTree::doFolderListChanged() (this=0x0)
    at kmfoldertree.cpp:700
#13 0x42d8394f in KMFolderTree::qt_invoke(int, QUObject*) (this=0x85a5460, 
    _id=1123958196, _o=0x85a5460) at kmfoldertree.moc:454
#14 0x418188ce in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8497078, clist=0x84ccb60, o=0xbfffdff0) at kernel/qobject.cpp:2381
#15 0x418185ec in QObject::activate_signal(int) (this=0x8497078, signal=2)
    at kernel/qobject.cpp:2326
#16 0x42e10a5e in KMFolderMgr::changed() (this=0x0) at kmfoldermgr.moc:140
#17 0x42e0fe51 in KMFolderMgr::contentsChanged() (this=0x0)
    at kmfoldermgr.cpp:398
#18 0x42e0fccc in KMFolderMgr::removeFolderAux(KMFolder*, bool) (
    this=0x8497078, aFolder=0x84b03b8) at kmfoldermgr.cpp:373
#19 0x42e11159 in KMFolderMgr::qt_invoke(int, QUObject*) (this=0x8497078, 
    _id=139030648, _o=0x84b03b8) at kmfoldermgr.moc:247
#20 0x41818794 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x84b03b8, clist=0x84b2198, o=0xbfffe1d0) at kernel/qobject.cpp:2357
#21 0x42dd6718 in KMFolder::removed(KMFolder*, bool) (this=0x84b03b8, t0=0x0, 
    t1=true) at kmfolder.moc:342
#22 0x42dd6b7e in KMFolder::qt_emit(int, QUObject*) (this=0x84b03b8, 
    _id=139133880, _o=0x806e1e8) at kmfolder.moc:375
#23 0x41818768 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x84ac548, clist=0x84a9538, o=0xbfffe310) at kernel/qobject.cpp:2355
#24 0x42defd24 in FolderStorage::removed(KMFolder*, bool) (this=0x84ac548, 
    t0=0x0, t1=true) at folderstorage.moc:376
#25 0x42dee03b in FolderStorage::remove() (this=0x84ac548)
    at folderstorage.cpp:699
#26 0x42e61633 in KMFolderImap::remove() (this=0x84ac548)
    at kmfolderimap.cpp:201
#27 0x42dd4a21 in KMFolder::remove() (this=0x0) at kmfolder.cpp:473
#28 0x42e0fa5d in KMFolderMgr::removeFolder(KMFolder*) (this=0x0, 
    aFolder=0x84b03b8) at kmfoldermgr.cpp:340
#29 0x42e0f9ab in KMFolderMgr::remove(KMFolder*) (this=0x8497078, 
    aFolder=0x84b03b8) at kmfoldermgr.cpp:333
#30 0x42e8df8a in KMKernel::cleanupImapFolders() (this=0x847c568)
    at kmkernel.cpp:1164
#31 0x42d32e27 in AccountsPageReceivingTab::save() (this=0x8ff9da8)
    at configuredialog.cpp:1433
#32 0x42d58790 in ConfigModuleWithTabs::save() (this=0x9002920)
    at configuredialog_p.cpp:395
#33 0x40b58f24 in KCModuleProxy::save() (this=0x8ee64f0)
    at kcmoduleproxy.cpp:533
#34 0x40b49701 in KCMultiDialog::apply() (this=0x8eb18d0)
    at kcmultidialog.cpp:146
#35 0x40b49b59 in KCMultiDialog::slotOk() (this=0x8eb18d0)
    at kcmultidialog.cpp:178
#36 0x42d2903a in ConfigureDialog::slotOk() (this=0x0)
    at configuredialog.cpp:249
#37 0x410b268b in KDialogBase::qt_invoke(int, QUObject*) (this=0x8eb18d0, 
    _id=149625040, _o=0x43044a68) at kdialogbase.moc:359
#38 0x40b487e9 in KCMultiDialog::qt_invoke(int, QUObject*) (this=0x8eb18d0, 
    _id=73, _o=0x49) at kcmultidialog.moc:148
#39 0x42d4e7d6 in ConfigureDialog::qt_invoke(int, QUObject*) (this=0x8eb18d0, 
    _id=73, _o=0x0) at configuredialog.moc:113
#40 0x41818794 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x8f4dd00, clist=0x8f4eac8, o=0xbfffeab0) at kernel/qobject.cpp:2357
#41 0x418185ec in QObject::activate_signal(int) (this=0x8f4dd00, signal=4)
    at kernel/qobject.cpp:2326
#42 0x41c00f5f in QButton::clicked() (this=0x8f4dd00)
    at .moc/debug-shared-mt/moc_qbutton.cpp:152
#43 0x418c631b in QButton::mouseReleaseEvent(QMouseEvent*) (this=0x8f4dd00, 
    e=0xbfffef50) at widgets/qbutton.cpp:833
#44 0x4185b745 in QWidget::event(QEvent*) (this=0x8f4dd00, e=0xbfffef50)
    at kernel/qwidget.cpp:4673
#45 0x417a85a9 in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbffff3f0, receiver=0x8f4dd00, e=0xbfffef50)
    at kernel/qapplication.cpp:2635
#46 0x417a7adc in QApplication::notify(QObject*, QEvent*) (this=0xbffff3f0, 
    receiver=0x8f4dd00, e=0xbfffef50) at kernel/qapplication.cpp:2421
#47 0x412ce34d in KApplication::notify(QObject*, QEvent*) (this=0xbffff3f0, 
    receiver=0x8f4dd00, event=0xbfffef50) at kapplication.cpp:549
#48 0x41730bd6 in QApplication::sendSpontaneousEvent(QObject*, QEvent*) (
    receiver=0x8f4dd00, event=0xbfffef50) at qapplication.h:494
#49 0x417289ba in QETWidget::translateMouseEvent(_XEvent const*) (
    this=0x8f4dd00, event=0xbffff300) at kernel/qapplication_x11.cpp:4288
#50 0x41726282 in QApplication::x11ProcessEvent(_XEvent*) (this=0xbffff3f0, 
    event=0xbffff300) at kernel/qapplication_x11.cpp:3439
#51 0x41743a0d in QEventLoop::processEvents(unsigned) (this=0x8130f38, flags=4)
    at kernel/qeventloop_x11.cpp:192
#52 0x417bf979 in QEventLoop::enterLoop() (this=0x8130f38)
    at kernel/qeventloop.cpp:198
#53 0x417bf892 in QEventLoop::exec() (this=0x8130f38)
    at kernel/qeventloop.cpp:145
#54 0x417a874b in QApplication::exec() (this=0xbffff3f0)
    at kernel/qapplication.cpp:2758
#55 0x0805ba18 in main (argc=0, argv=0x0) at main.cpp:156
Comment 1 Mathieu Jobin 2005-03-11 20:39:15 UTC
this for sure sounds like a kmail bug, however whenever a 
kontact-plugin crash, should kontact crash as well or gracefully handle 
it ?

I can imagine seeing kontact loosing is main document part, keeping 
only the side-button-bar

on the main part, it would be shown something like kmail crash.... 
sorry for incovenience... kmail is restarting please be patient.

and kmail would be back after some time .....

on a separate note, either kmail is embedded in kontact or not should 
be an option and if kmail is launch and the kontact option is enable, 
kontact should be launched instead.

thank you.
Comment 2 Mathieu Jobin 2005-08-13 19:01:02 UTC
is this fix ? I could post 1 new backtrace everyday.... 

I try to not use kmail these days, so much its unstable.

running 3.4.2

Comment 3 Mathieu Jobin 2007-04-24 16:57:45 UTC
this must have been fixed by now, doesn't it ?

Comment 4 Bram Schoenmakers 2007-05-17 11:27:29 UTC
Why you ask? You don't see these crashes anymore?
Comment 5 Mathieu Jobin 2007-05-18 01:45:34 UTC
sorry I was just going through my reports. I stopped using kmail when it became unstable.
Comment 6 Bram Schoenmakers 2007-05-18 18:58:12 UTC
You can try the soon-to-be-released KMail in KDE 3.5.7. Which a bunch of IMAP related crashes.

Bug 137302 is also fixed in 3.5.7, which looks at first glance the same as the problem you described here.

So it would be nice if you could give it a try by the time it is released.
Comment 7 Martin Koller 2009-09-03 23:34:40 UTC
As the reporter no longer uses kmail and the current code is for sure no longer matching this backtrace, let's close it.