Bug 81927 - Installation screws up file linkings to Microsoft Office, although installer was instructed not to touch them
Summary: Installation screws up file linkings to Microsoft Office, although installer ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version: 4.3.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-30 18:33 UTC by ovv123
Modified: 2015-01-05 20:26 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description ovv123 2014-07-30 18:33:25 UTC
Preambule: Dutch LibreOffice (32-bits?) installment on Dutch Windows 8.1 system, Intel 64-bits. Just a normal installation on a standard Windows version (Dutch) with all other application programs closed.

Earlier versions of LibreOffice, at least 4.2.5:
In the Installation wizard: unchecked (something like): leave the file linkings to Microsoft Office alone. So, the LibreOffice installer was not allowed to touch the file linkings of Microsoft Office documents!
Expected result: after installing LibreOffice all my MS Office documents should be linked to MS Word, MS Excel and MS PowerPoint respectively.
Result after installing: all Microsoft Office documents were linked to LibreOffice.
Remedy: opening all MS Office documents types once with the MS Office module in question. This changed the file linkings from LibreOffice to MS Office.

LibreOffice 4.3.0 screwed up linkings big time.
All documents linkings between Microsoft Office documents and Microsoft Office programs seemed to be intact.
However, double clicking on a Microsoft Office document or clicking on one of my Microsoft Office icons in the taskbar started not the Microsoft Office module as expected, but started some "Windows Installer".
I have no idea which installer, I cancelled immediately.
Again: the LibreOffice installer should have left all linkings to Microsoft documents alone, as instructed in the installer!
I found out a remedy: run the program Microsoft Office Diagnostics (NL: Microsoft Office Diagnostische gegevens). Luckily (the coupling to) this program wasn't screwed up. Somehow the MS Office Diagnostics program found out about the screwed up linkings and restrored them to the correct linkings.  There was no need to install something or another.

Please change the behavior in the LibreOffice installer. Leave all file linkings to Microsoft Office alone if you promise the user that these linkings will not be touched!
Comment 1 Beluga 2015-01-04 15:59:10 UTC
Yep, I actually experienced the same today, when I installed on Win 8.1.
Minus any Windows Installer craziness, that is.

Lowering priority, though: https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg

LibO 4.4 RC1 on Win 8.1 32-bit + MSO 2013.
Comment 2 gdeprins 2015-01-05 14:44:49 UTC
I had the same problem on Windows 7 with MS Office 2010 today. When you continue the MS Office installation that appears after launching any of the components (e.g. Word, Excel) it will finish very quickly and repair the links for all Office components without re-installing Office.
Comment 3 ovv123 2015-01-05 20:26:29 UTC
Priority should be high in my opinion. According to the LO "Bug priority triage flowchart" the bug results in "the inability to open particular documents".
For me and several others this bug results in not choosing to update or install LibreOffice. It is a long standing problem, which has gotten worse.
But, since I suspect most of the developers of the LO package don't care too much about products of others (sorry, this is my experience with several software developers), I set the priority to medium.
I still would like to give the bug a high priority though. Developers: choose wisely!
Probably the problem will be solved by simply updating your Windows compiler.


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.