mahajanudit writes

I installed the application using ppa, installed recoll and recoll-lens but the lens is not showing up in the dash.

medoc writes

Hi,

I was just working on the recoll interface to unity. If you want to try it, you will need to use the "experimental" ppa. It has recoll-1.20 but there should be no trouble, it’s fully compatible with 1.19, the version change is mostly motivated by some packaging changes. So:

#!shell
sudo apt-get remove recoll-lens
sudo add-apt-repository ppa:recoll-backports/experiments
sudo apt-get update
sudo apt-get install unity-scope-recoll

Please let me know how this works for you

jf

mahajanudit writes

Hi Medoc, I actually did that, I search through all three of your ppa’s in launchpad and figured this might be it. I had two problems: Due to some reason, it kept adding "raring" as the distribution after adding. I had to manually change it to "saucy". I did it a couple of times just to make sure it happened again. Second: Scope adds a complete section below? (like photo, application and all) or just adds a source of search?

medoc writes

Forgot: it should better to first remove the other recoll packages too (before installing):

#!shell
sudo apt-get remove recoll python-recoll

mahajanudit writes

Yes, I removed everything and manually downloaded the packages from experimental ppa (Even after changing it to "saucy" after running update it kept on changing it to raring for some reason) I installed python3-recoll, python-recoll and recoll. Still doesn’t work..

medoc writes

The package that you need to install for saucy is unity-scope-recoll, not recoll-lens. Is this what you did ?

Else, results should appear at the top level, or more clearly, inside the "files and folder" section ( selected at the bottom of the dash panel)/

I did try this morning, on a fresh saucy, and it did seem to work, but I only uploaded this a few hours ago, so it’s quite plausible that there are issues still…

mahajanudit writes

Yes I did exactly that.. I only have those three packages installed along with unity-scope-recall… The files are being searched in the application "Recoll" but in the "files & folder" lens they are not showing up.. Is there some daemon i need to start or something? How can I check the scope is loaded at least by unity?

medoc writes

I tried again and it does work for me. I don’t think that recoll-lens conflicts with unity-scope-recoll, but it is certainly not needed either. So I’d try to remove everything recoll and just add back:

sudo apt-get install recoll python3-recoll unity-scope-recoll

Then you should see the following process running while the Dash is open and a little after, after running a basic query, even at the top level:

/usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/recoll.scope

If this does not work for you, I’ll try it on a fresh saucy install, in case there is something fishy with this instance…

mahajanudit writes

Yes, I tried everything point by point, still not working… I removed everything about recoll. Ran the query even, but in Dash when I switch to files and folders (Super + F) I still can’t search for text within files..

This is the error I get when I ran that command: udit@crusader:~$ python3 /usr/share/unity-scopes/scope-runner-dbus.py -s /usr/share/unity/scopes/files/recoll.scope Traceback (most recent call last): File "/usr/share/unity-scopes/scope-runner-dbus.py", line 92, in <module > main (sys.argv) File "/usr/share/unity-scopes/scope-runner-dbus.py", line 79, in main loader.load_scope(name) gi._glib.GError: Valid key file could not be found in search dirs

medoc writes

I really don’t know where the "key file" issue comes from. Did you try to run with a relative path too "-s files/recoll.scope" instead of "-s /usr…" ?

Here is what I tried:

Installed Ubuntu 13.10 i386 desktop in a blank virtual machine

sudo add-apt-repository ppa:recoll-backports/experiments
sudo apt-get update
sudo apt-get dist-upgrade
(reboot because of kernel upgrade)
sudo apt-get install unity-scope-recoll

recollindex

Dash - > does not work

 - > Exception while opening .recoll/history file

touch ~/.recoll/history

- > works

I’ll fix the "history" file problem, but I don’t think that this has anything to do with what you are seeing. It can only happen on a system where the GUI has never been used as the first query would create this file.

By the way, there is someone else who tried the Scope and it worked for them. There seems to be something weird with your system. Does it have a special history in terms of installing advance versions of Unity or such ?

mahajanudit writes

Let me try again, and I will update you..

mahajanudit writes

I had to reinstall my entire system. The ppa trouble I was telling you about was something to do with my system only and not your ppa. Now it works perfectly fine. Thanks for the amazing scope.

medoc writes

Scope working after solving packaging issues

ben101 writes

Hello, first of all: thanks for this great application. I started using it just a few days ago and already love it. Following your instructions above, I also managed to get the unity scope going unter 13.10. However, it seems the scope doesn’t show all the possible results recoll is finding. Do you have a hint what I can do or is it a problem with the unity dash? ben

medoc writes

I can’t be absolutely sure of the reason for what you are seeing, but a possible one is that the scope is artificially limited to presenting the first 30 results.

This is hard-coded in the python program (yes I should retrieve this from the config instead but the early versions had no config access… history).

If you want to change it you have to edit /usr/share/unity-scopes/scope-recoll/unity_recoll_daemon.py and change the MAX_RESULTS constant. Not too sure of the exact path for this file and no system at hand, but if you've got this far, I think that you can find out :)

mahajanudit writes

@medoc I have noticed that while indexing recoll (either through application or console) sometimes (in fact more often than not) the indexing hangs/stops at a particular file. After that it won’t proceed… Then I have to manually stop indexing and update it again. This keeps happening at random files.. Any idea why?

medoc writes

@mahajanudit This is weird, but this bug report is not convenient for exploring the issue. Please contact me by email: jf@dockes.org

ben101 writes

@medoc thanks! I will try to manipulate the MAX_RESULTS constant and let you know.