Wrong! Word Processor program freezes up for almost a minute when you try to save your work. It seems to have no way to over ride this problem. Older program worked perfect!
Yes, noticing the same. Getting around it for now by saving in fodt format. The problem seemed to start for me after copying and pasting some text into a document from a Facebook note I was working on.
changed platform to 'all' as I'm on x86 (and couldn't seem to do a multi-select for platform).
Marking as 'NEW' as it was confirmed by comment 1. Also changing priority according to https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg, and summary to a more descriptive one.
I too have the same problem since I work with Winodws8. Unchanged documents open en close fine. After editing the file saves fine, but Writer then freezes for about a minute and in the title bar it says 'writer is not responding'. After that it takes longer to open the file too.
Can be related to a known bug in Explorer extension (see Bug 56007). Could anyone who is affected by this bug run again LibreOffice installation, choose 'Modify' and uncheck 'Windows Explorer extensions'. Does it solve the problem?
This report would appear to be a duplicate of bug 63877.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
If the original reporter or others can demonstrate that this bug is somehow different from the duplicate, please change status to REOPENED and provide the necessary details. Thanks. *** This bug has been marked as a duplicate of bug 63877 ***