| Summary: | [/usr/bin/nepomukservicestub] Failed to start service digikamnepomukservice (The service 'Digikam Nepomuk Service' does not provide an interface 'Nepomuk2::Service' with keyword '') | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rex Dieter <rdieter> |
| Component: | Database-Baloo | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, hrvoje.senjan, kde-bugzilla, lukasz.goralczyk, me, michael, sergio, woebbeking, xavier.ribes |
| Priority: | NOR | ||
| Version: | 2.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/digikam/b882df3641e6a3b6b0ff35552d1c9cda434e868e | Version Fixed In: | 3.0.0 |
| Sentry Crash Report: | |||
|
Description
Rex Dieter
2012-07-25 14:42:36 UTC
Sound like KDE nepomuk problem, not digiKam... Gilles Caulier I can confirm the same behaviour. I'm using Ubuntu 12.04, KDE 4.9, digikam 2.9. As a result synchronisation between digikam and nepomuk database is not possible (Dolphin or any other program won't see changed tags/rating). (In reply to comment #1) > Sound like KDE nepomuk problem, not digiKam... > > Gilles Caulier Hey Giles. I'm sorry to say this, but the digikam Nepomuk plugin is now quite broken. I know we should be maintaining compatibility over different releases. But the change monitoring APIs that the digikam service was using were slowing down the entire system by a large factor. In order to fix it one would have to port it to Nepomuk2 (a simple script), and change the resource monitoring from Soprano statements to the Resource Watcher. If someone wants, I can give more detailed instructions on how to fix it. This service ideally needs to be re-written. This time we can export the data properly, so that it can be read by KAddressbook, Telepathy and all other applications using "people" data from Nepomuk. Maybe this could be a nice summer of code project? I can confirm this issue.
This is the relevant debug info:
nepomukfileindexer(28268)/nepomuk (strigi service) Nepomuk2::clearIndexedData: (QUrl("nepomuk:/res/daee02f2-e7ef-497a-a73a-8dc48b99bc99") , QUrl( "nepomuk:/res/ddac37b0-c633-4b42-92ef-a34793cc43f6" ) , QUrl( "nepomuk:/res/40a33962-a35a-4036-ae0b-2e15fc9b34e2" ) , QUrl( "nepomuk:/res/b7758885-339e-4c50-9aed-cec790915fdd" ) )
Hi, Rex Dieter After do this reset akonadi data anda nepomuk data as describe here: http://userbase.kde.org/index.php?title=Akonadi_4.4/Troubleshooting#To_reset_nepomuk_and_the_akonadi_system_in_KMail_2 I also got this message: "Application '/usr/bin/nepomukservicestub digikamnepomukservice' crashed to often. Giving up!" with nepomuk-core-4.9.2-5.fc17.x86_64. It seems a show stopper because the numbering of files indexed, does not grow, just 8 files indexed ! so far Git commit b882df3641e6a3b6b0ff35552d1c9cda434e868e by Marcel Wiesweg. Committed on 17/10/2012 at 18:36. Pushed by mwiesweg into branch 'master'. Disable the current implementation of a digikam-nepomuk integration. By information from the Nepomuk maintainer, the relevant API have been replaced. Essentially, the current code is at best not functional, at worst polluting your Nepomuk db. A new implementation needs to be written based on current APIs. Related: bug 258837, bug 264124, bug 276457, bug 282918, bug 283168, bug 279404, bug 305079 M +35 -35 CMakeLists.txt M +12 -0 utilities/nepomuk/digikamnepomukservice.cpp M +13 -0 utilities/nepomuk/digikamnepomukservice.h http://commits.kde.org/digikam/b882df3641e6a3b6b0ff35552d1c9cda434e868e *** Bug 306861 has been marked as a duplicate of this bug. *** *** Bug 310079 has been marked as a duplicate of this bug. *** |