Shortly after libreoffice 18.104.22.168 is installed, SearchHostFilter.exe uses very high CPU for a number of hours. After it is done, odt files do not show up on the Windows 7 Search results. If I uninstall 22.214.171.124 and re-install 3.5.6, the install goes fine and I am able to see the odt files in Windows 7 Search results.
A little more light on this. I tried again with 126.96.36.199. SearchHostFilter ran again as described before, slowing down after a few hours. Still no odf filetypes in the Windows Search results. Re-installed 3.5.7 and SearchHostFilter ran a few minutes, then slowed down, and odf files appeared in the search results.
The interesting thing is that when looking at the indexing results, virtually the same number of files were indexed.
Note I tried different ways of installing 188.8.131.52 and got the same results (removing 3.5 first, renaming the LibreOffice file in the AppData/Roaming before installing, also restoring the 3.5 install and installing 3.6 on top).
I hope that this gets resolved and 3.5.7 won't be the end of the line for me (and I assume others who have this problem as well.)
Same observations with LO 3.6.4 and 3.6.4! I tested several times on different machines and under Windows7-Ulimate-32bit, Windows7-prof-64bit and Windows XP SP3 and it is always the same. So I confirm John's bug report.
There is a simple workaround: Just save the dlls of 3.5.7's folder ..program\shlxthdl\ and replace the correspondent dlls of 3.6 with the old ones and windows search indexing will function properly.
There is an equivalent Bug report: "Bug 56035 – Indexing for Search not working" in a different section: Component "LibreOffice".
Apparently a duplicate of bug 68487.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
*Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later)
*If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
*If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
*Update the version field
*Reply via email (please reply directly on the bug tracker)
*Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
I'm running LibreOffice 4.4.2 (just updated) on Windows 8.1 (x86); I no longer see this problem happen.