Summary: | kontact segfaults on exit | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | ray-ven <gortab> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | giecrilj, maarten.bezemer |
Priority: | NOR | ||
Version: | 4.9.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
ray-ven
2012-12-18 22:14:04 UTC
Created attachment 77547 [details]
New crash information added by DrKonqi
kontact (4.9) on KDE Platform 4.9.00 using Qt 4.8.1
- What I was doing when the application crashed:
I told KDE to shut down, Kontact crashed while quitting.
-- Backtrace (Reduced):
#7 0x000000000040374e in qDeleteAll<QList<KMainWindow*>::const_iterator> (end=..., begin=...) at /usr/include/QtCore/qalgorithms.h:322
#8 qDeleteAll<QList<KMainWindow*> > (c=...) at /usr/include/QtCore/qalgorithms.h:330
#9 main (argc=3, argv=0x7fffe64f6188) at /tmp/kde-krzysztof/ark3uU5x5/kdepim-4.9.0/kontact/src/main.cpp:220
Created attachment 82923 [details]
New crash information added by DrKonqi
kontact (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4
- What I was doing when the application crashed:
I quit KMail as I had to restart it to load newly installed dictionary
It happened on a freshly installed Kuuntu 13.10
-- Backtrace (Reduced):
#7 0x00000000004036a6 in qDeleteAll<QList<KMainWindow*>::const_iterator> (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322
#8 qDeleteAll<QList<KMainWindow*> > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330
#9 main (argc=1, argv=0x7fff7e1e4578) at ../../../kontact/src/main.cpp:220
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. |