https://bugs.documentfoundation.org/show_bug.cgi?id=170648
--- Comment #3 from Buovjaga <[email protected]> --- If you previously ran 25.8 without the saving issue, you might find out the exact cause by using a technique called binary bisecting: https://wiki.documentfoundation.org/QA/Bibisect https://wiki.documentfoundation.org/QA/Bibisect/Windows https://bibisect.libreoffice.org/win64-26.2-2022 I assume you don't have the newer Powershell 7 installed. 1. Open Powershell 5 2. Give this command to install the latest Powershell: winget install --id Microsoft.PowerShell --source winget 3. Give this command to install git: winget install -e --id Git.Git 4. Close the old Powershell window and use Windows Start Menu to launch Powershell 7 5. Go to some directory, could be the root of C: drive itself, so `cd C:\` and clone the 26.2 bibisect repository with: git clone https://bibisect.libreoffice.org/win64-26.2-2022.git 6. After the clone has finished, say cd win64-26.2-2022 7. Now say git tag oldest cc9574aa24614d168ead5ace2fcc96267347279f 8. Now give these chained commands and test the saving : git checkout oldest && instdir\program\soffice 9. If saving works, you should be able to bibisect the issue. Next use this and hopefully it *will* exhibit the saving issue: git checkout master && instdir\program\soffice 10. Next start the bibisecting with: git bisect start master oldest && instdir\program\soffice 11. Whenever you can save, say: git bisect good && instdir\program\soffice 12. Whenever you can't save, say: git bisect bad && instdir\program\soffice 13. When the process is finished after something like 13 steps, it will display the first bad commit. Select with the mouse and copy all the lines in this final output (you can copy by right-clicking, it gets put into the clipboard immediately) and paste here to a comment for us to inspect. -- You are receiving this mail because: You are the assignee for the bug.
