Summary: | KMail Fatal Error: Accessed global static 'SchedulerPrivate *schedulerPrivate()' | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Christopher Yeleighton <giecrilj> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | fizista, martin.ruessler |
Priority: | NOR | ||
Version: | 4.8.x | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christopher Yeleighton
2012-06-28 16:31:41 UTC
*** Bug 307369 has been marked as a duplicate of this bug. *** Confirmed by duplicate. Created attachment 75815 [details]
New crash information added by DrKonqi
kontact (4.9.4) on KDE Platform 4.9.4 using Qt 4.8.3
- What I was doing when the application crashed:
I had two active activities, Kontact running on one of them, I was using the other. When I clicked on the Kontact icon in the icon-only task manager Kontact crashed. I tried three times to reproduce the crash by running Kontact on a different activity from where I activated it but, alas, with no luck ;)
-- Backtrace (Reduced):
#6 0x00007f3cbe5b7425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f3cbe5bab8b in __GI_abort () at abort.c:91
[...]
#11 0x00007f3c5b70ba47 in operator-> (this=<optimized out>) at ../../mailcommon/mailkernel.cpp:53
#12 MailCommon::Kernel::self () at ../../mailcommon/mailkernel.cpp:69
#13 0x00007f3c5b6fe169 in MailCommon::FolderCollection::writeConfig (this=this@entry=0x2d57350) at ../../mailcommon/foldercollection.cpp:208
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. |