I have the latest version of LibreOffice but every time I go to save something, it erases most of what I have typed on the page. I've never had this problem before so it is getting a bit frustrating. Everything is on the page when I save it but if I close it and then open it again, it is all gone. I'm tired of having to type the same things out over and over again until it finally saves what I am trying to type(usually, three to four times). Any help would be great!
When there are unsaved changes in the document, the Save icon in the toolbar has an additional indicator. When you try to close a document with unsaved changes, you get prompted about this. What are your observations regarding these? Are you saving to a local drive or a network drive? Also, which application are you seeing this specifically? Writer? Calc? Impress? Others? All of them? Please copy and paste here the content of your Help - About by clicking the copy button. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Yes, I know about the save icon indicator, I've been using this program for a long time. I even hit the save button a couple times just to make sure it is saving before I close it but when I open it again it still has not been saved. Everything saves to my local drive. It happens in writer. Version: 26.2.0.3 (X86_64) Build ID: 620(Build:3) CPU threads: 8; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded
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.
git : The term 'git' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + git clone https://bibisect.libreoffice.org/win64-26.2-2022.git + ~~~ + CategoryInfo : ObjectNotFound: (git:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException