Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi :)
Just to settle your mind a bit by reducing some of the variables.  None of
this means that there is no problem.  Clearly there is, but Stuart is one
of the top stars on this mailing list.  Everyone here is amazing imo, but
some people such as Stuart take it up a few notches.

In Windows the "Admin User", as with the "Super User" in Gnu&Linux, should
be able to read/write everywhere.  Installing programs as
AdminUser/SuperUser is normally the only way to install things - whether by
elevating a normal user (in Gnu&Linux sudo, as in "do as SuperUser") or by
directly logging in as an AdminUser/SuperUser (Gnu&Linux has a default one
called "Root"), both ways should produce almost identical results.

Having installed a program as Admin/SuperUser the program 'should' then be
run by normal users.  Clearly this is where the problem is showing up in
this particular case.  However the problem may have occured during the
install process.  Clearly it's not running the way it normally does, ie the
way it 'should'.

Renaming the User Profile fixes many weird things that shouldn't be going
wrong and a reinstall/upgrade 'should' go smoothly.  So it's definitely a
good thing to try early on.
Regards from
Tom :)


On Tuesday, 26 January 2016, V Stuart Foote <VStuart.Foote@utsa.edu> wrote:

Andy,

Have you cleared your user profile and allowed it to rebuild?

https://wiki.documentfoundation.org/UserProfile

That really is the first step.

Otherwise, seems like a problem with the registered temp folder.

Here is a clip of a correctly configured Tools -> Options -> Paths panel
for
LO 5.1.0 (would be same on Vista, 7, 8, 8.1 and 10).

<
http://nabble.documentfoundation.org/file/n4173085/LO_ToolsOptionsPaths_Windows7-10.png


If clearing your user profile does not resolve--Next step is to do a
complete uninstallation, and clean install.

1. Remove (or rename)  all of the LO User profile's, e.g.
C:\Users\<usernames>\AppData\Roaming\LibreOffice
2. Login as an administrator's group member, and  uninstall LibreOffice.
3. Clean the Windows registry:
   HKEY_LOCAL_MACHINE\SOFTWARE\The Document Foundation
   HKEY_CURRENT_USER\SOFTWARE\The Document Foundation  (for all users)
4. launch a command prompt, change directory to your download, and with CLI
issue command "msiexec.exe /i LibreOffice_4.4.7.2_Win_x86.msi /L*v
installLog.txt"  This will log the installation should there still be
issues.
5. Log out and back in as your user. Launch LibreOffice to check  if that
resolved the path issues.

Stuart




--
View this message in context:
http://nabble.documentfoundation.org/Help-Lost-all-file-permissions-after-upgrading-Libre-Office-in-Win-7-tp4173055p4173085.html
Sent from the Users mailing list archive at Nabble.com.

--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
<javascript:;>
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.