Bug 173359 - kontact crashed after trying to log into newly created IMAP account
Summary: kontact crashed after trying to log into newly created IMAP account
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: 1.10.90
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 266074 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-10-23 11:57 UTC by Oliver Putz
Modified: 2012-08-19 10:58 UTC (History)
2 users (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 Oliver Putz 2008-10-23 11:57:55 UTC
Version:           1.10.90 (using 4.1.69 (KDE 4.1.69 (KDE 4.2 >= 20081009)), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.26-gentoo-r1

What I did:

- I fired up kontact and created an IMAP Mail account (only account)
- The first time I was asked to enter the password (automatic mail check for the newly created account) 
- I hit cancel (in fact I had to hit it like 10 times before it gave up...)
- I changed the settings of that IMAP Account (auto expunge from on to off)
- When I wanted to open the account I was again asked for the password.
- I entered the password and kontact crashed with the backtrace below:

Remark: Subsequent "logins" do not crash any longer

Application: Kontact (kontact), signal SIGSEGV

Thread 1 (Thread 0xb4ee4720 (LWP 12034)):
[KCrash Handler]
#6  0xb1bd981e in QPointer<KMAccount>::operator KMAccount* (this=0x7280039) at /usr/include/qt4/QtCore/qpointer.h:79
#7  0xb1bd0053 in AccountsPageReceivingTab::save (this=0x86e80c0) at /var/tmp/portage/kde-base/kmail-4.1.69/work/kmail-4.1.69/kmail/configuredialog.cpp:1192
#8  0xb1be77b7 in ConfigModuleWithTabs::save (this=0x86eb628) at /var/tmp/portage/kde-base/kmail-4.1.69/work/kmail-4.1.69/kmail/configuredialog_p.cpp:323
#9  0xb598480b in KCModuleProxy::save (this=0x86ecbd0) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs-4.1.69/kutils/kcmoduleproxy.cpp:276
#10 0xb5980709 in KCMultiDialogPrivate::apply (this=0x86d81b8) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs-4.1.69/kutils/kcmultidialog.cpp:192
#11 0xb598224a in KCMultiDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf87dfe8)
    at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs_build/kutils/kcmultidialog.moc:86
#12 0xb1bd8060 in ConfigureDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=77, _a=0xbf87dfe8)
    at /var/tmp/portage/kde-base/kmail-4.1.69/work/kmail_build/kmail/configuredialog.moc:67
#13 0xb7f924e1 in QMetaObject::activate (sender=0x86d2f78, from_signal_index=<value optimized out>, to_signal_index=42, argv=0x0) at kernel/qobject.cpp:3028
#14 0xb7f943d8 in QMetaObject::activate (sender=0x86d2f78, m=0xb7c1f684, local_signal_index=7, argv=0x0) at kernel/qobject.cpp:3098
#15 0xb7a4667d in KDialog::applyClicked (this=0x86d2f78) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs_build/kdeui/kdialog.moc:235
#16 0xb7a47a5d in KDialog::slotButtonClicked (this=0x86d2f78, button=8) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs-4.1.69/kdeui/dialogs/kdialog.cpp:848
#17 0xb7a49a4c in KDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbf87e21c) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs_build/kdeui/kdialog.moc:181
#18 0xb7af8220 in KPageDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbf87e21c)
    at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs_build/kdeui/kpagedialog.moc:63
#19 0xb59821d8 in KCMultiDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbf87e21c)
    at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs_build/kutils/kcmultidialog.moc:77
#20 0xb1bd8060 in ConfigureDialog::qt_metacall (this=0x86d2f78, _c=QMetaObject::InvokeMetaMethod, _id=68, _a=0xbf87e21c)
    at /var/tmp/portage/kde-base/kmail-4.1.69/work/kmail_build/kmail/configuredialog.moc:67
#21 0xb7f924e1 in QMetaObject::activate (sender=0x86d8208, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xbf87e21c) at kernel/qobject.cpp:3028
#22 0xb7f943d8 in QMetaObject::activate (sender=0x86d8208, m=0xb805f970, local_signal_index=0, argv=0xbf87e21c) at kernel/qobject.cpp:3098
#23 0xb7f95c27 in QSignalMapper::mapped (this=0x86d8208, _t1=8) at .moc/debug-shared/moc_qsignalmapper.cpp:93
#24 0xb7f96431 in QSignalMapper::map (this=0x86d8208, sender=0x86defd8) at kernel/qsignalmapper.cpp:277
#25 0xb7f9662e in QSignalMapper::map (this=0x86d8208) at kernel/qsignalmapper.cpp:268
#26 0xb7f96f7d in QSignalMapper::qt_metacall (this=0x86d8208, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf87e3ac) at .moc/debug-shared/moc_qsignalmapper.cpp:80
#27 0xb7f924e1 in QMetaObject::activate (sender=0x86defd8, from_signal_index=<value optimized out>, to_signal_index=30, argv=0xbf87e3ac) at kernel/qobject.cpp:3028
#28 0xb7f92904 in QMetaObject::activate (sender=0x86defd8, m=0xb62a1384, from_local_signal_index=2, to_local_signal_index=3, argv=0xbf87e3ac) at kernel/qobject.cpp:3118
#29 0xb60d09d3 in QAbstractButton::clicked (this=0x86defd8, _t1=false) at .moc/debug-shared/moc_qabstractbutton.cpp:185
#30 0xb5e2833f in QAbstractButtonPrivate::emitClicked (this=0x86df380) at widgets/qabstractbutton.cpp:544
#31 0xb5e29dda in QAbstractButtonPrivate::click (this=0x86df380) at widgets/qabstractbutton.cpp:537
#32 0xb5e2a003 in QAbstractButton::mouseReleaseEvent (this=0x86defd8, e=0xbf87ea9c) at widgets/qabstractbutton.cpp:1116
#33 0xb5b3a5a2 in QWidget::event (this=0x86defd8, event=0xbf87ea9c) at kernel/qwidget.cpp:7169
#34 0xb5e2820c in QAbstractButton::event (this=0x86defd8, e=0xbf87ea9c) at widgets/qabstractbutton.cpp:1078
#35 0xb5ecd13a in QPushButton::event (this=0x86defd8, e=0xbf87ea9c) at widgets/qpushbutton.cpp:658
#36 0xb5ae1fab in QApplicationPrivate::notify_helper (this=0x8066e00, receiver=0x86defd8, e=0xbf87ea9c) at kernel/qapplication.cpp:3809
#37 0xb5ae9438 in QApplication::notify (this=0xbf87f128, receiver=0x86defd8, e=0xbf87ea9c) at kernel/qapplication.cpp:3534
#38 0xb7ace2b1 in KApplication::notify (this=0xbf87f128, receiver=0x86defd8, event=0xbf87ea9c) at /var/tmp/portage/kde-base/kdelibs-4.1.69/work/kdelibs-4.1.69/kdeui/kernel/kapplication.cpp:307
#39 0xb7f7bb21 in QCoreApplication::notifyInternal (this=0xbf87f128, receiver=0x86defd8, event=0xbf87ea9c) at kernel/qcoreapplication.cpp:593
#40 0xb5aea879 in QApplicationPrivate::sendMouseEvent (receiver=0x86defd8, event=0xbf87ea9c, alienWidget=0x86defd8, nativeWidget=0x86d2f78, buttonDown=0xb62a7c60, lastMouseReceiver=@0xb62a7c64)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#41 0xb5b529e7 in QETWidget::translateMouseEvent (this=0x86d2f78, event=0xbf87efa8) at kernel/qapplication_x11.cpp:4048
#42 0xb5b5131e in QApplication::x11ProcessEvent (this=0xbf87f128, event=0xbf87efa8) at kernel/qapplication_x11.cpp:3044
#43 0xb5b7796d in QEventDispatcherX11::processEvents (this=0x8061ff0, flags={i = -1081610168}) at kernel/qeventdispatcher_x11.cpp:134
#44 0xb7f7a6b0 in QEventLoop::processEvents (this=0xbf87f0c0, flags={i = -1081610104}) at kernel/qeventloop.cpp:149
#45 0xb7f7a852 in QEventLoop::exec (this=0xbf87f0c0, flags={i = -1081610040}) at kernel/qeventloop.cpp:200
#46 0xb7f7cc6f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#47 0xb5ae1d43 in QApplication::exec () at kernel/qapplication.cpp:3337
#48 0x0804b901 in main (argc=1, argv=0xbf87f2e4) at /var/tmp/portage/kde-base/kontact-4.1.69/work/kontact-4.1.69/kontact/src/main.cpp:218
Comment 1 George Kiagiadakis 2008-10-23 14:24:44 UTC
Reassigning to kdepim-bugs. Looks like a valid bug :)
Comment 2 Björn Ruberg 2010-01-31 11:29:15 UTC
Cannot reproduce in KDE 4.3.4. Please report if you can
Comment 3 Christophe Marin 2011-02-14 11:03:41 UTC
from bug 266074:

- What I was doing when the application crashed:
Hi, I used IMAP email protocol to retrieve mails, but after few days, it
started to ask to password even I had it saved in kwallet, so I decided to
delete IMAP settings and then, it asked for downloading messages, I allowed it
and then it crashed.
Comment 4 Christophe Marin 2011-02-14 11:03:48 UTC
*** Bug 266074 has been marked as a duplicate of this bug. ***
Comment 5 Myriam Schweingruber 2012-08-19 10:58:07 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