Summary: | KMail crash upon accessing KWallet | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Baokai Lei <leibaokai> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | ken20001, montel |
Priority: | NOR | ||
Version: | 4.9.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Baokai Lei
2012-11-25 15:37:57 UTC
Created attachment 76930 [details]
New crash information added by DrKonqi
kmail (4.9.5) on KDE Platform 4.9.5 using Qt 4.8.3
I got thet same problem with KWallet. KMail crashes.
-- Backtrace (Reduced):
#6 QAbstractButton::isChecked (this=0x21) at widgets/qabstractbutton.cpp:774
[...]
#8 0x00007f485f411014 in KDialog::slotButtonClicked (this=0x1d7b850, button=4) at ../../kdeui/dialogs/kdialog.cpp:885
#9 0x00007f485f411434 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./kdialog.moc:167
#10 KDialog::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./kdialog.moc:127
[...]
#12 0x00007f485d7a8e2e in QSignalMapper::mapped (this=this@entry=0x3dbdbd0, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:115
What did you do ? Do you start from empty config ? etc. (In reply to comment #2) > What did you do ? > Do you start from empty config ? > etc. That's right. First I configured IMAP, saved settings and then configured SMTP and after pushing save button it crashed. 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. 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. |