Problem description: When attempting to insert a formula, sometimes the following happens: 1) The first time I click "Insert" there are a lot of grayed-out menu entries, including "Object". I click somewhere else to leave because I cannot select "Object". 2) The second time I click "Insert", "Object" is selectable, but the entries inside "Object" are all grayed-out. I click somehwere else again. 3) The third time I click "Insert", I can select "Object"->"Formula" properly. Current behavior: I cannot insert formula without visiting "Insert" thrice. Expected behavior: This is not just for formulas, but other entries under "Insert" should not be grayed out in the first place. More info: I insert formulas within text or inside the fn-F3 generated boxes. It is unclear to me exactly when this happens, but it occurs very very frequently as part of my normal work-flow. My documents generally contain text and formulas, occasionally a few figures as well. While writing text and I try to insert a formula, sometimes this happens but other times not (mostly it does unfortunately). I know this is not enough to go on, but I was hoping someone has more information or pointers that can shed more light. Operating System: Ubuntu Version: 4.2.0.4 release
This has been around since earlier version of libreoffice, so its not a recent regression.
Hi Alexander, thanks for reporting. I have never seen this issue neither windows or Linux. Please try resetting the user profile, sometimes solves strange issues. https://wiki.documentfoundation.org/UserProfile
Just performed a reset and the same thing still occurs. I am currently in the process of writing a lot of text (dissertation) so I can keep testing this - I get it quite frequently even though I cannot pinpoint the cause through observation. Additional info: I found a way to reproduce this fairly consistently. While in formula-editing if I exit formula-editing and afterwards quickly click somewhere in the text and hit Insert, I get grayed-out entries. Furthermore, it looks like these are the same grayed-out entries which appear in the Insert menu if a formula is selected (if a formula is selected then this is the expected behavior).
I got suspicious and tried to work under LXDE (Lubuntu). It seems that this bug does NOT occur there. My previous report was for Ubuntu with Unity. I suspect that the problem is with the Unity integration. As such, I am not sure if this is the right bugzilla.
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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Currently on LibO 4.2.6.3 under ubuntu 14.04 (with unity) and the issue is the same. Note again that this still does not occur under LXDE, so I would guess it has something to do with the LibO-unity interaction.
I have sometimes the same problem with LibreOffice under Unity when I click on a menu, several entry are greyed out. Generally it's enough to open the next menu and go back to the desired menu to get all available entries. That said, I do not have a clear scenario to reproduce the problem, it seems to depends on the machine activity. I just created a new clean Unity session on my PC, will see if I still reproduce the problem in a session without residues from gnome (various species), xfce and old parameters from bugged Unity (since Ubuntu 11.10). Best regards. JBF
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Still an issue in 5.0.2 under Ubuntu 14.04 64-bit (with Unity).
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Never seen this issue with LO ≥ 5.1 under Ubuntu / Unity with GTK3 backend. Closing as WorksForMe. Please, feel free to reopen if you disagree. Best regards. JBF
Just got around to retesting this. It appears to no longer be an issue :).