Summary: | assert in MonitorPrivate::deref( Collection::Id id ) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Christian Mollekopf <chrigi_1> |
Component: | akonadiconsole | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | chrigi_1 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christian Mollekopf
2012-01-18 17:37:29 UTC
Created attachment 67974 [details]
New crash information added by DrKonqi
akonadiconsole (0.99) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0
- What I was doing when the application crashed:
in akonadiconsole, collections tab, first select one collection, then another => crash
-- Backtrace (Reduced):
#13 0x00007f0dd7fcf1a5 in Akonadi::EntityTreeModel::setData (this=0x84d5d0, index=..., value=..., role=53) at /home/chrigi/devel/kde/kdepimlibs/akonadi/entitytreemodel.cpp:735
#14 0x00007f0dd803ecde in Akonadi::SelectionProxyModelPrivate::rootIndexAboutToBeRemoved (this=0x83fbd0, removedRootIndex=...) at /home/chrigi/devel/kde/kdepimlibs/akonadi/selectionproxymodel.cpp:59
#15 0x00007f0dd803e8b9 in Akonadi::SelectionProxyModel::qt_static_metacall (_o=0x83f570, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffee9dcfb0) at /home/chrigi/devel/kde/build/global/kdepimlibs/akonadi/selectionproxymodel.moc:53
[...]
#17 0x00007f0dd37f5da2 in KSelectionProxyModel::rootIndexAboutToBeRemoved(QModelIndex const&) () from /usr/lib/libkdeui.so.5
[...]
#22 0x00007f0dd2de6537 in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/libQtGui.so.4
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (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. |