1st 1.16 updates
This commit is contained in:
+28
-26
@@ -35,44 +35,19 @@
|
||||
supposedly fixed in later versions. Bugs listed in the
|
||||
topmost section may also exist in older versions.</i></p>
|
||||
|
||||
<h2><a name="b_latest">recoll 1.15</a></h2>
|
||||
<h2><a name="b_latest">recoll 1.16</a></h2>
|
||||
|
||||
<ul>
|
||||
|
||||
<li>Cancelling a preview in the GUI will also cancel the indexing
|
||||
thread if it is running.</li>
|
||||
|
||||
<li>Using the GUI preview while the indexing thread is running
|
||||
will sometimes crash the GUI or provoke other
|
||||
strangeness. This happens much more rarely than in 1.15.7,
|
||||
but still occurs. Workaround if this happens too frequently:
|
||||
use the standalone recollindex program instead of the GUI
|
||||
thread.</li>
|
||||
|
||||
<li>Real time indexer: uncontrolled concurrent access to
|
||||
the global configuration can cause a startup crash (mostly of
|
||||
big file trees because of timing issues).</li>
|
||||
|
||||
<li>Sorting by document and file size in the result table does
|
||||
not work.</li>
|
||||
|
||||
<li>Email messages for which there would be an error indexing
|
||||
an attachment would not be indexed at all.</li>
|
||||
<li>Text files bigger than 2 GB can not be indexed.</li>
|
||||
<li>After an upgrade, the recoll GUI sometimes crashes on
|
||||
startup. This is fixed by removing (back it up just in case)
|
||||
~/.config/Recoll.org/recoll.conf, the QSettings storage for
|
||||
recoll.</li>
|
||||
<li>Compressed man pages could not be previewed.</li>
|
||||
|
||||
<li>Performing a full index with release 1.11 or newer, over a
|
||||
version created with a much older recoll release may
|
||||
sometimes end with an error saying "backend doesn't
|
||||
implement metadata". If this happens, you need to delete
|
||||
the index directory (typically <em>~/.recoll/xapiandb/</em>)
|
||||
and restart indexing. For big indexes, to avoid losing
|
||||
time, removing the directory preventively may be preferable .</li>
|
||||
|
||||
<li>Under Solaris, it is necessary to perform the initial
|
||||
indexing with the recollindex program. For some unknown reason,
|
||||
the recoll index thread does not work for creating the database.
|
||||
@@ -100,6 +75,33 @@
|
||||
|
||||
<h2><a name="b_1_15_7">recoll 1.15.7</a></h2>
|
||||
<ul>
|
||||
<li>Sorting by document and file size in the result table does
|
||||
not work.</li>
|
||||
|
||||
<li>Email messages for which there would be an error indexing
|
||||
an attachment would not be indexed at all.</li>
|
||||
|
||||
<li>Performing a full index with release 1.11 or newer, over a
|
||||
version created with a much older recoll release may
|
||||
sometimes end with an error saying "backend doesn't
|
||||
implement metadata". If this happens, you need to delete
|
||||
the index directory (typically <em>~/.recoll/xapiandb/</em>)
|
||||
and restart indexing. For big indexes, to avoid losing
|
||||
time, removing the directory preventively may be preferable .</li>
|
||||
|
||||
<li>Text files bigger than 2 GB can not be indexed.</li>
|
||||
|
||||
<li>Using the GUI preview while the indexing thread is running
|
||||
will sometimes crash the GUI or provoke other
|
||||
strangeness. This happens much more rarely than in 1.15.7,
|
||||
but still occurs. Workaround if this happens too frequently:
|
||||
use the standalone recollindex program instead of the GUI
|
||||
thread.</li>
|
||||
|
||||
<li>Real time indexer: uncontrolled concurrent access to
|
||||
the global configuration can cause a startup crash (mostly of
|
||||
big file trees because of timing issues).</li>
|
||||
|
||||
<li>Using the result preview while the indexing thread is
|
||||
running will sometimes crash the GUI or provoke other
|
||||
strangeness. This is apparently due to insufficient
|
||||
|
||||
Reference in New Issue
Block a user