| Summary: | "Write Error. The file could not be written" | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Massimo <pincopallino> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEEDINFO --- | ||
| Severity: | normal | CC: | pincopallino, stephane.guillou |
| Priority: | medium | ||
| Version: | 24.2.0.3 release | ||
| Hardware: | All | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | Screenshot of the error message | ||
|
Description
Massimo
2024-02-19 10:09:38 UTC
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! |