from: https://www.linuxquestions.org/questions/linux-software-2/recoll-works-wonderfully-in-linux-mint-fails-in-opensuse-tumbleweed-and-antergos-4175612825/
I have used and depended on Recoll in Linux Mint for several years. Version 1.21.5 in Mint reliably indexes a large directory on an external drive, without error messages. The configuration indicates the top directory to be indexed and the database directory, and nothing else. I have no settings in Local parameters, or in a recoll.conf file.
I recently configured boot partitions with openSUSE Tumbleweed and Antergos. I installed Recoll 1.23 on both, and couldn't get them to work. Each run reported thousands of errors, and tests afterward proved that Recoll failed to index many files.
I checked for missing helpers, experimented with local parameters and recoll.conf settings, but made no headway.
I haven't been able to find a log file of skipped/missed files, and don't see any mention in the documentation of where I can find such a log.
Any suggestions from Recoll users will be welcome. If others have had problems with Recoll in other-than-Debian-based distributions, I'd like to know that, too.
Discussion
-
Anonymous
2017-08-30Certainly!
UNRTF_SEARCH_PATH=/etc/unrtf:/usr/share/unrtf unrtf --noppict --html /mnt/username/doc/clip/test/test_subdir/2010earthquakeinsurancepremiums.rtf
failed to find noppict.conf in search path dirs
-
medoc
2017-08-30Oops sorry, --nopict
-
Anonymous
2017-08-31Very different results this time!
Command:
UNRTF_SEARCH_PATH=/etc/unrtf:/usr/share/unrtf unrtf --nopict --html /mnt/username/doc/clip/test/test_subdir/2010earthquakeinsurancepremiums.rtf
results:
<!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN>
-->
-->
Firms find cost of earthquake insurance too big a jolt
SMALL BUSINESS
Many forgo coverage because of the high premiums and deductibles.
April 19, 2010|By Cyndia Zwahlen and Nathan Olivarez-Giles
Like small-business owners across Southern California, Hilario Sanchez knows all too well the shaking, the damage and, of course, the inevitable cleanup after an earthquake.
... followed by the text of the clipped article, and the HTML formatting codes "span," "font," "body" and "html" (stripped of HTML formatting here, to insure that the codes appear in this message.)
-
medoc
2017-08-31Check if you have a bad UNRTF_SEARCH_PATH in your environment:
echo $UNRTF_SEARCH_PATH
If it is set, unset it (in your shell init file), or change it to the correct value.
If this is not set, it would appear that the default value compiled in the unrtf command you have is incorrect, I'm not too sure of what happened, you will have to see with the packager.
Last edit: medoc 2017-08-31
-
Anonymous
2017-08-31First, medoc, thanks again for your help in troubleshooting this problem.
The command echo $UNRTF_SEARCH_PATH produces no results.
As for the rest: I haven't edited a shell init file before, and am unsure of what to do next. I'll be happy to create a ~/.bashrc file or a file in /etc/profile.d (or elsewhere) if it will fix this problem, but don't know what to put in the file. I'm in new territory.
FWIW: Although I no longer have Arch-based Antergos on disk and can't easily test, my problems running Recoll in that distro were about the same. I wonder if unrtf is being incorrectly configured by more than one packager.
-
medoc
2017-08-31if you are using bash, you probably already have a .bashrc in hour home. Actually it is sourced by ~/.bash_profile.
just add:
export UNRTF_SEARCH_PATH=/etc/unrtf:/usr/share/unrtf
at the end.
I don't understand why unrtf is misconfigured on both systems,this is weird. I am currently installing OpenSUSE tumbleweed to have a look
-
Anonymous
2017-08-31(with a smile) Success! Adding export UNRTF_SEARCH_PATH=/etc/unrtf:/usr/share/unrtf to the existing .bashrc file didn't produce results, but I re-read your message, created a one line .bash_profile file, and tried again. Recoll indexed everything in the test directory.
For me, the timing is perfect; I'm about to leave town for a week, and was about to apologize for having to bow out of this troubleshooting thread. I'll be back on September 6, and can try other steps then, if you wish. In the meantime -- thanks to your patient help -- it looks like I have a functional Recoll in openSUSE. I'm grateful, medoc!
-
medoc
2017-09-01This definitely looks like an unrtf (probably packaging) issue.
As far as I can see there is no official package for unrtf on opensuse. Where did your unrtf come from ?
-
Anonymous
2017-09-06I just checked YAST --> Software Management. It says:
021.51-1.33-x86_64 from openSUSE_Tumbleweed ... and vendor obs://build.opensuse.org/KDE:Extra
That's the same repository that Recoll came from. I don't know of another one for openSUSE Tumbleweed. If my memory isn't playing tricks on me, I didn't install unrtf separately. I think it was installed automatically with Recoll.
Here's the file list, from Software Management:
/etc/unrtf
/etc/unrtf/html.conf
/etc/unrtf/latex.conf
/etc/unrtf/rtf.conf
/etc/unrtf/text.conf
/etc/unrtf/troff_mm.conf
/etc/unrtf/vt.conf
/usr/bin/unrtf
/usr/share/doc/packages/unrtf
/usr/share/doc/packages/unrtf/AUTHORS
/usr/share/doc/packages/unrtf/COPYING
/usr/share/doc/packages/unrtf/ChangeLog
/usr/share/doc/packages/unrtf/NEWS
/usr/share/doc/packages/unrtf/README
/usr/share/man/man1/unrtf.1.gz
/usr/share/unrtf
/usr/share/unrtf/SYMBOL.charmap
Last edit: Anonymous 2017-09-06
-
Anonymous
2017-09-07I just posted a related message on the openSUSE forum:
https://forums.opensuse.org/showthread.php/526978-Possible-packing-issue-with-unrtf
Thank you again for your help, medoc.