|
a |
|
b/website/BUGS.html |
|
|
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
|
2 |
<html>
|
|
|
3 |
<head>
|
|
|
4 |
<title>Recoll known bugs</title>
|
|
|
5 |
|
|
|
6 |
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
|
|
7 |
<meta name="Author" content="Jean-Francois Dockes">
|
|
|
8 |
<meta name="Description" content=
|
|
|
9 |
"recoll is a simple full-text search system for unix and linux
|
|
|
10 |
based on the powerful and mature xapian engine">
|
|
|
11 |
<meta name="Keywords" content=
|
|
|
12 |
"full text search, desktop search, unix, linux">
|
|
|
13 |
<meta http-equiv="Content-language" content="en">
|
|
|
14 |
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
|
|
|
15 |
<meta name="robots" content="All,Index,Follow">
|
|
|
16 |
|
|
|
17 |
<link type="text/css" rel="stylesheet" href="styles/style.css">
|
|
|
18 |
</head>
|
|
|
19 |
|
|
|
20 |
<body>
|
|
|
21 |
|
|
|
22 |
<div class="rightlinks">
|
|
|
23 |
<ul>
|
|
|
24 |
<li><a href="index.html">Home</a></li>
|
|
|
25 |
<li><a href="download.html">Downloads</a></li>
|
|
|
26 |
<li><a href="doc.html">Documentation</a></li>
|
|
|
27 |
</ul>
|
|
|
28 |
</div>
|
|
|
29 |
|
|
|
30 |
<div class="content">
|
|
|
31 |
|
|
|
32 |
<h1>Known bugs in current and older versions</h1>
|
|
|
33 |
|
|
|
34 |
<p><i>Bugs that are listed in an older version section are
|
|
|
35 |
supposedly fixed in later versions. Bugs listed in the
|
|
|
36 |
topmost section may also exist in older versions.</i></p>
|
|
|
37 |
|
|
|
38 |
<h2>Latest (recoll 1.11.0 + xapian 1.0.x)</h2>
|
|
|
39 |
<ul>
|
|
|
40 |
|
|
|
41 |
<li> When Recoll is built with qt 4.4.0, the icons in the
|
|
|
42 |
result list are all displayed at the top of the page and
|
|
|
43 |
garbled. This appears to be a qt bug, fixed in 4.4.1. Use
|
|
|
44 |
either qt 4.3.x or 4.4.1
|
|
|
45 |
|
|
|
46 |
<li> If the user-chosen result list entry format results in
|
|
|
47 |
several paragraphs (in the qt textedit sense), right clicks
|
|
|
48 |
will only work inside the first one for each entry.
|
|
|
49 |
|
|
|
50 |
<li> When a mime type has an external viewer defined, but the
|
|
|
51 |
actual file is compressed (ie: xxx.txt.gz), recoll will try
|
|
|
52 |
to start the external viewer on the compressed file, which
|
|
|
53 |
will not work in most cases.
|
|
|
54 |
|
|
|
55 |
<li> NEAR crashes: 1.6 has added NEAR searches. Unlike what
|
|
|
56 |
recoll did with PHRASES, stemming expansion is performed on
|
|
|
57 |
terms inside NEAR clauses (except if prevented by a
|
|
|
58 |
capitalized entry of course). There is a bug in Xapian (all
|
|
|
59 |
versions as far as I know), where NEAR does not support
|
|
|
60 |
multiple OR subclauses, as would result from a multiple
|
|
|
61 |
expansion. This manifests itself by a 'not implemented'
|
|
|
62 |
Xapian exception. Workarounds:
|
|
|
63 |
<ul>
|
|
|
64 |
<li>Prevent expansion of NEAR terms (possibly except one) by
|
|
|
65 |
capitalizing them.
|
|
|
66 |
|
|
|
67 |
<li>Or apply the following patch to xapian, inside the
|
|
|
68 |
"api/" directory:
|
|
|
69 |
http://www.recoll.org/xapian/xapNearDistrib-1.0.patch
|
|
|
70 |
or fetch the already patched source:
|
|
|
71 |
http://www.recoll.org/xapian/xapian-core-1.0.7-recollNEARpatch.tar.gz
|
|
|
72 |
then recompile, and install.
|
|
|
73 |
</li>
|
|
|
74 |
</ul>
|
|
|
75 |
|
|
|
76 |
I hope that an equivalent fix will make it into xapian at
|
|
|
77 |
some point (the current fix is not completely correct but
|
|
|
78 |
still handles most useful cases).</li>
|
|
|
79 |
|
|
|
80 |
<li> If you are seeing a delay of a few seconds before the
|
|
|
81 |
result list displays for the first query of a recoll
|
|
|
82 |
instance, try changing the result list font in the query
|
|
|
83 |
preferences. This is not a recoll problem, I don't know the
|
|
|
84 |
exact cause (I've seen it happen with "Sans Serif" and go
|
|
|
85 |
away with Helvetica or Arial).
|
|
|
86 |
|
|
|
87 |
<li> Under some versions of KDE (ie: Fedora FC5 KDE
|
|
|
88 |
3.5.4-0.5.fc5), there is a problem with the window stacking
|
|
|
89 |
order. Opening the "browse" file selection dialog from the
|
|
|
90 |
advanced search dialog will stack the latter under the main
|
|
|
91 |
window, possibly making it invisible. This is quite probably
|
|
|
92 |
a Kwin bug, possibly related to
|
|
|
93 |
http://bugs.kde.org/show_bug.cgi?id=79183 or a correction
|
|
|
94 |
thereof.
|
|
|
95 |
|
|
|
96 |
<li> Under Solaris, it is necessary to perform initial indexing with the
|
|
|
97 |
recollindex program (the recoll index thread doesn't work for creating
|
|
|
98 |
the database). Don't know the reason. Only idea I have is problem with
|
|
|
99 |
exception handling (recoll catches an exception while trying the
|
|
|
100 |
yet inexistant db).</li>
|
|
|
101 |
</ul>
|
|
|
102 |
|
|
|
103 |
<h2>1.10.6</h2>
|
|
|
104 |
<ul>
|
|
|
105 |
<li> If the locale is not utf-8, non-ascii command line
|
|
|
106 |
arguments to recoll and recollq are not converted to utf-8,
|
|
|
107 |
which may prevent, for example, the kde applet from
|
|
|
108 |
working. The workaround is to apply the following one-line
|
|
|
109 |
fix to qtgui/main.cpp, recompile and install recoll:
|
|
|
110 |
<pre>
|
|
|
111 |
386c386
|
|
|
112 |
< sSearch->setSearchString(QString::fromUtf8(qstring.c_str()));
|
|
|
113 |
---
|
|
|
114 |
> sSearch->setSearchString(QString::fromLocal8Bit(qstring.c_str()));
|
|
|
115 |
</pre>
|
|
|
116 |
</li>
|
|
|
117 |
</ul>
|
|
|
118 |
|
|
|
119 |
<h2>1.10.1</h2>
|
|
|
120 |
|
|
|
121 |
<ul>
|
|
|
122 |
<li> A relatively simple error case can cause the indexer to
|
|
|
123 |
stop processing an mbox file (forgetting all subsequent
|
|
|
124 |
messages). More specifically, this happens when encountering
|
|
|
125 |
more than than a few dozen errors while handling
|
|
|
126 |
attachments. This is relatively common: for exemple if an
|
|
|
127 |
external helper application is missing and multiple
|
|
|
128 |
attachments of the affected type are found (ie: multiple
|
|
|
129 |
images and no exiftool). Workaround: install the helper
|
|
|
130 |
application.
|
|
|
131 |
<li> The decoding of base-64 data in emails fails in a relatively uncommon
|
|
|
132 |
but sometimes encountered case.
|
|
|
133 |
<li> In a preview window, when walking the search term hits with the
|
|
|
134 |
Previous/Next buttons, 'Previous' actually acts as 'Next' (it does work
|
|
|
135 |
normally for the local search).
|
|
|
136 |
<li> Problems in detecting message separators inside Thunderbird mailboxes
|
|
|
137 |
(quite probably mainly for messages imported from outlook?). Can lead to
|
|
|
138 |
unindexed messages, and even apparently indexer crashes in some cases.
|
|
|
139 |
<li> File names indexed as terms can sometimes overflow the maximum term
|
|
|
140 |
size, halting the indexing.
|
|
|
141 |
<li> For Phrase/Near searches, only the first term group is highlighted in
|
|
|
142 |
preview.
|
|
|
143 |
</ul>
|
|
|
144 |
|
|
|
145 |
<h2>1.10.0</h2>
|
|
|
146 |
<ul>
|
|
|
147 |
|
|
|
148 |
<li> If a filter fails while trying to extract the data from a file, the file
|
|
|
149 |
will not be indexed at all (not even the file name). The file
|
|
|
150 |
name should be indexed in this case. This happens in particular in the
|
|
|
151 |
very common case where the helper application is not installed (ie:
|
|
|
152 |
missing Exiftool -> no *.jpg names in the index).
|
|
|
153 |
|
|
|
154 |
<li> If several query language "ext:" qualifiers are specified, they will be
|
|
|
155 |
joined by an AND instead of OR, resulting in no results. Using an
|
|
|
156 |
explicit OR doesn't work (actually OR + field names is generally
|
|
|
157 |
broken). In some cases, you can use a "type:" qualifier as a workaround.
|
|
|
158 |
|
|
|
159 |
|
|
|
160 |
</ul>
|
|
|
161 |
<h2>1.9.x</h2>
|
|
|
162 |
<ul>
|
|
|
163 |
<li> Problems have been reported indexing big mailstores (several hundreds of
|
|
|
164 |
thousands of messages): resulting in a very big database and even
|
|
|
165 |
crashes.
|
|
|
166 |
|
|
|
167 |
</ul>
|
|
|
168 |
<h2>1.8.2</h2>
|
|
|
169 |
<ul>
|
|
|
170 |
<li> Under ubuntu (at least, maybe debian too), the default awk interpreter
|
|
|
171 |
(mawk) is ancient, and the recoll pdf input filter does not
|
|
|
172 |
work (removes all space characters). This can be solved by installing the
|
|
|
173 |
gawk package.
|
|
|
174 |
$ apt-get install gawk
|
|
|
175 |
$ update-alternatives --set awk /usr/bin/gawk
|
|
|
176 |
|
|
|
177 |
<li> There are sometimes problems with document deletions: the index can
|
|
|
178 |
get in a state where deleted or moved documents are not purged from the
|
|
|
179 |
index (the log file says that the doc are deleted, but they aren't
|
|
|
180 |
actually). When this happens, the only solution currently is to reindex
|
|
|
181 |
from scratch (recollindex -z). This is due to a xapian bug, which is
|
|
|
182 |
fixed in xapian 1.0.2, or you can apply the following patch to xapian
|
|
|
183 |
1.0.1 to fix it:
|
|
|
184 |
http://www.lesbonscomptes.com/recoll/xapian/xapian-delete-document.patch
|
|
|
185 |
|
|
|
186 |
<li> The dates shown for email attachments in a result list are the email
|
|
|
187 |
folder modification date. This should be inherited from the parent
|
|
|
188 |
message instead.
|
|
|
189 |
|
|
|
190 |
<li> There are a few problems in the qt4 version of recoll:
|
|
|
191 |
<li> Some accelerators (esc-spc, ctl-arrow) do not work, neither do
|
|
|
192 |
copy/paste between the result list and preview windows and x11
|
|
|
193 |
applications.
|
|
|
194 |
<li> The qt4 q3textedit::find() method is extremely slow, so that
|
|
|
195 |
positionning to first search term in Recoll preview has been disabled,
|
|
|
196 |
and the application will sometimes appear to be looping when using the
|
|
|
197 |
find feature in the preview window (it's not looping, it's searching...)
|
|
|
198 |
|
|
|
199 |
</ul>
|
|
|
200 |
<h2>1.8.1</h2>
|
|
|
201 |
<ul>
|
|
|
202 |
<li> This is not really a bug but .beagle really should be included in
|
|
|
203 |
"skippedNames", or you end up indexing the beagle text cache, which is
|
|
|
204 |
not really desirable.
|
|
|
205 |
<li> Doc bug: the manual states that the query language supports a "mime:"
|
|
|
206 |
switch to filter mime types. There is currently no such thing.
|
|
|
207 |
|
|
|
208 |
|
|
|
209 |
</ul>
|
|
|
210 |
<h2>1.7.5</h2>
|
|
|
211 |
<ul>
|
|
|
212 |
<li> Debian and Ubuntu: the rclsoff Openoffice filter doesn't work,
|
|
|
213 |
because of an incorrect shell syntax (understood by bash but not sh). To
|
|
|
214 |
fix, you edit /usr[/local]/share/recoll/filters/rclsoff and can change
|
|
|
215 |
the line:
|
|
|
216 |
trap cleanup EXIT SIGHUP SIGQUIT SIGINT SIGTERM
|
|
|
217 |
into:
|
|
|
218 |
trap cleanup EXIT HUP QUIT INT TERM
|
|
|
219 |
or download the updated filter from the filters page:
|
|
|
220 |
http://www.recoll.org/filters/filters.html
|
|
|
221 |
|
|
|
222 |
</ul>
|
|
|
223 |
<h2>1.7.3</h2>
|
|
|
224 |
<ul>
|
|
|
225 |
<li> Processing will stop on first error while indexing an mbox file. This
|
|
|
226 |
could happen just because an attachment could not be decoded, and can
|
|
|
227 |
cause non-indexing of many messages. The most probable cause of error is
|
|
|
228 |
a missing filter (ie for ms-word files), so the temporary workaround
|
|
|
229 |
would be to install the missing filters. This bug is specific to 1.7 and
|
|
|
230 |
1.6 users need not worry. A correction will be issued very soon.
|
|
|
231 |
<li> Messages of type multipart/signed are not indexed.
|
|
|
232 |
|
|
|
233 |
</ul>
|
|
|
234 |
<h2>1.6.2</h2>
|
|
|
235 |
<ul>
|
|
|
236 |
<li> Relatively unfrequent issue with message boundary detection in mbox
|
|
|
237 |
files, could cause miscellaneous problems.
|
|
|
238 |
<li> Executing an external viewer for a file with single-quotes in the name
|
|
|
239 |
would not work.
|
|
|
240 |
|
|
|
241 |
</ul>
|
|
|
242 |
<h2>1.5.10</h2>
|
|
|
243 |
<ul>
|
|
|
244 |
<li> If a defaultcharset was set in the configuration file for a subdirectory,
|
|
|
245 |
it would stay in effect for all subsequent files/directories (except if
|
|
|
246 |
explicitely overridden), potentially causing many transcoding errors.
|
|
|
247 |
|
|
|
248 |
</ul>
|
|
|
249 |
<h2>1.5.[1-7]</h2>
|
|
|
250 |
<ul>
|
|
|
251 |
<li> Dates in result list come from the file's ctimes, which may be confusing
|
|
|
252 |
<li> Some rare MIME messages with null boundaries can crash the indexer.
|
|
|
253 |
|
|
|
254 |
</ul>
|
|
|
255 |
<h2>1.5.0</h2>
|
|
|
256 |
<ul>
|
|
|
257 |
<li> Under some conditions, recoll startup and exit could be very slow: the
|
|
|
258 |
simple search history list had serious problems with non-ascii strings,
|
|
|
259 |
whose size sometimes doubled at each program startup/stop.
|
|
|
260 |
|
|
|
261 |
</ul>
|
|
|
262 |
<h2>1.3.3</h2>
|
|
|
263 |
<ul>
|
|
|
264 |
|
|
|
265 |
<li> Several of the external filters did not handle path names with embedded
|
|
|
266 |
spaces (rcluncomp rclsoff rclps rclmedia rcldjvu). This is fixed in 1.4.
|
|
|
267 |
|
|
|
268 |
<li> If your QT installation is built with the QT_NO_STL flag, Recoll will not
|
|
|
269 |
compile. I have a patch for this (will be fixed in the next release),
|
|
|
270 |
contact me if you get the problem. Typical error message:
|
|
|
271 |
main.cpp:160: error: no match for 'operator+=' in 'msg += reason'
|
|
|
272 |
|
|
|
273 |
<li> The 'None of these words' field in the complex search does not work if
|
|
|
274 |
there are no other filled fields (it transforms into an ordinary
|
|
|
275 |
search). Workaround: enter very common term(s) in the 'any of these
|
|
|
276 |
words' field.
|
|
|
277 |
|
|
|
278 |
<li> Indexing cannot currently be conveniently and cleanly
|
|
|
279 |
stopped when it's started. You can kill the process, and
|
|
|
280 |
keyboard interrupt might work, but this may leave the
|
|
|
281 |
database in a bad state. This is fixed in the upcoming
|
|
|
282 |
release, there is no current workaround.
|
|
|
283 |
</ul>
|
|
|
284 |
|
|
|
285 |
<h2>1.2.2</h2>
|
|
|
286 |
<ul>
|
|
|
287 |
<li> The preview window is supposed to scroll after loading the document so
|
|
|
288 |
that the first search term is visible. This does not work in many cases.
|
|
|
289 |
<li> The result list title is not shown for sorted lists
|
|
|
290 |
|
|
|
291 |
Notes on older versions:
|
|
|
292 |
<li> Trouble compiling on some linux systems (Gentoo and Slackware?). There
|
|
|
293 |
existed a quite common issue where the Recoll link will fail trying to
|
|
|
294 |
use a libstdc++.la file. This was due to a problem with the xapian-config
|
|
|
295 |
program. A workaround has been included in the configure script for
|
|
|
296 |
recoll 1.2.2, and the problem should not occur any more.
|
|
|
297 |
|
|
|
298 |
<li> Case-insensitive search should now work in most cases
|
|
|
299 |
(used to not work except for accented ascii).
|
|
|
300 |
|
|
|
301 |
<li> All directories and files with names beginning with a dot were ignored
|
|
|
302 |
by the skippedNames directive in the default recoll.conf file from
|
|
|
303 |
older versions (no indexation of mozilla or thunderbird email !). An
|
|
|
304 |
upgrade will not fix this (it will not modify an existing
|
|
|
305 |
configuration). You need to edit recoll.conf by hand and remove the .*
|
|
|
306 |
from skippedNames.</li>
|
|
|
307 |
|
|
|
308 |
</ul>
|
|
|
309 |
|
|
|
310 |
</div>
|
|
|
311 |
</body>
|
|
|
312 |
</html>
|