Description: When double-clicking an existing LO office (Writer, Calc.... whatever), I frequently get the error message "Write Error. The file could not be written" (see the attached screenshot). I have to exit Quickstarter to fix it. It was already occurring in 7.6. It also happened that a new Writer document could not be saved, wit the same error message. I have lost all what I had typed. Occurs on at least three different PCs. Steps to Reproduce: 1. Make sure Quickstarter is on. 2. Double-click an existing document. Actual Results: Error message as in the attached screenshot Expected Results: Open the document. Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 6; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: en-GB Calc: threaded
Created attachment 192630 [details] Screenshot of the error message Here is what I get when double-clicking an existing document.
Do you by chance have some sort of TEMP directory cleanup procedure running on logon? Asking because, by chance, today I fixed tdf#159769, and it had exactly the same manifestation. If you have quickstarter opening automatically at logon, then it would be a matter of chance if it starts first, or the cleanup procedure runs. If the cleanup happens *after* quickstarter already started (and created its temporary directory), then the problem will happen. Either a custom batch file (put to autostart) could do the cleanup, or a utility like registry cleaner, configured accordingly.
(In reply to Mike Kaganski from comment #2) > Do you by chance have some sort of TEMP directory cleanup procedure running > on logon? Asking because, by chance, today I fixed tdf#159769, and it had > exactly the same manifestation. If you have quickstarter opening > automatically at logon, then it would be a matter of chance if it starts > first, or the cleanup procedure runs. If the cleanup happens *after* > quickstarter already started (and created its temporary directory), then the > problem will happen. > > Either a custom batch file (put to autostart) could do the cleanup, or a > utility like registry cleaner, configured accordingly. No, I do not have have a cleanup procedure runninng on logon. I do sometimes manually run ccleaner at the beginning of a session, but not every-time. This is always after all the startup program are launched, including the LO quickstarter. The bug occurs very frequently and on different PCs. I'll keep an eye on whether there is any correlation between running ccleaner and the problem reported.
A couple of potentially related reports: - bug 157547 - bug 158507 Let us know how you go with the ccleaner theory. Thank you!