I recently upgraded from KDE 4.12.4 to 4.13.0.

I followed the instructions to migrate from Nepomuk to Baloo given in the thread Transitioning to KDE's next generation semantic search but it does not seem to have worked correctly, as Nepomuk is still running. nepomukbaloomigrator crashes if I run it. Before I ran nepomukbaloomigrator I noticed that the file nepomukserverrc already contained "migrated=true". Was nepomukserverrc run automatically the first time I logged-in to KDE 4.13.0? Anyway, here is the current situation:

Code: Select all

$ cat ~/.kde4/share/config/nepomukserverrc
[Baloo]
migrated=true

[Basic Settings]
Start Nepomuk=true

[Service-nepomukfileindexer]
autostart=true

[Service-nepomuktelepathyservice]
autostart=false

[main Settings]
GraphMigrationRequired=false
Port=1113
Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/
Used Soprano Backend=virtuosobackend
$

Code: Select all

$ nepomukctl status
Nepomuk Server is running.
Service storage is running.
Service fileindexer is running.
Service filewatch is running.
$

Code: Select all

$ nepomukbaloomigrator
Data already migrated. Quitting
nepomukbaloomigrator(8913): Communication problem with  "nepomukbaloomigrator" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.UnknownObject" : " "No such object path '/MainApplication'" "

$

Code: Select all

$ nepomukctl status
Nepomuk Server is running.
Service storage is running.
Service fileindexer is running.
Service filewatch is running.
$

Code: Select all

$ pgrep -fl nepomuk
8461 nepomukserver
8463 nepomukstorage
8842 nepomukfilewatc
8844 nepomukfileinde
$ pgrep -fa nepomuk
8461 kdeinit4: nepomukserver [kdeinit]
8463 /usr/bin/nepomukstorage
8842 /usr/bin/nepomukfilewatch
8844 /usr/bin/nepomukfileindexer
$

I would be grateful for advice on what to do in order to complete the migration successfully. Thanks in advance.

Did you try removing the [Baloo] key and associated bits entirely?

Please do as Ben suggested. Remove the [Baloo] migrated = true from the config file, and then run the nepomukbaloomigrator. You may want to run it under gdb as follows -

$ gdb nepomukbaloomigrator
> run

This way if it crashes, you can get a backtrace by typing 'bt'. You should file a bug if it crashes again.

Unfortunately that did not work:

Code: Select all

$ cp ~/.kde4/share/config/nepomukserverrc ~/nepomukserverrc.bak
$ nano ~/.kde4/share/config/nepomukserverrc
$ cat ~/.kde4/share/config/nepomukserverrc
[Basic Settings]
Start Nepomuk=true

[Service-nepomukfileindexer]
autostart=true

[Service-nepomuktelepathyservice]
autostart=false

[main Settings]
GraphMigrationRequired=false
Port=1113
Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/
Used Soprano Backend=virtuosobackend
$

Code: Select all

$ nepomukctl status
Nepomuk Server is running.
Service storage is running.
Service fileindexer is running.
Service filewatch is running.
$

Code: Select all

$ nepomukbaloomigrator
No Nepomuk data found
nepomukbaloomigrator(9690): Communication problem with  "nepomukbaloomigrator" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.UnknownObject" : " "No such object path '/MainApplication'" "

$

I also tried with gdb as suggested by vHanda, but got the following:

Code: Select all

$ gdb nepomukbaloomigrator
GNU gdb (Gentoo 7.6.2 p1) 7.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/bin/nepomukbaloomigrator...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/nepomukbaloomigrator
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
No Nepomuk data found
nepomukbaloomigrator(9928): Communication problem with  "nepomukbaloomigrator" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.UnknownObject" : " "No such object path '/MainApplication'" "

[Inferior 1 (process 9928) exited with code 0377]
(gdb) bt
No stack.
(gdb) quit
$ bt
bash: bt: command not found
$

Further to my previous post, I decided to reboot even though nepomukbaloomigrator continued to crash, just to see if anything would change after a complete restart. There is now a difference:

Code: Select all

$ nepomukctl status
Nepomuk Server is not running.
$

I also see that nepomukserverrc was again altered to include [Baloo] migrated=true, but this time both [Basic Settings] Start Nepomuk and [Service-nepomukfileindexer] autostart have been changed to =false as you can see below:

Code: Select all

$ cat ~/.kde4/share/config/nepomukserverrc
[Baloo]
migrated=true

[Basic Settings]
Start Nepomuk=false

[Service-nepomukfileindexer]
autostart=false

[Service-nepomuktelepathyservice]
autostart=false

[main Settings]
GraphMigrationRequired=false
Port=1113
Storage Dir[$e]=$HOME/.kde4/share/apps/nepomuk/repository/main/
Used Soprano Backend=virtuosobackend
$

Does this mean that, despite nepomukbaloomigrator crashing as shown in my previous post, this time the migration completed successfully?

How can I check that Nepomuk has been properly disabled and that Baloo is running and indexing correctly?

Previously, when you couldn't get a backtrace off gdb. That was cause the migrator was still running in the background (I think). If you want to get a proper backtrace, you need to kill it and then start it via gdb.

Anyway, it seems like the migration is done. A backtrace would have been nice though.

Check if baloo_file is running. If it is, then you are good to go.

Does the following look correct?

Code: Select all

$ ps -ef | grep baloo
fitzcarraldo      8213  8166  0 13:11 ?        00:00:00 /usr/bin/akonadi_baloo_indexer --identifier akonadi_baloo_indexer
fitzcarraldo      8246     1  0 13:12 ?        00:00:04 /usr/bin/baloo_file
fitzcarraldo     10249  8351  0 14:53 pts/0    00:00:00 grep --colour=auto baloo

So just akonadi_baloo_indexer and baloo_file take care of indexing everything?

How can I be sure that everything in the Nepomuk database has been moved to Baloo's database? Is there some way for me to check that? Is there a way of making Baloo re-index all files if necessary?

I'd also be grateful if you could point me to some good on-line documentation on Baloo, so that I can learn how to use it properly, including any commands I can issue from the command line. Thanks again for your help.

Yes, it looks fine from a functionality perspective. While I am not well versed in the new system yet, I can tell you that "baloosearch" is a command-line search client, and "balooshow" shows metadata information about a file. The rest behaves like with Nepomuk, IOW you can use Dolphin to search, or KRunner (the "Run Command" interface), or the new "Milou" plasmoid.