Summary: | Nepomuk crashes on startup when Strigi is enabled | ||
---|---|---|---|
Product: | nepomuk | Reporter: | Robert Forsyth <robert.styles.forsyth> |
Component: | fileindexer | Assignee: | Sebastian Trueg <sebastian> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | drf, me, trueg, wstephenson |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Robert Forsyth
2011-11-14 01:01:11 UTC
Is this if you logout directly after logging in, ie. shutting down nepomuk during initialization? It appears to happen soon after I login. If Nepomuk is already enabled and then Strigi is enabled, no immediate crash, then logout, no obvious crash (although occasionally something crashes), then log back in, crash. If Nepomuk is already enabled and then Strigi is enabled, no immediate crash, then if Nepomuk is disabled crash. On 17 November 2011 19:06, Sebastian Trueg <trueg@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=286546 > > > > > > --- Comment #1 from Sebastian Trueg <trueg kde org> 2011-11-17 19:06:42 > --- > Is this if you logout directly after logging in, ie. shutting down nepomuk > during initialization? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Hello, can you please repost the backtrace after having installed debug symbols for Solid (kdelibs)? The following two lines are missing information and are quite critical: #9 0x00007f4a07cbf0a0 in ?? () from /usr/lib64/libsolid.so.4 #10 0x00007f4a07cbfd6e in Solid::PowerManagement::notifier() () from /usr/lib64/libsolid.so.4 Thanks Today I logged in from cold boot (first from power up). Loaded the kdelib debug symbols via YaST. Both Nepomuk and Strigi were enabled (in the Desktop Search - KDE Control Module) and Strigi was indexing some file. Anyway, I logged out, then logged back in, but no crash. In the Desktop Search - KDE Control Module, both Nepomuk and Strigi were enabled, but were inactive. While writing this they became active. Disabling Nepomuk (while Strigi is enabled) caused some notifications, but no crash. I don't know why the problem has gone away, may be when Strigi is first enabled some long running critical task occurs, which is not needed on subsequent enabling. Closing as FIXED. The issue has disappeared, and without a backtrace containing the solid debugging symbols, we cannot do much. |