Description: Every few saves when working on a Draw document, the save process hangs LO and does not release for 5-10 minutes. After several minutes i can see the save progress bar start to move towards completion but it is so slow it is basicall frozen. In most cases the save completes within 10 minutes but sometimes I give up waiting and force quit the application, losing my work in the process. Steps to Reproduce: 1. Open or create a Draw document. Paste a bunch of text into a text box. 2. Press Crtl-S. 3. If the document saves as it should just repeat Ctrl-S and eventually LO will hang while it saves. Actual Results: Eventually LO freezes because it is locked in the Save process. It is random but on my machine it is repeatable every few saves. LO will remain frozen for 5-10 minutes. A few times I gave up waiting and force quit the application, losing my work in the process. Expected Results: The save process should complete almost instantly for these tiny documents.This happens with documents containing a single page so it is not because the files are huge or complex. They do not have any images in them. They only have 2-3 text boxes in them. Reproducible: Always User Profile Reset: Yes Additional Info: This problem occurred a few years ago with LO. It turned out then that it was an issue with the 6th Generation of Intel's i3 Core CPU. The fix then was to disable OpenGL, CL, and turn off antialiasing i.e. it was related to the graphics subsystem. This time these fixes didn't work. I reported this as a bug with Mesa too but one of the support guys helped me and mesa was unable to report any problems. I have reset my profile. I have gone into Advanced Configuration and disabled OpenGL. I have tried increasing the memory allocation for objects. No success. I have tried Fresh and Stable. I have tried appimages for multiple older versions and all of them hang on save eventually (versions after 6) I have also tried several different linux kernels. The same hang. Curiously, Writer 7.2 does not hang when saving. As far as I can tell this is related to Draw only. I'm not having any problems with Scribus or any other application. Could it be some change to the codebase for Draw's saving routine? I managed to find an appimage for LO 6.0.x and so far this one works correctly. This is the last version of LO before the new ribbon bar was introduced I think. I will keep testing but for now, LO Draw 7.2 is remains unusable.
Okay, after a lot of experimentation I have found a workaround to the FILESAVE HANG bug. It is associated with GTK3. Changing the theme from GTK3 to QT5, then logging out and back in fixes the problem. Saving is once again instantaneous the way it used to be under GTK2. /etc/profile.d/libreoffice-fresh.sh export SAL_USE_VCLPLUGIN=qt5 /etc/profile.d/libreoffice-fresh.csh setenv SAL_USE_VCLPLUGIN qt5 This also explains why multiple versions of Libreoffice are affected. The last usable version for me was 6.1.2.3 I'm not sure there is anything that LibreOffice developers can do about this. I hope this workaround helps someone in the future.
Sorry, 6.1.6.3 was the last usable version for me without changing the theme.
No repro with Version: 7.5.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7b23c53232245a1f61c3e8ddff59d049a49fe975 CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Please attach test file, thank you.
Dear David, 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
Dear David, 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-FollowUp