Summary: | Akonadi control crashes after restart | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Karel Pazdera <pazderak> |
Component: | libakonadi | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | sergio_725, unicejos, upscope, winter |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Karel Pazdera
2012-01-21 20:10:46 UTC
Git commit d9194563b17e567317fa3b533a0daa0b03e3fd4b by Allen Winter. Committed on 22/01/2012 at 16:24. Pushed by winterz into branch 'master'. in mimeTypesMonitored() and itemsMonitored() don't call toList() on empty QSets. Since QSets are QHashes and performing operations on empty QHashes is crashy. MERGE: 4.8 FIXED-IN: 4.8.1 M +10 -2 akonadi/monitor.cpp http://commits.kde.org/kdepimlibs/d9194563b17e567317fa3b533a0daa0b03e3fd4b Git commit 872548726dd778011a39576c04cbe9f42e9cc1d5 by Allen Winter. Committed on 22/01/2012 at 16:24. Pushed by winterz into branch 'KDE/4.8'. in mimeTypesMonitored() and itemsMonitored() don't call toList() on empty QSets. Since QSets are QHashes and performing operations on empty QHashes is crashy. MERGE: 4.8 FIXED-IN: 4.8.1 (cherry picked from commit d9194563b17e567317fa3b533a0daa0b03e3fd4b) M +10 -2 akonadi/monitor.cpp http://commits.kde.org/kdepimlibs/872548726dd778011a39576c04cbe9f42e9cc1d5 reopen. my fix was silly and I will revert it. *** Bug 300171 has been marked as a duplicate of this bug. *** *** Bug 300677 has been marked as a duplicate of this bug. *** *** Bug 258449 has been marked as a duplicate of this bug. *** 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. |