https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #47 from Michail Pappas ---
Forgot to mention that AV is installed on both systems. System 2 has a stock
Windows 10 defender, whereas System 1 has ESET endpoint protection 10.
--
You are receiving this mail because:
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #46 from Michail Pappas ---
Created attachment 190528
--> https://bugs.documentfoundation.org/attachment.cgi?id=190528=edit
MSI transform file to NOT associate MS office files with LibO during GPO-based
installations
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #45 from Michail Pappas ---
Created attachment 190527
--> https://bugs.documentfoundation.org/attachment.cgi?id=190527=edit
MSI transform file to associate MS office files with LibO during GPO-based
installations
Transform
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #44 from Michail Pappas ---
(In reply to Mike Kaganski from comment #42)
> What about an antivirus, that might possibly block/scan some files based on
> extension?
Made some tests on two AD-joined systems, both running
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #43 from Mike Kaganski ---
(In reply to Lobotomik from comment #32)
> This issue is languishing unassigned and nobody has looked at it since you
> looked at it last time. Is there something we could do to help get it
>
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #42 from Mike Kaganski ---
(In reply to Oliver Brinzing from comment #26)
> My log file contained an entry for every *.odt file skipped during index
> process:
>
> 87f36909 1d5de88
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #41 from Michail Pappas ---
(In reply to Oliver Brinzing from comment #16)
> i did some test using "ifilttst.exe" from:
> https://docs.microsoft.com/en-us/previous-versions/windows/desktop/indexsrv/
> ifilttst
>
> e.g.:
>
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #40 from Michail Pappas ---
That's some laggy response, but had the time so...
(In reply to Oliver Brinzing from comment #26)
> I forgot to mention: Windows Search writes a log file:
>
>
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #39 from Michail Pappas ---
Issue persists on: Version: 7.5.7.1 (X86_64) / LibreOffice Community
Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126
CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL:
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #38 from QA Administrators ---
Dear Michail Pappas,
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
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
Gilward Kukel changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #37 from Gilward Kukel ---
When I save an ODT file with WordPad, its contents are found. When I save one
with LibreOffice Writer, its contents are not found.
--
You are receiving this mail because:
You are the assignee for
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #36 from Lobotomik ---
FWIW, I have completely uninstalled LibreOffice and done a clean install of
7.1.1, making sure to start in safe mode and wipe out all existing user
configuration, but that has not changed anything.
--
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #35 from Lobotomik ---
I just tried saving a .docx file as .odt hoping the issue had been cured, but
the bug persists.
I think the key to get this fixed is that simply renaming the .odt file to .sxw
causes the file to be
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #34 from MariaC ---
I have this problem but only for old Open Office Documents. Newly created odt
files are index right away. Old are not even when windows indexing is
finnished.
--
You are receiving this mail because:
You
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #33 from Lobotomik ---
(In reply to Lobotomik from comment #32)
> For the time being, I'm trying to batch convert all my files to .docx and
> use .docx as default to get rid of the issue. For those interested in doing
> that,
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #32 from Lobotomik ---
Hello Stuart,
This issue is languishing unassigned and nobody has looked at it since you
looked at it last time. Is there something we could do to help get it solved?
If a simple rename to .sxw is
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
V Stuart Foote changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #31 from Lobotomik ---
I'm adding this information in the hope it helps fixing what seems to be a
trivial issue (bearing in mind indexing works when you change the file
suffix!).
I also hope that some additional information
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #30 from Lobotomik ---
I've been suffering the same for a long time.
* Windows 10 Home 1909 64-bit, running at home.
* LibreOffice 6.4.4.2 as of today, but it happened just the same with previous
versions.
* In Advanced
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #29 from AngelaAngie ---
Nice post for any query and help related to this or any other, you should go to
https://rs4264979.wixsite.com/mysite/post/hoe-hp-printerfout-79-op-te-lossen;>Klantenservice
Belgie
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #28 from Michail Pappas ---
Not a bump, just a request whether I can provide something else to help this
investigation, after the registry keys from the problematic installation were
provided on
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #27 from Michail Pappas ---
(In reply to V Stuart Foote from comment #24)
> (In reply to Michail Pappas from comment #23)
>
> @Michall, rather seems they are intertwined. NEEDINFO to you to at your
> 'work' systems, open a
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #26 from Oliver Brinzing ---
I forgot to mention: Windows Search writes a log file:
%ProgramData%\Microsoft\Search\Data\Applications\Windows\GatherLogs\SystemIndex
SystemIndex.1.gthr
My log file contained an entry for every
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #25 from Michail Pappas ---
(In reply to V Stuart Foote from comment #24)
> (In reply to Michail Pappas from comment #23)
>
> @Michall, rather seems they are intertwined. NEEDINFO to you to at your
> 'work' systems, open a
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #24 from V Stuart Foote ---
(In reply to Michail Pappas from comment #23)
@Michall, rather seems they are intertwined. NEEDINFO to you to at your 'work'
systems, open a regedit session and check the recorded persistent
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #23 from Michail Pappas ---
(In reply to Michail Pappas from comment #19)
> (In reply to Oliver Brinzing from comment #17)
> > (In reply to Michail Pappas from comment #14)
> > > Being clueless on how to proceed from here, I
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #22 from Oliver Brinzing ---
Created attachment 157740
--> https://bugs.documentfoundation.org/attachment.cgi?id=157740=edit
Win10x64_with_LO61_and_MS_Office_2016_odt_ok.reg
I was able to make it work for my notbook
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #21 from Oliver Brinzing ---
FYI: The notebooks that I used for the test are not in a domain.
After making changes to the registry/renaming file extensions, I always had the
index recreated.
--
You are receiving this mail
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #20 from Mike Kaganski ---
The thing is: if renaming an ODT to SXW makes the file to be indexed, that
means that LibreOffice code works OK: no other filter (except OOo/AOO, which
are hopefully outside of the scope here, to
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #19 from Michail Pappas ---
(In reply to Oliver Brinzing from comment #17)
> (In reply to Michail Pappas from comment #14)
> > Being clueless on how to proceed from here, I should first ask on how should
> > I handle the bug
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #18 from Mike Kaganski ---
Could there be difference in filter registration between 32- and 64-bit
registry?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #17 from Oliver Brinzing ---
(In reply to Michail Pappas from comment #14)
> Being clueless on how to proceed from here, I should first ask on how should
> I handle the bug at hand: that is, should I close this one and file a
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #16 from Oliver Brinzing ---
With
a) Win10x64 LO 6.1x64 Notebook with ms office 2016 installed
b) Win10x64 LO 6.1x64 Notebook no ms office installed
i did some test using "ifilttst.exe" from:
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #15 from Michail Pappas ---
Created attachment 157614
--> https://bugs.documentfoundation.org/attachment.cgi?id=157614=edit
Windows indexing properties
Not sure if this is related, but the indexing options show a GUID
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
Michail Pappas changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEEDINFO
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #13 from Oliver Brinzing ---
(In reply to Michail Pappas from comment #9)
> (In reply to V Stuart Foote from comment #4)
> Oliver, what's your exact Windows configuration (7/8/10 32-64bit and build
> number) and your LibO
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #12 from V Stuart Foote ---
(In reply to Michail Pappas from comment #11)
> BTW, I don't have office installed at either work or home.
Maybe. But if the still needed F3 search turns up the odffilter.dll string, or
the GUIDs
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #11 from Michail Pappas ---
(In reply to V Stuart Foote from comment #10)
> You'd need to look for the MS Office filter GUID pairs, the CLSID for the
> odffilter.dll and the GUID for the file type (MS Office defines at least
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #10 from V Stuart Foote ---
(In reply to Michail Pappas from comment #9)
>
> The files referenced by HKCR\CLSID\{7BC0E713-5703-45BE-A29D-5D46D8B39262}
> refer to C:\Program Files\LibreOffice\program\shlxthdl\ooofilt.dll on
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #9 from Michail Pappas ---
(In reply to V Stuart Foote from comment #4)
> Yes that GUID is the correct CLSID, inherited by the LibreOffice source from
> OOo (circa 2004), HKCR\CLSID\{7BC0E710-5703-45BE-A29D-5D46D8B39262}
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #8 from Oliver Brinzing ---
Created attachment 157581
--> https://bugs.documentfoundation.org/attachment.cgi?id=157581=edit
test blindtext files
--
You are receiving this mail because:
You are the assignee for the
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #7 from Oliver Brinzing ---
Created attachment 157580
--> https://bugs.documentfoundation.org/attachment.cgi?id=157580=edit
windows search result
Attached picture shows the result:
Content indexing with Windows Search
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #6 from Oliver Brinzing ---
Checked with:
a) Notebook with ms office 2016 installed:
Search uses: "[x]odt Open Document Format ODT Filter"
C:\Program Files (x86)\Microsoft
Office\root\VFS\ProgramFilesCommonX64\Microsoft
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #5 from V Stuart Foote ---
> (In reply to Michail Pappas from comment #3)
>
> > I'm not sure of how one finds the GUID of the filter.
Sorry, should have included that from a 'regedit' session, do search
against either
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #4 from V Stuart Foote ---
(In reply to Michail Pappas from comment #3)
> I'm not sure of how one finds the GUID of the filter. Perhaps it's
> 7BC0E710-5703-45BE-A29D-5D46D8B39262 ?
>
Yes that GUID is the correct CLSID,
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #3 from Michail Pappas ---
(In reply to V Stuart Foote from comment #1)
> In the Windows shell, document thumbnails are being extracted and built (so
> show in the Windows explorer view for Icons & Tiles) while the Search bar
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
--- Comment #2 from Mike Kaganski ---
I also can't confirm (testing with 6.4.0.3 on Win10 right now, searching term
"lorem" typing in Start menu, and getting ODT documents in my Documents
directory among results). However, please open a
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
V Stuart Foote changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=130320
Michail Pappas changed:
What|Removed |Added
Summary|LibO 6: Windows 10 indexing |LibO 6: Windows 10 content
50 matches
Mail list logo
