Created attachment 113678 [details] Screenshot of frozen desktop. Hi, I have been writing a number of documents over the last week. Regardless of the document I have found when editing the various documents the whole platform freezes and becomes mostly unresponsive. This is repeatable on my environment. The specific activity is selecting a region of text using either: a) the mouse pointer b) the keyboard (shift + UP/DOWN arrow keys) then the application and all other windows become unresponsive. The keyboard is unresponsive (NumLock light) etc. The mouse clicks no-longer perform any actions in the Gnome3 desktop. However, there is one thing that does work. The mouse pointer. It can be moved around the screen but mouse clicks have no effect. As a test to check system activity I had terminal window open. Split to show platform metrics per second displayed using "dstat". The second pane showing "top" running. Both panes of the terminal stopped updating immediately. The only solution to get the system running again is to press the reboot button on the machine. I have attached a sample document. Also a picture of the screen at the point of freezing. The screenshot shows the terminal window on the left and Libre Writer on the right. I found a defect that is very similar. https://bugs.documentfoundation.org/show_bug.cgi?id=81503 Regards, Jeremy $ uname -a Linux xxxxx 3.18.6-100.fc20.x86_64 #1 SMP Fri Feb 6 22:55:01 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Platform: Fedora20
Created attachment 113680 [details] Sample document. Sample document that can cause the platform to freeze. Interestingly when creating this document initially it did not cause the freeze. The document contained random text. The platform freezing has been happening on documents that contain output from sql queries in postgresql. When I pasted one of the results of a sql query into the sample document and saved it. Then shortly afterwards a freeze occurred. It may be relevant. It may not.
I tried with Scientific Linux 7 64-bit that I happened to have as a VM. I could not reproduce with LibreOffice 4.3.5. Would you like to try with 4.3.x or even 4.4.x? You can install in parallel for your tests using these instructions: https://wiki.documentfoundation.org/Installing_in_parallel/Linux Set to NEEDINFO for now.
Hi, Yes I will try installing one of those. Thank you for the instructions. I've found this issue also affects my platform when using Libre Writer and selecting text in the document. (In reply to Beluga from comment #2) > I tried with Scientific Linux 7 64-bit that I happened to have as a VM. I > could not reproduce with LibreOffice 4.3.5. > > Would you like to try with 4.3.x or even 4.4.x? > You can install in parallel for your tests using these instructions: > https://wiki.documentfoundation.org/Installing_in_parallel/Linux > > Set to NEEDINFO for now.
(In reply to Beluga from comment #2) > I tried with Scientific Linux 7 64-bit that I happened to have as a VM. I > could not reproduce with LibreOffice 4.3.5. > > Would you like to try with 4.3.x or even 4.4.x? > You can install in parallel for your tests using these instructions: > https://wiki.documentfoundation.org/Installing_in_parallel/Linux > > Set to NEEDINFO for now. Installed 4.4.1.2 in parallel. Still experiencing platform crashes. Some more more background. The platform crashes when the application is open with a document and unused for some time. Typically I switch to a different application (terminal/browser) do some work. Then later come back to swriter to continue working on the open document. swriter gets focus, text is selected and then the platform becomes unresponsive. Leaving only the mouse pointer moving over the screen. But all other input (mouse button clicks, keyboard, remote ssh into machine) is ignored.
Thanks for testing. I'll change back to UNCONFIRMED.
I can not reproduce on my machine with the sample documents. aaron@IdeaPad-Y510P:~$ uname -a Linux IdeaPad-Y510P 3.19.0-14-generic #14-Ubuntu SMP Mon Apr 13 22:18:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Kubuntu 15.04 Beta 2.
It looks like this is an edge case specific to my desktop environment setup. I am not expecting this to get fixed as it cannot be reproduced easily. I won't be upset if this bug is closed as WONTFIX or something along those lines.
Hey, I know you were fine with closing this, but we don't like to close bugs that seem real :) What is your current status? Moved to a newer Fedora? Still freezing with LibreOffice 5.1? Might be worth a shot: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/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 MassPing-NeedInfo-Ping-20161010
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20161108