Summary: | Nepomuk crashed when logging in. | ||
---|---|---|---|
Product: | [Unmaintained] nepomuk | Reporter: | Benoit Leffray <benoit.leffray.kde> |
Component: | general | Assignee: | Nepomuk Bugs Coordination <nepomuk-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bladud, lucla99_01, nepomuk-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | b94e9f73bd86593928988e5626511acea805b7be | Version Fixed In: | 4.10.1 |
Sentry Crash Report: |
Description
Benoit Leffray
2013-02-08 20:38:47 UTC
*** Bug 314754 has been marked as a duplicate of this bug. *** This appears to be a crash when setting a member variable of m_basicIQ - perhaps due to some sort of memory corruption? I find it a bit suspicious that in both duplicates, the pointer to m_basicIQ is set to the same value, (0x6c). All I can find that is significant about that is that in decimal 0x6c == 108, the value of UNIX_PATH_MAX. Ah, no - it is calling Nepomuk2::IndexCleaner::start at line 56 of ./../../services/fileindexer/indexscheduler.cpp, which means it is the bug that was fixed by commit: commit b94e9f73bd86593928988e5626511acea805b7be Author: Edward Toroshchin <kde@hades.name> Date: Sun Feb 3 17:57:23 2013 +0100 fileindexer: initialize objects in correct order The IndexCleaner job created in IndexScheduler could complete before m_eventMonitor is initialized, which leads to crash in slotCleaningDone. REVIEW: 108754 Sorry, I thought this fix got into 4.10, but it seems it did not. Nuts. |