Description: I open an odt document to edit. I have to leave my desk for 5-6 minutes. When back, cursor is not blinking, mouse & keyboard commands are not working. Steps to Reproduce: 1. Open an odt file to edit. 2. Edit some, and let it sit for some minutes 3. Check mouse & keyboard commands Actual Results: Writer is not responsive. I have to close Writer and start anew. Expected Results: Writer working as in 6.5.4.2 ;-) Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: OS: Windows 10 Pro V 2004 x64 German Fresh installation on new hardware
Happy Birthday masi https://birthday-wishes-hindi.website/birthday-wishes-for-masi-in-hindi/
I can confirm this behaviour. Running LO 7.0.0.3 x64 on Windows 10 with UK English edition. Editing a document in LO Writer. Document will appear to "freeze". No mouse or keyboard movement within document, even when typing. Only option is to save, close and re-open the document in order to continue. However, any text which has been typed will be present when re-opened. Situation often occurs when switching task to another window then back again. Perhaps the period of inactivity in LO Writer is the cause. Problem is very irritating, especially when not immediately detected. Issue only encountered recently after upgrading to Version 7.0
This UI freezing behavior happens to me too. I am often editing my most important ODTs in writer, and switch to another app like chrome to do something else for a few minutes. If i give focus to Libreoffice Writer again, the UI menu is still selectable most of the time, i just cant enter text into the window, scroll, or select headings in the page navigator. I'm using LO 7.0.2.2 Windows 10 (10.0.19041 Build 10941)
Dear w.sirges, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Just wanted to add that the freeze doesn't happen for me in the version I have now: Version: 7.4.1.2 (x64) / LibreOffice Community Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0 CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Thanks for checking!
Could you please retest if you have this problem anymore?
(In reply to BogdanB from comment #6) > Could you please retest if you have this problem anymore? Hi, the issue stopped occurring for me a few releases ago.
Okay, thanks for the reply. I'm glad this bug doesn't affect you anymore.