Summary: | kde-base/kmail-4.4.5: "nepomuk indexing agents have been disabled" error message every time I run it | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PM <mitaspiotr> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ag+services, anarsoul, donmartio, esigra, nikoli, vincent |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 313999 | ||
Attachments: |
backtrace1
backtrace2 backtrace3 backtrace4 backtrace5 report file |
Description
PM
2010-02-13 16:21:36 UTC
Did you change to soprano-backend? In ~/.kde4/share/config/nepomukserverrc Change the sesame2 Backend to Used Soprano Backend=virtuosobackend And stop nepomuk (best would be to logout and login again). I did that, then killed everything with nepomuk in it's name and started kmail. I got the same error message plus four "Akondai Resource" crash dialogs and one "Akondai Agent" crash dialog. I'll attach the backtraces. Also when I was closing those dialogs, more of them were popping up, there was about 15 of them... Created attachment 219783 [details]
backtrace1
Created attachment 219785 [details]
backtrace2
Created attachment 219787 [details]
backtrace3
Created attachment 219789 [details]
backtrace4
Created attachment 219791 [details]
backtrace5
And kdepim-runtime is installed? Yes. Now all of a sudden I started getting the following window instead of the previous error: http://img687.imageshack.us/img687/1728/plasmadesktopmy2119.jpg After clicking "Close" kmail quits. I'll attach the report file. Created attachment 220795 [details]
report file
I'm hitting same bug, Soprano Backend is virtuosobackend. Does this still happen on kde 4.4.2? Yes. (In reply to comment #15) > Yes. > Does this still happen on kde 4.4.4? (In reply to comment #16) > (In reply to comment #15) > > Yes. > > > > Does this still happen on kde 4.4.4? > yes still in 4.4.5, and the cure was to change the backend to virtuoso as previously noted, my error was a bit different in that nepomuk was complaining about the sesame2 db not available. sesame2 is not a supported soprano backend any more, and i removed it from >=soprano-2.5.2 I'll close this bug, please reopen if you hit it again with virtuoso backend (as it is the only supported backend) |