Description: Installation of LibreOffice version 6.2.7 recognize the installation path on my Windows 10 Laptop. The version 6.3.1 does not. If I change the installation path by hand and click on next, the installation process frozes. Steps to Reproduce: 1.Start installation process 2.Change the installation path 3.The software is going to frozen Actual Results: I have to cancel the installation process Expected Results: Go on further with installation process Reproducible: Always User Profile Reset: No Additional Info:
Not mixing 32-bit and 64-bit builds?
No, no mix of different versions, please take a look to the screenvideo I made for you https://www.screencast.com/t/ioODlLTL
OK, so obvious question... Is your existing installation on the D: drive you are setting the custom installation path to? Going to assume so. Unfortunately to see what is happening with the packaging will need you to prepare a verbose installation log, running the install from the command line. Entered as follows: --Open a command window, or powershell (run as administrator) --type the command "msiexec.exe -i LibreOffice_6.3.1_Win_x64.msi /L*v lo631Log.txt" --process with the custom install --when install completes or aborts, ZIP the log file --post as attachment we should be able to see what is misconfigured.
Hi, Cannot record/log the issue with your command. After entering your "msiexec.exe -i LibreOffice_6.3.1_Win_x64.msi /L*v" in the cmd (as an admin) a pop-up opens, see https://www.screencast.com/t/aIB7vR9zAii. I click OK but nothing happens. Open "msiexec.exe -i LibreOffice_6.3.1_Win_x64.msi" file again from "D:\Downloads" where my installation file is located. Cannot find any log file as "lo631Log.txt" in my C:\WINDOWS\system32\" What's wrong please? Regards, Thorsten
(In reply to Thorsten from comment #4) > What's wrong please? > Sorry, should have mentioned that the CLI syntax needs to include the directory (either full path, or relative). Can use fulll pat,h but easiest to change directory to the folder holding the downloaded MSI package. So with a command window or PS open, issue: -- "d:" (to change the shells current drive) -- "cd \downloads" (to change the shells current directory) -- "msiexec.exe -i LibreOffice_6.3.1_Win_x64.msi /L*v lo631Log.txt" The lo631Log.txt named file will be created there in the current shell directory, and be available to Windows Explorer file manager.
Created attachment 154368 [details] Log file requested if installation fails.
@Thorsten, that log was partial with only 6,391 lines--you should get something more like 190,000 lines and ~50 MB in size (why you'll need to ZIP before attaching). But what was there does show the entry of the D:\Program Files\LibreOffice install folder.
Hi, Thank you for your response but this is the result. I made a second screen video for, see https://www.screencast.com/t/PYymQBhZ The file I sent you does not have more lines. I'm going to send you the second result. With the previous version and the versions before, I did not have any issues, only with the latest one. Maybe I can install in standard directory on disk c:\ but I do not want to do this. Something is wrong with the latest installation process. Cheers, Thorsten
Created attachment 154371 [details] Second log file you requested Unfortunately the second try has a file similar to the first try.
[Automated Action] NeedInfo-To-Unconfirmed
So, on my daily driver desktop, I uninstalled LO 6.3 and installed a seat of 6.2.7.1 as a Custom install to a D:\Program Files\LibreOffice directory. I then performed an upgrade custom install to 6.3.1.2 over that. And then performed an upgrade custom install of 6.3.2.2 over that. Verbose logging of all the installs. As OP has been unable to provide verbose logging, and custom install to alternate disk drives is proven to work correctly going to close this issue. For OP, not clear why you are unable either to install to the D:\ location you select in a custom install, nor why your verbose logging is aborting. Could be a physical issue with your D:\ drive, unwritable sector(s) -- probably should test the drive. Also, a good idea to validate the copy of the 6.3.1 installer you'd downloaded--check its MD5 or SHA256 Hash value matches what the project has posted. But, you might move on to the 6.3.2.2 release (again check its HASH). If the installer(s) and the HDD have no issues and you continue to error out of install to your D:\, we can't do anything without the verbose log of a command line installation as above. => WFM
I also tested with a virtual machine, with a deliberately small disk (200MB) to test "not enough space" scenario; and also selecting a read-only disk (CD-ROM) as destination, and could not reproduce the issue.
Hi, Thank you for your response. I tested my SSD drive C + D, both without any errors or faults. I opened LibreOffice version 6.2.7.1 without any issues. I checked your software under "Help" if there is a new version. Now your software says, that my version is up to date. That`s interesting if your software tests were successful as mentioned above. I am going to check within the next days if a new version will be available and maybe you have news for me. Best regards, Thorsten PS: I will attach my screenshots of version request
Created attachment 154413 [details] Request of ne version As mentioned i my previous Email
(In reply to Thorsten from comment #14) > Created attachment 154413 [details] > Request of ne version > > As mentioned i my previous Email Nothing out of normal there, the 'Check for updates...' dialog posts a query to a static page of build signatures [1]. Changes to the listed builds, and notifications that new builds are available, are staged with the release cycle by our release engineer(s). In the next month or so, the 6.2.7.2 should recognize when 6.3.2.2 is available--the 6.3.1.2 build would not yet be orrered. =-ref-= [1] https://cgit.freedesktop.org/libreoffice/website/tree/check.php?h=update
s/not yet be orrered/not yet be offered for download