Summary: | Activate kmail module cause crash [KMKernel::identityManager, IdentityPage::load] | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Bruno Friedmann <bruno> |
Component: | Assignee: | kdepim bugs <kdepim-bugs> | |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | cyberang3l, glauber.md |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Bruno Friedmann
2009-12-24 17:17:53 UTC
*** Bug 209530 has been marked as a duplicate of this bug. *** Created attachment 53744 [details]
New crash information added by DrKonqi
kontact (4.4.7) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0
- What I was doing when the application crashed:
I was trying contact and I disabled kmail. When I re-enabled it I got this crash. After that, every time I try to use Settings -> Configure Contact, kontact crashes.
-- Backtrace (Reduced):
#6 KMKernel::identityManager (this=0x0) at ../../kmail/kmkernel.cpp:2162
#7 0x00007effe366a8b3 in IdentityPage::load (this=0x2a0e820) at ../../kmail/configuredialog.cpp:301
#8 0x00007f0000b7cd01 in KCModule::qt_metacall (this=0x2a0e820, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2a612f0) at ./kcmodule.moc:89
#9 0x00007effe36a7e70 in qt_metacall (this=0x0, _c=QMetaObject::InvokeMetaMethod, _id=-471061808, _a=0xfffffffffff2a150) at ./configuredialog_p.moc:123
#10 IdentityPage::qt_metacall (this=0x0, _c=QMetaObject::InvokeMetaMethod, _id=-471061808, _a=0xfffffffffff2a150) at ./configuredialog_p.moc:307
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 kontact (version 5.0 or later, as part of KDE Applications 15.08 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. |