Summary: | Kontact crashes when updating Kolab contacts | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Thiago Moreira <thiagomoreira> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | rasasi78 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.11.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Thiago Moreira
2014-02-06 12:08:07 UTC
Created attachment 90569 [details]
New crash information added by DrKonqi
kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
I opened kontact, went to kmail component.
I moved a big imported mail folder to another mail folder created by me. This was a lengthy operation and as it run, I opened a mail in a file using kmail --view <filename>
-- Backtrace (Reduced):
#6 0x00007f1216c66107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7 0x00007f1216c674e8 in __GI_abort () at abort.c:89
[...]
#11 0x00007f11ae9661ef in operator-> (this=<optimized out>) at ../../mailcommon/kernel/mailkernel.cpp:57
#12 MailCommon::Kernel::self () at ../../mailcommon/kernel/mailkernel.cpp:73
#13 0x00007f11ae9b0043 in MailCommon::FolderCollection::writeConfig (this=this@entry=0x29dd7e0) at ../../mailcommon/folder/foldercollection.cpp:218
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |