Created attachment 146994 [details] which callout aren't working On some documents only, I'm not able to visualize the line between endpoint and callcout box. I've tried to modify properties (color, style, width, etc.) without success. 1. open the document 2. click on line callout (any of "line callout") 3. place de line callout : 2 yellow points are present to show where should be the line However, "callouts" icon works fine (see attached picture)
Created attachment 146995 [details] callout with yellow dot but no line
Created attachment 146996 [details] Writer document where I can't use callout (lines not visible)
I can reproduce the problem with your document in Version: 6.3.0.0.alpha0+ (x64) Build ID: 9e55c8c7ffc43004ca314edcd4712dcc29adf933 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: de-DE (en_US); UI-Language: en-US Calc: threaded I cannot produce the problem with a new document. It seems to be somehow connected to the TOC. If I delete the TOC, the leg of the callout is visible, if I insert the TOC again, the leg of the callout vanishes.
(In reply to Regina Henschel from comment #3) > I can reproduce the problem with your document in Version: 6.3.0.0.alpha0+ > (x64) > Build ID: 9e55c8c7ffc43004ca314edcd4712dcc29adf933 > CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; > Locale: de-DE (en_US); UI-Language: en-US > Calc: threaded > > I cannot produce the problem with a new document. > > It seems to be somehow connected to the TOC. If I delete the TOC, the leg of > the callout is visible, if I insert the TOC again, the leg of the callout > vanishes. What is the TOC ? could I delete it without datas lost ? thanks
TOC = Table of Contents Removing and newly inserting the table of content does not solve the problem for this document. I have tried that already. But because I could not reproduce the problem with a new document, it might help, if you make a new document and transfer the content from the old document into it. First load the styles from the old document, then copy and paste the content. If that does not solve the problem, try it without preserving the styles.
I can reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 3911bf8364dae4c855ad37237c114f9007f70657 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded I can't reproduce it on page 1, but I can on page 4
Not reproduced in Version: 4.4.0.0.alpha2+ Build ID: b21df5a993a3815cf736fe3d2eab73eee646b38e
bisected with bibisect-linux-64-6.1. Lots of crashes when place callout during bibisect, and it looks like crashes started with https://cgit.freedesktop.org/libreoffice/core/commit/?id=bf46b46a1d734348096936284fb8a76e977936d0 (14.3.2018) and crash is fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=2dadf90aa7bb03d895abc05ec93ca116eb9bacbd (20.3.2018) Before crash is callout correct and after crash is callout with bug.
I don't know if Mohammed Abdul Azeem is active but let's try with CC.
Dear roumanet, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I cannot reproduce with old LO, so you who can, please retest.
Actually, for some reason I couln't rpro with 6.0 but I could reproduce with 6.2.0 while not with 6.4.0 and 7.5+. So I close as WFM. Please retest.