You need to have the local help installed. Turn on "Extended Tips" in Tools > Options > LibreOffice > General. Start a Draw document and insert a shape. Hover over an icon to make sure, that for icons the "Extended Tips" work. Then hover the menu line. No tooltip appear. Open a menu and rest on a menu item. No tooltip. Open context menu of the shape. There the same error, no tooltip on items or sublists. I see this error in Version: 4.2.2.1 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f and in Version: 4.3.0.0.alpha0+ Build ID: f839b5dd16c05c0eda21345ec36ec0cb024eb732, both on Windows 7. It has worked in version 4.1.
Hello Regina, *, I can confirm your issue: * with LO Version: 4.1.5.3 Build-ID: 1c1366bba2ba2b554cd2ca4d87c06da81c05d24 (with installed Germanophone lang- as well as helppack under Debian Testing) I have to click on a menu item and then moving around to see the Extended Help. * with LO Version: 4.2.3.3 Build-ID: 6c3586f855673fa6a1576797f575b31ac6fa0ba3 (parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel, also with installed Germanophone lang- as well as helppack) I can confirm your observation ... :( * with LO Version: 4.3.0.0.alpha0+ Build ID: 6d9d0393f54d6a20a5c5b11b038fb1cb9dcfe492 TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-04-09_06:28:03 (also parallel installed, but with en_US lang- as well as helppack) it is the same as with 4.2.3.3 ... :( HTH Thomas.
** 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 (4.4.3 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-06-08
I see the problem still in Version: 5.0.0.0.alpha1 Build ID: 77a35997fa7cff387b5b135ff0c42155f80e9884 Locale: de_DE
Is it possible to bibisect this issue, please?
Migrating Whiteboard tags to Keywords: (bibisectRequest) [NinjaEdit]
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I see the problem still in Version: 6.0.0.0.alpha1+ Build ID: d30522e46ca884e9bc74af21711d9537e8118859 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-10-29_23:13:14 Locale: de-DE (de_DE); Calc: group
I see the problem still in Version: 6.2.0.0.alpha1+ (x64) Build ID: f825e6d4082c0d0beb1c95b881f6a2ee9bfc9161 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-05_00:20:26 Locale: de-DE (en_US); Calc: CL
(In reply to Jan Holesovsky from comment #4) > Is it possible to bibisect this issue, please? Apparently not. The bibisect repos don't seem to include the offline help...
(In reply to Mihkel Tõnnov from comment #9) > (In reply to Jan Holesovsky from comment #4) > > Is it possible to bibisect this issue, please? > > Apparently not. The bibisect repos don't seem to include the offline help... I take that back. Using HELP_DEBUG=1 environment variable, I could at least see the placeholders, and see when they disappeared for the menus: 3e850c3ca58c147ee5913f9226fc383257fde14e is the first bad commit source-hash-d7fe5ab30ca9df722eec33d428baedd258075eac commit d7fe5ab30ca9df722eec33d428baedd258075eac Author: Noel Grandin <noel@peralex.com> AuthorDate: Thu Aug 1 11:23:58 2013 +0200 Commit: Noel Grandin <noel@peralex.com> CommitDate: Mon Aug 12 11:56:36 2013 +0200 convert vcl/menu.hxx from XubString to OUString (second attempt) Change-Id: I579525326be702ffbb57d49970da5804fd2fe12d https://gerrit.libreoffice.org/plugins/gitiles/core/+/d7fe5ab30ca9df722eec33d428baedd258075eac^!/ Not sure if that helps particularly much, though, considering how extended tips currently aren't shown for anything at all and some bigger changes are needed to fix that (bug 120538 / 118148).