Problem description: Steps to reproduce: 1. Install with standard 2. .... 3. .... Current behavior: search in registry for shlxthdl under HKEY_CLASSES_ROOT\CLSID\ found path like this: C:\Program Files (x86)\LibreOffice 3.5\shlxthdl\shlxthdl.dll Expected behavior: path like this: C:\Program Files (x86)\LibreOffice 3.5\program\shlxthdl\shlxthdl.dll Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Andras Timar commited a patch related to this issue to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=2786c354ce4f7ff215fffe83ef242ee3b411fb13 fdo#46167 fix path of shell extension dll in registry
Thanks for the bug report!
Andras Timar commited a patch related to this issue to "libreoffice-3-5": http://cgit.freedesktop.org/libreoffice/core/commit/?id=02f57086c2d35b68b35c2f62926ef9597eb7a85f&g=libreoffice-3-5 fdo#46167 fix path of shell extension dll in registry It will be available in LibreOffice 3.5.1.
*** Bug 43708 has been marked as a duplicate of this bug. ***
*** Bug 46473 has been marked as a duplicate of this bug. ***
Although the wrong registry entries are fixed in 3.5.1, the shell extensions are still not enabled after a clean installation of LibreOffice 3.5.1 in Windows x64. Procedure: In a clean Windows 7 x64 system you install LibreOffice 3.5.1. After installation, libreoffice document properties and images are not shown in windows explorer. Manually registering the following dlls (win admin rights) solves the problem: regsvr32 "C:\Program Files (x86)\LibreOffice 3.5\program\shlxthdl\ooofilt_x64.dll" regsvr32 "C:\Program Files (x86)\LibreOffice 3.5\program\shlxthdl\shlxthdl_x64.dll" Best regards.
Iker, thanks for the bug report, but I think it should be a new bug, not reopening of another, related bug. I filed bug 47805.
I added Fix submitter as assignee because this will ease queries and bug tracking.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.