Description: When I draw in LO Draw simple sketches and copy them in LO Writer they are screwed up. Moving them or resizing them screws them up completely. Steps to Reproduce: 1. Draw a sketch in Draw 2. Copy into Writer (grouping them leads to slightly different results, but doesn't remove ptroblem) 3. shift drawing by mouse 4. close and open writer Actual Results: see attachment Expected Results: lines are turned, shifted and changed in lenght. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: de Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Created attachment 138956 [details] screwed up drawing
Created attachment 138957 [details] drawing copied into LO writer
Created attachment 138958 [details] the screwed up drawing being imported into writer
Try grouping the objects before copying into Writer.
Steps: 1. Open the attached document 2. Select everything in the document 3. Move it around Reproduced in Version: 6.1.0.0.alpha0+ Build ID: 0ef0740298b45379bbf8d00d50beffee7a2f812a CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded
Reproduced in Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
(In reply to Mike Kaganski from comment #4) > Try grouping the objects before copying into Writer. Already mentioned: "(grouping them leads to slightly different results, but doesn't remove problem)" ------ It doesn't help- that's the big point. Try it out: I am making as a Tech teacher my sketches with LO draw being imported into LO Writer. Any Bug came in and this is not acceptoble. In earlier versions this problem was not existent. I think it's existent since anybody "optimized" draw by picking up one line and then the 2nd line is "jumping". This is already a problem in LO draw. Today I lost 1 hour (OK-programmers do a great work!). Furthermore "undo" does NOT work. Hermann
Created attachment 138983 [details] Screenshot of broken graphic in OOo 3.3.0 (In reply to Hermann Rochholz from comment #7) > (In reply to Mike Kaganski from comment #4) > > Try grouping the objects before copying into Writer. > > Already mentioned: > "(grouping them leads to slightly different results, but doesn't remove > problem)" > ------ > It doesn't help- that's the big point. > Try it out: I am making as a Tech teacher my sketches with LO draw being > imported into LO Writer. Sorry; was under impression that your "grouping them leads to slightly different results" means grouping *after* it has been inserted into Writer (so I suggested to try *before*) - and yes, I didn't look into your attached example, sorry. > > Any Bug came in and this is not acceptoble. > > In earlier versions this problem was not existent. This isn't true. As Xisco mentioned in comment 6, it is reproducible since the very first version of LO. I just have tried with OpenOffice.org 3.3.0 OOO339m20 (Build:9567) - just in case, - and it is reproducible there, too.
Hmm- yes - this grouping confuses me completely how it works. But I use it always the same way: Group in Draw and copy to Writer. That was a problem for the drawings. Since 3 years I use LO Draw intensively for my complex sketches and I never had these problems. 7 months ago I wrote a bug report about svg-export of LO Draw to Inkscape. (108002 not fixed :-( ) These problems never were existent.
** 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
Dear Hermann Rochholz, 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://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
Repro 7.2+.
Dear Hermann Rochholz, 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 the problem in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1309e6332d7ff2bd1f9b6bf87385b8b570e59158 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Please try with a daily build. It can be installed parallel to your regular LibreOffice version. https://dev-builds.libreoffice.org/daily/master/
I checked with Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-PL (pl_PL); UI: en-PL Calc: CL threaded and the error does not occur for me, I also checked the daily build version as someone suggested in the discussion and the error does not occur too: Version: 7.6.0.0.alpha1+ (x86) / LibreOffice Community Build ID: 1c98c88a1208f47327ac2f3beaf593521ce9b394 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: pl-PL (pl_PL); UI: en-US Calc: CL threaded
Based on comment 14 and comment 15 it's a WFM.