Created attachment 84977 [details] sample incomplete ellipses Problem description: incorrect filling ellipses Steps to reproduce: 1. .... 2. .... 3. .... Current behavior: Expected behavior: Operating System: Ubuntu Version: 4.1.1.2 rc
We need more from you if we're going to do anything about this bug. We need: Your operating system and what version of libreoffice you're using. Exact steps on how to reproduce Exact issue that you are seeing What you expect to see. A much clearer title would be nice - the title should tell us what the problem is not just say a shape - if possible. We understand if there are language barriers or other reasons why the title isn't clear. Marking as NEEDINFO. Once you provide all of the above, please mark as UNCONFIRMED.
Created attachment 88170 [details] the gap exported to bmp
I can reproduce the bug (as far as I understand it) with libreoffice 4.1.0.4 from Debian Wheezy backports amd64. To do this you need to draw filled ellipse or filled curve and look at its right or bottom border. You can see a gap between filling and border. A scale or the ellipse size should be big enough. I attache a part with the gap after importing to bmp. I can not reproduce the bug with libreoffice draw 4.1.2.3 on windows 7. Can somebody try this on other platforms?
Reproducible with LibreOffice 4.1.4.0.0+ under Ubuntu 13.10 x86-64. The bug is related to the graphics antialiasing. Indeed if you disable antialiasing for graphics in menu Tools > Options > LibreOffice > View the gap disappears. Reproducible with master too (Version: 4.2.0.0.alpha1+ Build ID: 9ab89a7599f79092027ae86b5b4cd0e3d67b8b4d). Thank you for the bug report. 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 (4.4.1 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-04-18
Reproducible with LibreOffice 3.5.4, 4.3.3, 4.4.0.0 beta2 and 4.5.0.0 alpha1 on Debian x86_64.
** 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.5 or 5.2.1 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-20160920
Not reproducible anymore in LO 5.2.3.0+ and current master, both built at home under Ubuntu 16.04 x86-64. Closing as WorksForMe. Please, feel free to reopen if you disagree. Best regards. JBF