Bug 77435 - install libreoffice via GPO at machine level, errors about 64 bit reg key field
Summary: install libreoffice via GPO at machine level, errors about 64 bit reg key field
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.2.2.1 release
Hardware: x86 (IA32) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-14 13:25 UTC by sotiraw
Modified: 2015-09-04 03:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sotiraw 2014-04-14 13:25:28 UTC
i try to install libreoffice via gpo. i do all described at bug45750 descussion. i do remove all unwanted languages , so i dont get validation errors from them.

BUT one error remains. it refers to a 64bit value that doesnt show to a 64 install location, but to a 32 bit as the error says. since this is the only error remaining i think this is what is that gives the fail error to group policy deployment. 

how can i fix this? or has anyone managed to deploy new versions of libre office via gpo?

ICE80 Error This 64BitComponent registry_g_m_o_winexplorerext_x64_libreoffice42 uses 32BitDirectory INSTALLLOCATION	ice80.html	Component	Directory_	registry_g_m_o_winexplorerext_x64_libreoffice42	C:\Program Files\Orca\darice.cub

ICE80 ErrorThis package contains 64 bit component'registry_g_m_o_winexplorerext_x64_libreoffice42' but the Template Summary Property does not contain Intel64 or x64.	registry_g_m_o_winexplorerext_x64_libreoffice42	C:\Program Files\Orca\darice.cub

it shows as 2 errors but actually it refers to one
Comment 1 Robinson Tryon (qubit) 2015-01-15 00:18:29 UTC
(In reply to sotiraw from comment #0)
> i try to install libreoffice via gpo. i do all described at bug45750
> descussion. i do remove all unwanted languages , so i dont get validation
> errors from them.

Hi sotiraw,
Are you still experiencing problems with builds from the 4.3 branch?

Status -> NEEDINFO

(please change status -> UNCONFIRMED after you reply. Thanks!)
Comment 2 QA Administrators 2015-07-18 17:35:13 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-07-18
Comment 3 QA Administrators 2015-09-04 03:00:30 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-09-03