https://bugs.documentfoundation.org/show_bug.cgi?id=164771
--- Comment #14 from DenisMtz <[email protected]> --- Hello Team, In reply to comment #13 : Since 3 days, 100% of LO file recording attempts are failed: what ever is among [ 'save' or 'save as' or 'save a copy' ] When saving an LO Draw file (New or Pre-existing) , 100% results are now always the same ERROR : "The file could not be written". The issue began with LO 24.8.3 . (the Update to 24.8.4 was an attempt to fix the issue (but finally not, as same behavior). As well as, refresh/check the MacOS System release with Apple process. When the issue came, the .odg files were initially stored onto Apple iCloud drive, which capacity is half full only. Since the issue came, I copied the files onto the Local drive. (= same save behavior & same error). Local Disc not full since : 313 GB used out of 500 GB . Not sure to understand 'accessibility thing' ? Anyway : No new Apps installed since ages onto this MAC computer. NO one game. No new font. This MAC was my PRO engine, and remain it for the new association Project, I am involved with. As of today : No other "weird" bug seen detected with this Mac ? Only Apps that I use on this MAC are : Thunderbird Mail, WhatsApp Messaging, Firefox and Google Chrome Browsers, 'Apercu' is Apple Pdf file reader, Microsoft OneNote (is a personal Note Grabber) ... and intensive LibreOffice work (Draw, Calc, Writer). About storage, I use : — Apple iCloud as local storage extension , — Google Drive related the Groupware Project team using GoogleDocs & shared storage. — Microsoft OneDrive as repository for Microsoft OneNote. — Western Digital local Nas Storage for Local Archives. — External USB direct attached local disk for TimeMachine local Backup Please note : A clean Libreoffice UN-Installation process (back to bare-metal state) onto the MAC would nicely help ( meanning purging profile and all system lib, or dependent hidden files affected included, if any). Thx in advance. -- You are receiving this mail because: You are the assignee for the bug.
