Bug 107989 - EDITING: Some sort of artifacts in the corners of a shape when using line styles
Summary: EDITING: Some sort of artifacts in the corners of a shape when using line styles
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shapes-Line
  Show dependency treegraph
 
Reported: 2017-05-21 13:12 UTC by Telesto
Modified: 2025-09-21 03:25 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Example file (9.53 KB, application/vnd.oasis.opendocument.graphics)
2017-05-21 13:13 UTC, Telesto
Details
Screenshot (123.97 KB, image/jpeg)
2017-05-21 13:14 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-05-21 13:12:57 UTC
Description:
A bit of a nitpicking but corners look sometimes a bit odd when a line style is applied. The same sort of 'artifacts' can be reproduced in Word (so not unique for LibO), but not that often.


Steps to Reproduce:
1. Open the attached file
2. Take a look at the corners

Actual Results:  
Pac-man shaped corners

Expected Results:
No pac-man shaped corners


Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Version: 5.5.0.0.alpha0+
Build ID: d57e6cd9dcc96112994ca2b14ac45896e86b26e5
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-05-18_22:43:07
Locale: nl-NL (nl_NL); Calc: CL

and 3.3.0


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Telesto 2017-05-21 13:13:15 UTC
Created attachment 133432 [details]
Example file
Comment 2 Telesto 2017-05-21 13:14:54 UTC
Created attachment 133433 [details]
Screenshot
Comment 3 Stéphane Guillou (stragu) 2017-05-22 13:43:48 UTC
I see the same result in 

Version: 5.2.5.1
Build ID: 1:5.2.5~rc1-0ubuntu1~trusty0
CPU Threads: 2; OS Version: Linux 3.13; UI Render: default; VCL: gtk2; 
Locale: en-GB (en_GB.UTF-8); Calc: group

Switching to "new".
Comment 4 QA Administrators 2018-09-20 02:51:16 UTC Comment hidden (obsolete)
Comment 5 Roman Kuznetsov 2018-09-20 12:18:25 UTC
still repro in

Version: 6.1.1.1
Build ID: 2718b4a18dfcc6a54ebe5f7b801ee7a47fa81e0c
CPU threads: 4; OS: Windows 6.1; UI render: default; 
Locale: ru-RU (ru_RU); Calc: group threaded
Comment 6 QA Administrators 2019-09-21 03:07:23 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2021-09-21 04:52:25 UTC Comment hidden (obsolete)
Comment 8 Sophie Sipasseuth 2023-09-21 08:19:07 UTC
It is not perfect, but it looks better in the last version of LO:

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: df3b95a39472e18ea8acdaae447b7176e37a9256
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: threaded
Comment 9 QA Administrators 2025-09-21 03:25:27 UTC
Dear Telesto,

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