Bug 136391

Summary: Writer does not save documents
Product: LibreOffice Reporter: Artem Korneev <artem.korneev>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED NOTABUG    
Severity: normal CC: buzea.bogdan
Priority: medium    
Version: 7.0.0.3 release   
Hardware: x86-64 (AMD64)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Save icon

Description Artem Korneev 2020-09-02 03:31:31 UTC
Created attachment 165001 [details]
Save icon

OS - MacOS Catalina 10.15.6 (19G2021)

Writer does not save the document in any ways - Cmd + S does not save it, File -> Save does not work, "Save as..." does not work, "Export" does not work. In all those cases I see a turning colored wheel for a few seconds, which means that the system is busy. But nothing happens after that. Both from hotkeys, from the system menu and from the window's own toolbar.

If I click "Export as PDF...", it shows the initial dialog with export settings, but once I click the "Export" button, it is all the same - turning colored wheel, system is busy for a few seconds, then nothing happens. The dialog window disappears.

UI keeps showing the "save" icon on a toolbar with red dot, which means document has unsaved changes - see the attached screenshot.
Comment 1 Artem Korneev 2020-09-02 03:37:08 UTC
If I close the document, it proposes to save it, but is not able to do that either. It is busy for a few seconds, but nothing happens. And it does not close the document (which is good, cause it failed to save it).
Comment 2 BogdanB 2020-09-02 19:35:41 UTC
Hi, have you tried Restart in Safe mode?
Help - Restart in Safe Mode - Restart - Factory Settings
Comment 3 Artem Korneev 2020-09-19 00:42:16 UTC
(In reply to BogdanB from comment #2)
> Hi, have you tried Restart in Safe mode?
> Help - Restart in Safe Mode - Restart - Factory Settings

Well.. Cannot reproduce anymore.
Somehow it got deleted from my laptop - I don't think I did it, but might be some corporate software did it. So, I downloaded it again today and this time I see that "save" works fine.

Maybe it was some corp-wide restrictions for the software from unknown sources. Cannot say for sure.

But it is not reproducible on my system anymore.
Comment 4 QA Administrators 2020-09-19 04:14:21 UTC Comment hidden (obsolete)