Description: When we try to open it, a "(" character appear in the left to corner, a CPU (of 8) is at 100%. I try to use the "mode sans echec" and deactivate openGL, etc but the problem is the same. Can'I send you this file! it's a model very important for my job and I'm bloked !! Steps to Reproduce: 1. try to open my file .odt 2. 3. Actual Results: impossible to open the file Expected Results: CPU go 100%, and file never open, I must kill processes ! Reproducible: Always User Profile Reset: No Additional Info: open my calc file for i can work on this....
Bonjour, La version 7.0.3.1 est plutôt ancienne. Quelle distribution Linux utilisez-vous et quelle est la version ? translation: 7.0.3.1 version is quite old. What's the distrib Linux and what's the version?
(In reply to Julien Nabet from comment #1) > Bonjour, > > La version 7.0.3.1 est plutôt ancienne. Quelle distribution Linux > utilisez-vous et quelle est la version ? > > translation: > 7.0.3.1 version is quite old. What's the distrib Linux and what's the > version? Linux Mint 20.1 Cinnamon Voulez-vous que je vous envoie le fichier problématique (modèle qui s'ouvre mais après plusieurs enregistrement fini par devenir in-ouvrable, et/ou le fichier issue de ce modèle et qui ne s'ouvre plus ?). Je peux si nécessaire mettre à jour manuellemnt LibreOffice mais là c"est la version proposé par les dépôt de la distribution linux que j'utilise ! Merci d'avance de votre aide. PS : je ne l'ai pas déposé sur le site car il contient des données confidentielle ! Solairement, Richard BARRAS
Je préfère qu'on ne m'envoie pas de données confidentielles. Il existe une procédure pour tenter de supprimer tout ce qui est confidentiel (cf https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission). Sinon voici ce que je ferais : - migration vers Mint 20.2, peut-être que la version LibreOffice incluse sera un peu plus récente - si ce n'est pas déjà le cas, des sauvegardes régulières du fichier qui s'ouvre bien - recopier le contenu du fichier dans un nouveau fichier ods (afin de travailler sur le format natif de LibreOffice Calc) si possible. Comme c'est pour le travail, je suppose que c'est le format Excel (xls ou xlsx) qui est requis et là la conversion ods vers xls/xlsx peut apporter son lot de surprises. En tout cas, sans un fichier "public" et une procédure qui permette de reproduire le problème à coup sûr, cela sera compliqué d'avancer.
Is this still a problem? If yes, please follow Julien's advice and provide a document, so we can look at it.
Dear Richard BARRAS, 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 Richard BARRAS, 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