Description: Calc: Working on Charts of a huge table (35000 lines, 30 columns)cause a system hang up, especially when modifying the chart (never ending processor load of 100%). For example in Excel you get the message "calculating cell ..", so you know, why the system is slow. In LO you never know why. But often thoses processes don't even end after an hour or more. So i got to restart LO. Things are so delicate, that i don't dare to make changes. So i get back to Excel. My System: Mint 18.3 Sylvia with KFCE; LO 5.1.6.2 Beim Arbeiten in einer Grafik über einen grossen Tabellenbereich kann es passieren, dass sich das Programm "aufhängt" bzw man kann nicht erkennen, welcher Prozess kein Ende findet (Prozessorauslastung 100%). In Excel wird zB angezeigt "wird berechnet". Dann weiss man wenigstens, warum nichts weiter geht. Die Sache ist so heikel, dass ich mich nicht mehr traue, Änderungen einzugeben. Mein System: Mint 18.3 Sylvia mit KFCE; LO 5.1.6.2 Actual Results: It is not possible to change the related column in a chart. Almost any change in an existing Chart over 35000 cells leads to a crash. Only deleting the chart and starting a new one leads further. If you want, i can send you the table. Expected Results: In big data the programm should suck in the related data like a biological cell does with a dna. It should not start working before ending to type the command. There should be a key to stop the execution when you notice a mistake and fall back to the state before. Reproducible: Always User Profile Reset: No Additional Info: It is a pitty, that you have to restart not only the hungup table, not only the programm (Calc), but the whole Libre Office. It is fine, that it is possible to resurrect all files, but when you have 25 files it's still an tiresome work. Isn't it possible at least to sepparate Calc from Writer or Impress?
5.X version are EOL, like 6.0.X, 6.1.X, 6.2.X, 6.3.X and soon 6.4.X Last stable LO version 6.4.7 but you can also try brand new 7.0.3 You can also try LO from PPA (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). Since according to https://en.wikipedia.org/wiki/Linux_Mint_version_history, Mint 18.3 Sylvia is based on Ubuntu 16.04 (Xenial Xerus), you must choose LO package accordingly. Anyway, the simplest would be to upgrade Mint to 20 (Ulyana).
Dear Doaro, 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 Doaro, 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