Bug 306861 - digikam Baloo interface no longer works since KDE's upgrade
Summary: digikam Baloo interface no longer works since KDE's upgrade
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Baloo (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-15 19:56 UTC by Xavier Ribes
Modified: 2022-01-28 03:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Ribes 2012-09-15 19:56:05 UTC
Since upgrade to KDE 4.9, digikamnepomukservice crashes too many time on startup (5 tries) and does no longer start. My problem is that I used to deal with digiKam data (tags, comments,...) in Dolphin, Gwenview, etc...
Command in terminal :
/usr/bin/nepomukserver
Messages in terminal :
........ then :
Application '/usr/bin/nepomukservicestub digikamnepomukservice' crashed! 0 restarts left.
[/usr/bin/nepomukservicestub] Failed to start service digikamnepomukservice (Le service " Service Nepomuk pour digiKam " ne fournit pas d'interface " Nepomuk2::Service " avec le mot-clé " ").
Application '/usr/bin/nepomukservicestub digikamnepomukservice' crashed too often. Giving up!
[/usr/bin/nepomukservicestub] QObject::connect: cannot connect XSyncBasedPoller::destroyed() to (null)::_k_x11FilterDestroyed()

Reproducible: Always

Steps to Reproduce:
1. Log on to Ubuntu (Precise 12.04.1) / Unity as a normal user. Check that strigidaemon and nepomukserver have correctly started with the appropriate session startup commands. You should not see 'digikamnepomukservice'.
2. Open a terminal. Kill nepomukserver. Check that no more processes related to nepomuk are running (except 'strigidaemon').
3. At the terminal prompt, enter the command '/usr/bin/nepomukserver &'. Virtuoso / Soprano start correctly, then you get messages (see above) stating that digikamnepomukservice couldn't be started.
4. Check which processes run : digikamnepomukservice is no longer there.
Actual Results:  
You loose all your digiKam metadata in Nepomuk

Expected Results:  
Make all digiKam metadata available to Nepomuk, Dolphin, Gwenview....
Comment 1 Xavier Ribes 2012-09-15 20:02:12 UTC
I couldn't find any similar bug in the database (nothing involving digikamnepomukservice)
Comment 2 Hrvoje Senjan 2012-09-15 20:11:12 UTC
Here it is:
https://bugs.kde.org/show_bug.cgi?id=304052
Comment 3 Vishesh Handa 2012-11-30 23:33:23 UTC

*** This bug has been marked as a duplicate of bug 304052 ***
Comment 4 caulier.gilles 2022-01-28 03:57:34 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=304052