Description: Some hours after installation, LO freezes PC Linux (except the mouse) on every search of a word. Some time I have no time to enter the complete word.It is not related to the text or the word. Happens also on Calc. The only solution except waiting and hope is to cancel the graphic manager. glances mentions a high context sw (58kB) Same problem on LBO 7.0 BUT NOT WITH 6.4.7 reinstalled to work. In glances (top) : the process marco --composite --replace is at 100% The problem doesn't exist with metacity en Compiz. So the window manager marco (WM) doesn't work with version 7.X. marco : version 1.22.3-2-mint1+tricia Libreoffice 7.1.3.2 Community (LinuxMint 19.3 64bit / Linux 4.15.0-143-generic) MATE 1.22.2 memory 8GB Intel® Core™ i5-8400 CPU @ 2.80GHz × 6 Steps to Reproduce: 1. Have a PC Linux with marco 1.22 2. Open a text (.odt) or new text 3. search a word Actual Results: Very slow the first time, more and more time, then freeze Expected Results: PC freeze (graphical layer) Reproducible: Always User Profile Reset: Yes Additional Info: No problem on Linux Mint 19.3 with metacity or Compiz.
are you sure it's a LibreOffice's bug? So, please write here info from LO's Help-About dialog
(In reply to Roman Kuznetsov from comment #1) > are you sure it's a LibreOffice's bug? > > So, please write here info from LO's Help-About dialog It is not my problem. THe problem is that LO 7.X is not usable with marco 1.22. All other software are ok.
OK. I know the the problem could be out of LO version 7 but in my opinion, a software like it must run on every supported OS. I want only to know where is the problem and how to run 7.X on Linux Mint without usign Compiz.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to sergetome from comment #2) > (In reply to Roman Kuznetsov from comment #1) > > are you sure it's a LibreOffice's bug? > > > > So, please write here info from LO's Help-About dialog > > It is not my problem. THe problem is that LO 7.X is not usable with marco > 1.22. All other software are ok. Version: 7.1.3.2 / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 6; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: fr-BE (fr_BE.UTF-8); UI: fr-FR Calc: threaded
Do you still reproduce it with MATE version 1.26 and LibreOffice 7.3? If it still happens, you could also report it to marco: https://github.com/mate-desktop/marco/issues
Dear sergetome, 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 sergetome, 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