Summary: | Kmail2 crashed on CTL-Q [ KWallet::Wallet::openWallet ] | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Christopher Heiny <christopherheiny> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | christopherheiny, kdenis |
Priority: | NOR | ||
Version: | 4.8.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christopher Heiny
2012-02-19 01:30:12 UTC
Created attachment 71033 [details]
New crash information added by DrKonqi
kmail (4.8.3) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed: hit CTL-Q. Kmail2 crashed.
Just capturing a dump from version 4.8.3 in case it might be useful.
-- Backtrace (Reduced):
#7 0x00007f554a5317b7 in KWallet::Wallet::openWallet (name=..., w=115343378, ot=KWallet::Wallet::Synchronous) at /usr/src/debug/kdelibs-4.8.3/kdeui/util/kwallet.cpp:518
#8 0x00007f55457a5393 in MailTransport::TransportManager::wallet (this=0x1134480) at /usr/src/debug/kdepimlibs-4.8.3/mailtransport/transportmanager.cpp:606
#9 0x00007f554579c9fd in MailTransport::Transport::readPassword (this=0x12402e0) at /usr/src/debug/kdepimlibs-4.8.3/mailtransport/transport.cpp:314
#10 0x0000003a8b9927a6 in QObject::event (this=0x12402e0, e=<optimized out>) at kernel/qobject.cpp:1195
#11 0x0000003a8f3c9bc4 in notify_helper (e=0x13d4290, receiver=0x12402e0, this=0xf51f50) at kernel/qapplication.cpp:4554
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. I gave up on Kmail about a year and a half ago. As far as I'm concerned, you can close this bug. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |