Description: Installer kept hanging if a custom install to go to the d: drive is selected. After a few attempts & a reboot, I gave up and let it install to the primary (c:) drive which went as normal. It did remove most of the files from the previous installation to the d: drive as part of this. Steps to Reproduce: 1. Run the installer 2. Select custom install 3. Change the installation folder to the d: drive Actual Results: Hang! Expected Results: Should install to selected drive like previous version. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36
Was the installer located in the D: drive when you launched it? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
I had downloaded the installer file at work so was running from a USB flash drive (l: to be exact)
What is the D: drive? Is it on your physical hard drive?
(In reply to Buovjaga from comment #3) > What is the D: drive? Is it on your physical hard drive? It's a physical hard drive but not the o/s drive which is c: The install went as normal once I let it install on the c: drive.
*** Bug 112895 has been marked as a duplicate of this bug. ***
Issue confirmed from French users mailing list: http://document-foundation-mail-archive.969070.n3.nabble.com/mettre-sur-disque-D-tp4241910.html Set status to NEW. Best regards. JBF
Dear John Kissane, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
Dear John Kissane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to Xisco Faulí from comment #7) > Dear John Kissane, > Could you please try to reproduce it with the latest version of LibreOffice > from https://www.libreoffice.org/download/libreoffice-fresh/ ? Apologies I no longer have a PC with a 2nd hard drive so cannot try to reproduce it.
Dear John Kissane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I wasn't able to reproduce with the 7.4.3.2 64bit MSI, installing on a USB drive (D:). Is Paul still able to reproduce?
Jean-Baptiste's link to the French mailing list doesn't work anymore, here is a working one: https://www.mail-archive.com/users@fr.libreoffice.org/msg40909.html The issue was reported in 2018 for LO 5.4, Windows 10. The reporter says the installer tries to install to the C drive anyway. Paul replied via email and said he wasn't able to test because of different hardware. Duplicate bug 112895 could be a false-positive related to the unpacking of the installer on a nearly-full C drive. Tempted to close as "works for me" because no one has reproduced since 2018 and LO 5.4.
So - is this reproducible? The NEEDINFO status will auto-close the bug, if no data provided.