Bug 226613 - KMail crashed after granting KWallet access once
Summary: KMail crashed after granting KWallet access once
Status: RESOLVED DUPLICATE of bug 286789
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 238286 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-13 00:46 UTC by Christoph Lange
Modified: 2011-11-18 22:50 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 Christoph Lange 2010-02-13 00:46:17 UTC
Application: kmail (1.13.0)
KDE Platform Version: 4.4.00 (KDE 4.4.0) (Compiled from sources)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-thinkpad x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
I wanted to send a mail. My SMTP password is in KWallet. KWallet was running and still had the password cached, as I had started KMail just a few minutes ago, and it used my IMAP password, which is also in KWallet. So when sending the mail, KMail asked for access to the wallet, and I granted it access “once”. Then KMail crashed.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fa2ce546f6d in QString::operator=(QString const&) () from /usr/lib64/qt4/libQtCore.so.4
#6  0x00007fa2d36017ad in KWallet::Wallet::readPassword(QString const&, QString&) () from /usr/lib/libkdeui.so.5
#7  0x00007fa2c8dfbd89 in MailTransport::Transport::readPassword() () from /usr/lib/libmailtransport.so.4
#8  0x00007fa2c8dfc19a in MailTransport::Transport::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libmailtransport.so.4
#9  0x00007fa2ce5f827e in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fa2ce5fea7d in QSingleShotTimer::timerEvent(QTimerEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#11 0x00007fa2ce5f502c in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007fa2cd9024ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00007fa2cd90a58c in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#14 0x00007fa2d3581654 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007fa2ce5e6b74 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007fa2ce60fd0e in QTimerInfoList::activateTimers() () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fa2ce60c84f in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007fa2c663f8e3 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007fa2c664283c in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#20 0x00007fa2c66429be in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007fa2ce60c5c4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007fa2cd991586 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007fa2ce5e5834 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007fa2ce5e5b7f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007fa2ce5e7b5e in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#26 0x00000000004038e7 in main ()

Reported using DrKonqi
Comment 1 Laurent RINEAU 2010-05-20 12:04:00 UTC
*** Bug 238286 has been marked as a duplicate of this bug. ***
Comment 2 Laurent RINEAU 2010-06-17 14:57:05 UTC
This bug is really annoying. Can we do anything to help you understand the cause of it and fix it?
Comment 3 Christophe Marin 2011-11-18 22:50:05 UTC

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