Summary: | Kontact crash when moving to next unread message (KMail) | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Andreas Karrenbauer <andreas.karrenbauer> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | m.wege |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Andreas Karrenbauer
2011-08-10 15:05:57 UTC
*** Bug 283291 has been marked as a duplicate of this bug. *** Created attachment 67398 [details]
New crash information added by DrKonqi
kmail (4.8 rc1) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4
- What I was doing when the application crashed: I was klicking on an email in a folder.I was klicking on an email in a folder.
-- Backtrace (Reduced):
#6 size (this=0x2e006500700079) at ../../include/QtCore/../../src/corelib/tools/qvector.h:124
#7 QSortFilterProxyModelPrivate::proxy_to_source (this=0x2346bc0, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:369
#8 0x000000345758b33d in QSortFilterProxyModel::mapToSource (this=<optimized out>, proxyIndex=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:2500
#9 0x000000345758c5ad in QSortFilterProxyModelPrivate::store_persistent_indexes (this=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:994
#10 0x00000034575910bf in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x2346bc0, source_top_left=..., source_bottom_right=...) at itemviews/qsortfilterproxymodel.cpp:1158
Created attachment 67399 [details]
New crash information added by DrKonqi
kmail (4.8 rc1) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4
- What I was doing when the application crashed: I was klicking on an email in a folder.I was klicking on an email in a folder.
-- Backtrace (Reduced):
#6 size (this=0x2e006500700079) at ../../include/QtCore/../../src/corelib/tools/qvector.h:124
#7 QSortFilterProxyModelPrivate::proxy_to_source (this=0x2346bc0, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:369
#8 0x000000345758b33d in QSortFilterProxyModel::mapToSource (this=<optimized out>, proxyIndex=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:2500
#9 0x000000345758c5ad in QSortFilterProxyModelPrivate::store_persistent_indexes (this=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:994
#10 0x00000034575910bf in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x2346bc0, source_top_left=..., source_bottom_right=...) at itemviews/qsortfilterproxymodel.cpp:1158
Created attachment 67400 [details]
New crash information added by DrKonqi
kmail (4.8 rc1) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4
- What I was doing when the application crashed: I was klicking on an email in a folder.I was klicking on an email in a folder.
-- Backtrace (Reduced):
#6 size (this=0x2e006500700079) at ../../include/QtCore/../../src/corelib/tools/qvector.h:124
#7 QSortFilterProxyModelPrivate::proxy_to_source (this=0x2346bc0, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:369
#8 0x000000345758b33d in QSortFilterProxyModel::mapToSource (this=<optimized out>, proxyIndex=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:2500
#9 0x000000345758c5ad in QSortFilterProxyModelPrivate::store_persistent_indexes (this=<optimized out>) at itemviews/qsortfilterproxymodel.cpp:994
#10 0x00000034575910bf in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=0x2346bc0, source_top_left=..., source_bottom_right=...) at itemviews/qsortfilterproxymodel.cpp:1158
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. |