Hi,
After upgrading to kubuntu 14.04 I've found that dolphin lacks the ability to add ratings/tags/comments to files.
Baloo is enabled and running.
Do I miss something or is this an expected "behavior"?
ty

So far I've been able to use these. Please make sure you have "baloo-widgets" and "kfilemetadata" installed. The actual package names may vary depending on your distribution.

einar wrote:So far I've been able to use these. Please make sure you have "baloo-widgets" and "kfilemetadata" installed. The actual package names may vary depending on your distribution.

Unfortunatley I do not have any baloo-widgets, maybe it is named libbaloowidgets4:

Code: Select all

$ dpkg -l|grep baloo
ii  baloo                                  4:4.13.2-0ubuntu0.1                        amd64        framework for searching and managing metadata.
ii  libbaloocore4                          4:4.13.2-0ubuntu0.1                        amd64        Core funcationality for Baloo
ii  libbaloofiles4                         4:4.13.2-0ubuntu0.1                        amd64        Files funcationality for Baloo
ii  libbaloopim4                           4:4.13.2-0ubuntu0.1                        amd64        PIM funcationality for Baloo
ii  libbaloowidgets4                       4:4.13.0-0ubuntu1                          amd64        Wigets for use with Baloo
ii  libbalooxapian4                        4:4.13.2-0ubuntu0.1                        amd64        Xapian funcationality for Baloo
$ dpkg -l|grep kfilemetadata
ii  libkfilemetadata4                      4:4.13.2-0ubuntu0.1                        amd64        library for extracting file metadata

I have this same problem on three kubuntu 14.04 desktops upgraded from 13.10.
EDIT: How is it supposed to be called the function to add tags/ratings/comments? I may have missed its location..

I'm not sure of the current state of affairs with Baloo as I've gave up on it.

At a minimum you require:

baloo-core
baloo-file
libbaloofiles4
libbaloowidgets4

You also require to have the file-system use extended file attributes.

There are quite a few bugs teething problems with Baloo, for example:

https://bugs.kde.org/show_bug.cgi?id=333553
https://bugs.kde.org/show_bug.cgi?id=333962
https://bugs.kde.org/show_bug.cgi?id=332065
https://bugs.kde.org/show_bug.cgi?id=336084
https://bugs.kde.org/show_bug.cgi?id=335087
https://bugs.kde.org/show_bug.cgi?id=332610
https://bugs.kde.org/show_bug.cgi?id=332214

Some people have reported few problems, and Baloo 'works for me', others have many issues.

Your mileage will vary

Are you able to tell from the package metadata whether Dolphin depends on any of those Baloo libraries?

Dolphin has 'libbaloofiles4' & 'libbaloowidgets4' as dependencies....

However the developers (Dolphin) have done quite a lot to enable Dolphin to work, albeit with some meta-data display limitations, without baloo.

It's all rather 'fluid' at the moment, and as I said I'm no longer using baloo, so therefore not following too closely the bug-fixes being made.

bcooksley wrote:Are you able to tell from the package metadata whether Dolphin depends on any of those Baloo libraries?

On openSUSE, yes:

Code: Select all

:~> rpm -q --requires dolphin
...
libbaloocore.so.4()(64bit)
libbaloofiles.so.4()(64bit)
libbaloowidgets.so.4()(64bit)
...


(libbaloocore is instide the package "baloo-core")

baloo-file is actually _not_ required on a package level, as it was advertised you can uninstall this to get rid of the file indexer completely (it only contains the indexer executables and the KCM).
But without it, the whole dolphin information panel does not work at all at the moment, see the mentioned https://bugs.kde.org/show_bug.cgi?id=335087 f.e.
On Kubuntu this is part of the normal "baloo" package though, which the OP apparently has installed, so this should not be the problem here.

Btw, adding tags/ratings/comments in dolphin's information panel seems to work fine here on a default Kubuntu 14.04 installation inside VirtualBox.

@Frasty:
I do see a possible problem with the package list you posted:
libbaloowidgets4 is still at version 4:4.13.0-0ubuntu1, whereas the rest has 4:4.13.2-0ubuntu0.1.
Maybe this causes your problem?

Where do you actually have those 4.13.2 packages from? I don't see those available here in that Kubuntu VM.
From some PPA? Then make sure that you install libbaloowidgets4 from there as well.
Or switch back all packages to the standard versions.

wolfi323 wrote:@Frasty:
I do see a possible problem with the package list you posted:
libbaloowidgets4 is still at version 4:4.13.0-0ubuntu1, whereas the rest has 4:4.13.2-0ubuntu0.1.
Maybe this causes your problem?

4:4.13.0-0ubuntu1 seems to be the last released package:

Code: Select all

$ apt-cache policy libbaloowidgets4
libbaloowidgets4:
  Installato: 4:4.13.0-0ubuntu1
  Candidato:  4:4.13.0-0ubuntu1
  Tabella versione:
 *** 4:4.13.0-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

wolfi323 wrote:Where do you actually have those 4.13.2 packages from? I don't see those available here in that Kubuntu VM.
From some PPA? Then make sure that you install libbaloowidgets4 from there as well.
Or switch back all packages to the standard versions.

All the 4.13.2 packages belong to "trusty-proposed", although I do have kubuntu-ppa/ppa and kubuntu-ppa/experimental enabled.
Maybe packages from trusty-proposed are still not in an optimal status, I'll try to downgrade asap.

Code: Select all

apt-cache policy libbaloofiles4 libbalooxapian4
libbaloofiles4:
  Installato: 4:4.13.2-0ubuntu0.1
  Candidato:  4:4.13.2-0ubuntu0.1
  Tabella versione:
 *** 4:4.13.2-0ubuntu0.1 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status
     4:4.13.2-0ubuntu0.1~ubuntu14.04~ppa1 0
        500 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu/ trusty/main amd64 Packages
     4:4.13.1-0ubuntu0.1 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
     4:4.13.1-0ubuntu0.1~ubuntu14.04~ppa3 0
        500 http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu/ trusty/main amd64 Packages
     4:4.13.0-0ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

This is still happening to me debian/jessie:

Code: Select all

# dpkg -l | grep baloo
ii  baloo-utils                           4:4.13.3-1                        i386         framework for searching and managing metadata.
ii  baloo4                                4:4.13.3-1                        i386         framework for searching and managing metadata.
ii  libbaloocore4                         4:4.13.3-1                        i386         Core funcationality for Baloo
ii  libbaloofiles4                        4:4.13.3-1                        i386         Files funcationality for Baloo
ii  libbaloopim4                          4:4.13.3-1                        i386         PIM funcationality for Baloo
ii  libbaloowidgets4                      4:4.13.3-1                        i386         Widgets for Baloo
ii  libbalooxapian4                       4:4.13.3-1                        i386         Xapian funcationality for Baloo


No ratings/tags on dolphin. Ballo is active and is able to search metadata, in krunner I have results from emails and other semantic goodies. kfilemetadata is provided in debian as libkfilemetadata4 and it is a depedency of libbaloowidgets4, baloo4 and baloo-utils.

Does anyone have any idea. My system is supposed to be up to date but this is functionality that I am missing.

Upon further inspection of the issue when starting dolphin in the shell i get this:

Code: Select all

dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting
dolphin(10534)/nepomuk (library): Could not find virtuoso to connect to. Aborting


However in my system I have:

Code: Select all

$ dpkg -l | grep virtuoso
ii  virtuoso-minimal                      6.1.6+dfsg-4                      all          high-performance database - core dependency package
ii  virtuoso-opensource-6.1-bin           6.1.6+dfsg-4                      i386         high-performance database - binaries
ii  virtuoso-opensource-6.1-common        6.1.6+dfsg-4                      i386         high-performance database - common files


virtuoso-minimal is a depedency for baloo.

tassos wrote:virtuoso-minimal is a depedency for baloo.

Baloo does not use virtuoso.
It was used by nepomuk though, and needed for the migration from Nepomuk to Baloo of course.

So apparently you are actually still using Nepomuk? (those error messages would suggest that as well)

So, which version of dolphin are you using?
4.13 should use libbaloowidgets4 for the information panel, which of course uses Baloo, not Nepomuk.
If you still have an older dolphin, it would still use nepomuk-core and therefore Nepomuk and virtuoso, which you don't seem to have running. (AFAIK baloo turns it off after the migration is completed)

Another note if it wasn't clear already:
Comments/tags/ratings only work on folders that are indexed.
If you are in a not-indexed folder, the widgets are still there and you can add comments/tags/ratings, but existing ones will not be shown.
I filed a bug report about this some time ago: https://bugs.kde.org/show_bug.cgi?id=337026
So check in Baloo's settings which folders are excluded.

I don't have any folders excluded and it seems that I am using the latest dolphin.

Code: Select all

ii  dolphin                               4:4.13.3-1                        i386         file manager

tassos wrote:I don't have any folders excluded and it seems that I am using the latest dolphin.

Hm, I don't know then. This works fine here on openSUSE and worked fine in KUbuntu 14.04 when I tried.

Apparently something seems not quite right with the Debian packages. You do know about this thread, and the reply to your post by luebking, right?
viewtopic.php?f=154&t=122256

Maybe you should better ask in a distribution-specific forum.

Just an idea though:
As your packages seem to still be using Nepomuk/virtuoso, it might help/be necessary to enable Nepomuk in systemsettings->Desktop Search...
Or maybe even _disabling_ it explicitely might help?

Yeah I know about that thread and good job on your part reminding me so I could append info on that, especially the dolphin log. The strange thing is that nepomuk packages are removed from my system, the migrator application says that everything has been migrated and there is no way to add/display tags or ratings in doplhin which tries to talk to virtuoso through nepomuk starting up. Madness!

I filed this bug some days ago https://bugs.kde.org/show_bug.cgi?id=338496 against baloo however I am not sure whether this is a baloo problem, a dolphin thing or a debian specific issue.

tassos wrote:Yeah I know about that thread and good job on your part reminding me so I could append info on that, especially the dolphin log. The strange thing is that nepomuk packages are removed from my system, the migrator application says that everything has been migrated and there is no way to add/display tags or ratings in doplhin which tries to talk to virtuoso through nepomuk starting up. Madness!

Yeah, right.
It shouldn't talk to Nepomuk or virtuoso, but should use Baloo instead.

Have you tried to install the Nepomuk packages again, or is this not possible?
(I do still have them installed here on openSUSE/KDE 4.14)

I filed this bug some days ago https://bugs.kde.org/show_bug.cgi?id=338496 against baloo however I am not sure whether this is a baloo problem, a dolphin thing or a debian specific issue.

As I said I think this is a debian specific/packaging issue.
It works fine on openSUSE and KUbuntu AFAICT.