| Summary: | "Could not create system" fatal error on FILESAVE | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | David Clayton <dcclayton> |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | VERIFIED NOTABUG | ||
| Severity: | normal | CC: | jmadero.dev |
| Priority: | medium | ||
| Version: | 5.1.6.2 release | ||
| Hardware: | x86 (IA32) | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | Shows fatal error message. | ||
We need a lot more information - and to be quite honest this seems like an enterprise type issue which (if you want the problem fixed on your time, vs. waiting for a volunteer to fix it whenever they want to) I'd suggest considering support. Please describe your network setup more - what computers as host/client, what type of server setup is it? Also can you please try with a fresh profile just to be sure that it's reproducible: https://wiki.documentfoundation.org/UserProfile This is going to be very hard for anyone to triage because it's such a particular setup. Set to UNCONFIRMED once you've answered the questions and reset your profile. Thanks Hi Joel, Thank you for your reply. Apologies I haven't been back and updated the report. I have installed 5.0.3.1 and haven't noticed the fault since. I don't know if it was fixed directly, or if there was an error in the local installation. David. Hi, I have the same problem with the same condition, upgrade LibreOffie to the 5.1.6 change nothing (but no problem on Linux version). The problem was on a specific file, after recreate it bye migrate pages to a other file, it's works fine. Regards |
Created attachment 119301 [details] Shows fatal error message. When working with sheet, either the background auto-save, or manually clicking the save button will result in the error message attached, or Libre Office crashing / becoming completely unresponsive. The file is located on a network share. The PC has Cisco Fire AMP cloud based anti virus (which does scan the file on save). AV log shows soffice.bin creating a file on the local machine, user data, roaming, backup. diagnosis could be aided by either trying a local save, and or turning off the AV. I believe that this was not an issue with the 4.x version, and therefore has been noticed since version 5. Could there have been a change that would conflict with the AV not scanning the file in a timely manor?