Problem description: Error while trying to launch English LibreOffice installer Steps to reproduce: 1. Install Windows 7 English with Russian regional settings. 2. Run msiexec /i LibO_3.5.4_Win_x86_install_multi.msi TRANSFORMS=:1033 3. Get the error "Error applying transforms. Verify that the specified transform paths are valid". Expected behavior: Installer runs in English language. Platform: Windows 7.
I have forgotten to mention that msiexec /i LibO_3.5.3_Win_x86_install_multi.msi TRANSFORMS=:1084 works fine, and msiexec /i LibO_3.5.3_Win_x86_install_multi.msi TRANSFORMS=:1049 fails with the same error.
There is no :1033 (a.k.a. en-US) transform, because the original MSI is en-US. However, when I tried :2057 (en-GB) or :7177 (en-ZA) under Russian regional settings, I got Russian installer, not English. While it does not make much sense to run run :1049 (ru) under Russian regional settings, it is unexpexted, that we get an error message. Interesting bug, but I doubt we can fix it.
So, is it possible to install English version and use English installer without changing regional settings to English?
never confirmed by QA. I change status from NEW to NEEDINFO. please tell if this issue is still present with current LibO 4.3.4.1 installer.
(In reply to tommy27 from comment #4) > please tell if this issue is still present with current LibO 4.3.4.1 > installer. Still present with LO 4.4.3.2. Encountered during install in OS environment set to pl_PL locale.
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/Bugzilla/Fields/Status/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
Error still happens with 5.0.4 installer so can't force en-us installer UI. Would be nice if the installer could just follow the set UI language or even system locale and not use location/input layout/region format/whatever like it seems to do now.
Seems we have enough confirmations, so setting to NEW.
(In reply to libreoffice from comment #0) > Problem description: > Error while trying to launch English LibreOffice installer > > Steps to reproduce: > 1. Install Windows 7 English with Russian regional settings. > 2. Run msiexec /i LibO_3.5.4_Win_x86_install_multi.msi TRANSFORMS=:1033 > 3. Get the error "Error applying transforms. Verify that the specified > transform paths are valid". > > Expected behavior: > Installer runs in English language. > > Platform: > Windows 7. Bug still present in LibreOffice_5.1.4. BTW Is it really impossible to add an option for selecting installer interface language?
According to suggestion in the Comment 6 below, I change status to UNCONFIRMED, just to try to catch QA attention :-)
(In reply to Witold Rakoczy from comment #10) > According to suggestion in the Comment 6 below, I change status to > UNCONFIRMED, just to try to catch QA attention :-) Well, you have weird habits..
(In reply to Buovjaga from comment #11) > (In reply to Witold Rakoczy from comment #10) > > According to suggestion in the Comment 6 below, I change status to > > UNCONFIRMED, just to try to catch QA attention :-) > > Well, you have weird habits.. Why? In Comment 6 (above, not below of course) there's the following statement: "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."
(In reply to Witold Rakoczy from comment #12) > In Comment 6 (above, not below of course) there's the following statement: > "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." Yes, but obviously that automated request was obsoleted by comment 7 and 8 and you are actually the third person to confirm, so there is even less reason to change it to unconfirmed.
It's possible that you are right. However in that case the comment 6 would be at least misleading, what isn't true, I think (see https://wiki.documentfoundation.org/QA/Bugzilla/Gardening#Task:_Cleaning-out_NEEDINFO). Thus I prefer to believe that the comment 6 is valid, and thet your opinion is based on the obsolete state diagram of Bugzilla bugs (https://wiki.documentfoundation.org/File:BzLifecycleold.png) still referred in the up-to-date description of bug states (https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status). Cheers ;-)
Witold: it is not my opinion, it is a fact. If you willingly set a confirmed bug back to unconfirmed, you are taking the risk that no developer will ever look at it.
** 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 (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ 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) http://downloadarchive.documentfoundation.org/libreoffice/old/ 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
The proper way to define installer UI from command line is use ProductLanguage property [1]. It automatically selects the built-in language transform (or base en-US UI, if needed). > msiexec /i LibreOffice_X.Y.Z_Win_x64.msi ProductLanguage=1033 where 1033 is for en-US; the value is decimal LCID number [2]. Note that the [MS-LCID] document lists the IDs in hexadecimal, e.g. 0x0409 for en-US. [1] https://docs.microsoft.com/en-us/windows/desktop/Msi/productlanguage [2] https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c
Dear libreoffice, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
As explained in comment 2, there is no en-US transform in the installer (which is authored as en-US), and comment 17 describes the correct way to launch installer in *any* available language (including en-US and those that are available as transforms). Just tested that 'msiexec /i D:\Downloads\LibreOffice_7.1.1.2_Win_x64.msi TRANSFORMS=:1049' works fine with version 7.1.1.2; so that part of comment 1 (which was not the issue discussed in this report) is WORKSFORME. Closing this as NOTABUG.