1. UAC has been turned OFF since a week before I installed this program. 2. I am signed in as an administrator AND am the sole user of this computer. 3. I've manually gone through every single file in the LibreOffice 3.5 directory, its storage directory at c:\ProgramData\Microsoft\Windows\Start Menu\Program\LibreOffice 3.5 and for all .exe files, I've changed their status to "Privilege Level: Run this program as an Administrator." under the Compatibility Tab AND the "Change settings for all users." (where I'm not locked out as "not having the appropriate permissions to access the item." that is.) 4. Despite all this, (& partially why) my attempts to run app as "an administrator" fail because right-clicking the run menu shows neither the option to "Run as administrator" or my "Take Ownership" adaptation. 5. I've also installed this app in both the "Program Files" and "Program Finles (x86)," and when error messages told me I didn't have the "appropriate permissions" to access either "system file," I created my own folder and tried again -- I failed again. During installation, I see no error messages and everything seems fine. The problem occurs when I try to run any part of the program. All Event Log listings from MSInstaller say the installation succeeded. But what good is that when every time I tried to run the app, Windows spits out the message: Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. Since this problem has been going on in my computer since I bought it in the middle of April, the problem is Administrative Rights/UAC settings within Win7, NOT LibreOffice. Between April 16 and July 9, I've sent the computer in for repairs (they replace the hard drive as defective) and since I got the computer back on June 2, I've had three such major computer meltdowns that I was forced to reinstall my operating system back to factory specs THREE times (not counting the reinstallation done after the hard drive replacement). The last time was a week ago and I'm already beginning to think I have to do it again. The most common flaw is the above message. I've been blocked from my programs, my hardware AND my data. Media Center has deleted recordings on its own.
Not reproduced in my numerous libo version. Could you check this : http://support.microsoft.com/kb/2669244/en-us Let us know if you have again this problem. Yves
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
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