Bug 74281 - Access control blocking installation
Summary: Access control blocking installation
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-31 14:45 UTC by computerfella
Modified: 2015-09-04 03:00 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screen shot (10.18 KB, image/gif)
2014-01-31 14:45 UTC, computerfella
Details

Note You need to log in before you can comment on or make changes to this bug.
Description computerfella 2014-01-31 14:45:14 UTC
Created attachment 93143 [details]
Screen shot

Instalation stop with following error messages:

"OpenWithProgids cannot be opened. An error is preventing this key from being opened. Details: Access is denied"

"Error 140-4. Couldnot open key: HKEY_LOCAL_MACHINE32\Software\Classes\.tga\OpenWithProgsIDs. Veryify that you have sufficient access to that key, or contact your support personnel.

I'm running Win 8.1, 8mb Ram, Dell. I was able to install 4.1 just fine.
Comment 1 Julien Nabet 2014-02-01 14:17:33 UTC
Jesus: one for you?
Comment 2 Robinson Tryon (qubit) 2014-12-22 07:04:26 UTC
(In reply to computerfella from comment #0)
> Instalation stop with following error messages:
> 
> "OpenWithProgids cannot be opened. An error is preventing this key from
> being opened. Details: Access is denied"
> 
> "Error 140-4. Couldnot open key:
> HKEY_LOCAL_MACHINE32\Software\Classes\.tga\OpenWithProgsIDs. Veryify that
> you have sufficient access to that key, or contact your support personnel.
> 
> I'm running Win 8.1, 8mb Ram, Dell. I was able to install 4.1 just fine.

Hi fella,

Are you still having an issue with LibreOffice? Have you tried one of our current 4.3 releases or 4.4 release candidates?
https://www.libreoffice.org/download/

What kind of access control lockdown is in place on these machines?

Status -> NEEDINFO

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