Created attachment 121277 [details] File to save and reopen and original ODG Greetings from Russia, comrads! My version is: Версия: 5.0.3.2 ID сборки: 1:5.0.3~rc2-0ubuntu1~precise2 Also affected 4.4 The versions above are affected on Linux Ubuntu 12.04 LTS. Moreover, a version of OpenOffice runned on Win10 is affected, too. To reproduce the bug: 1) Open the attached file bug_for_LO_orig.odt Arrows go from 1 to 2 and from 2 to 3, don't they? 2) Click on the drawing. 3) Click the "Pegging" ("Привязка") icon (drawed as anchor) 4) Choose "As a symbol" ("Как символ") option (the last in list) 5) Save the document 6) Close the document 7) Re-open the document (for example, from File - Recent) 8) Arrows are incorrect, aren't they? 1 to 2, 2 to 1, 3 is disconnected. I've noted that size of file before is less than size of the file after. Excuse for my English - I am Russian and have no English-interfaced version of LibreOffice (so I need to guess for appropriate English names). This example was made on OpenOffice on Win10 by my bear who had drinken some vodka. I don't know what she did but when making MWE (minimal working example) I've noticed that there were some groups one inside another. Maybe she drawed arrows to grouped items. The ODG with MWE is attached. When I deleted arrows in Draw and drawed new ones, the bug disappeared. Should I give any additional information? The text below is in Russian. Доброго времени суток, товарищи! Текст выше - вольный пересказ нижеследующего на английском. Затронутые версии (фиг тут найдёшь, как две указать): а) Версия: 5.0.3.2 ID сборки: 1:5.0.3~rc2-0ubuntu1~precise2 б) Также задета 4.4 (точнее не скажу, в надежде на фикс обновил) - эти две на Ubuntu 12.04 LTS Известно, что аналогичная проблема имеет место быть на каком-то OpenOffice (кажется, четвёртой ветки) на винде-десятке (не к ночи будь помянута). Собственно, подшефная девушка на ней и делала, а мне прислала с просьбой сказать, что она делает не так. Файл с минимальной блок-схемой прилагаю. Конечно, изначально она была больше, но я отгрыз глючащее место. Чтобы воспроизвести баг в домашних условиях, надо сделать следующее: 1) Открыть прикреплённый файл bug_for_LO_orig.odt Стрелки идут по-человечески, от 1 к 2, от 2 к 3. 2) Щёлкаем по схеме 3,4) ПКМ - "Привязка" - "Как символ" 5,6,7) Сохранить - открыть - закрыть 8) Стрелка идёт от 2 к 1 кальдебобером Что девушка делала - неясно. Подозреваю, что группировала-разгруппировывала и рисовала стрелки в группе и вне группы. По крайне мере, в исходном файле группа на группе сидела и группой погоняла, но MWE вот. Когда я стрелки удалил и нарисовал по новой, то всё стало хорошо. Что-нибудь ещё прислать? Слава ГОСТ Р ИСО/МЭК 26300-2010 !
I don't know where to find the pegging symbol. You can change the interface to English from Tools - Options - Language settings - User interface. Then restart LibreOffice.
(In reply to Beluga from comment #1) > I don't know where to find the pegging symbol. > > You can change the interface to English from Tools - Options - Language > settings - User interface. Then restart LibreOffice. Thanks a lot! Right-click the drawing, Anchor - As Character. Спасибо большое! А то получается как в том анекдоте: "запах сильный, хотя мясо размякло".
Ok, thanks, I could repro. Opened bug_for_LO_orig.odt and changed the drawing anchoring to As character. The arrow from 2 to 3 switched to point from the bottom of 2 to 1. Win 7 Pro 64-bit, Version: 5.0.4.2 (x64) Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 Locale: fi-FI (fi_FI) Version: 5.2.0.0.alpha0+ Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44 Locale: fi-FI (fi_FI)
Created attachment 121433 [details] As earlier, change anchoring to character, save and reopen
Created attachment 121434 [details] Original ODG for second case
(In reply to Beluga from comment #3) > Ok, thanks, I could repro. > > Opened bug_for_LO_orig.odt and changed the drawing anchoring to As character. > The arrow from 2 to 3 switched to point from the bottom of 2 to 1. > > Win 7 Pro 64-bit, Version: 5.0.4.2 (x64) > Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78 > Locale: fi-FI (fi_FI) > > Version: 5.2.0.0.alpha0+ > Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969 > CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; > TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44 > Locale: fi-FI (fi_FI) Look, I've found related test case with only one rectangle and one arrow. Ti reproduce it: 1) Draw a rectangle in Draw 2) Draw an arrow connected to the rectangle with ony one end 3) Group them 4) Copy the group 5) Paste in empty Writer document 6) Change anchoring to character 7) Save and reopen 8) ??????? 9) PROFIT! Should I try to find even more test cases? It seems that I've had one in one of my documents. Я принёс ещё один файл с аналогичным глюком. Рубрика "сделай сам": 1) Нарисовать в Draw прямоугольник 2) Нарисовать стрелку, ведущую к нему с одной стороны 3) Сгруппировать результат. 4) Скопировать полученную группу 5) Вставить рисунок в пустой текстовый документ 6) ПКМ, Привязка - Как символ 7) Сохранить, закрыть, открыть. 8) ??????? 9) PROFIT! Ещё пытаться найти? Кажется, где-то у себя я подобное видел.
(In reply to NickKolok from comment #6) > Should I try to find even more test cases? It seems that I've had one in one > of my documents. This is fine, thanks.
Created attachment 121436 [details] One more example - with "sun", where size of the imahe changes Look! This is the Sun. Right-click it, change "Anchor" to "As Character", save, close, reopen. The Sun turned into a satellite, didn't it? Type or delete some text anywhere (or do any changes — to be able to save the document), save and reopen. The satellite flies down, doesn't it?
(In reply to Beluga from comment #7) > (In reply to NickKolok from comment #6) > > Should I try to find even more test cases? It seems that I've had one in one > > of my documents. > > This is fine, thanks. I've posted an example with size of image changing on every time when the document is saved. What exploration can I do to help the Community with work on this bug?
(In reply to NickKolok from comment #9) > I've posted an example with size of image changing on every time when the > document is saved. > What exploration can I do to help the Community with work on this bug? I just tested the first example and the problem is already in 3.5. Do you mean exploration regarding fixing the bug? First you have to be able to compile LibreOffice and then explore the source code. https://wiki.documentfoundation.org/Development Regarding quality assurance, there isn't really anything more you can do. You are of course invited to join the quality assurance team and this way you will make it easier for developers to fix any bugs https://wiki.documentfoundation.org/QA/Triage_For_Beginners Win 7 LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
** 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-20170103
Dear NickKolok, 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
Dear NickKolok, 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