Bug Hunting Session
Bug 70748 - CONFIGURATION: Update LibreOffice to open MSO File Types
Summary: CONFIGURATION: Update LibreOffice to open MSO File Types
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.0.5.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-22 06:14 UTC by mieltxo
Modified: 2015-10-14 19:48 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mieltxo 2013-10-22 06:14:56 UTC
Problem description: 

Hello,

Until now I have Office and LibreOffice installed in some systems and each application opened its default extensions.

Now, I have uninstalled Microsoft Office and I dont know how to predetermine LibreOffice to open Office extensions.

I need to do through msiexec command to do in unattended way.

I execute the following without success: msiexec /qn LibreOffice_4.0.5_Win_x86.msi REGISTER_ALL_MSO_TYPES=1

The problem is that the msiexec unattended command appears to not working when the product is installed.

However, it works correctly when is not installed. 


Steps to reproduce:
1. Install Microsoft Office 2003 SP3
2. Install LibreOffice_4.0.5_Win_x86.msi without Office file extension association. 
3. Uninstall Microsoft Office 2003 SP3
4. Try to associate installed LibreOffice to open Microsoft Office extensions. To that, run msiexec command like this:

msiexec.exe /qn /i LibreOffice_4.0.5_Win_x86.msi REGISTER_ALL_MSO_TYPES=1

Current behavior:
No noticeable change in the configuration

Expected behavior:
Installed LibreOffice modify its configuration to open Microsoft Office files. 
              
Operating System: Windows XP
Version: 4.0.5.2 release
Comment 1 bfoman (inactive) 2013-11-20 21:34:42 UTC
Please see https://bugs.freedesktop.org/show_bug.cgi?id=60714#c2 and bug 44462.
I am not sure if command line should work when LO is installed, so leaving status of this bug as it is.
Comment 2 Robinson Tryon (qubit) 2015-01-20 07:37:58 UTC
(In reply to mieltxo from comment #0)
> Steps to reproduce:
> 1. Install Microsoft Office 2003 SP3
> 2. Install LibreOffice_4.0.5_Win_x86.msi without Office file extension
> association. 

Hi mieltxo,
LO 4.0 is EOL at this point. Can you still reproduce the problem with a modern 4.3 or 4.4 build?

Status -> NEEDINFO

(after you reply, please change status to UNCONFIRMED. thanks!)
Comment 3 QA Administrators 2015-09-04 02:56:03 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-09-03
Comment 4 QA Administrators 2015-10-14 19:48:13 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO

Message generated on: 2015-10-14