Bug 126040 - Loading arrow styles also changes the start and end style in the Line dialog
Summary: Loading arrow styles also changes the start and end style in the Line dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: lowest trivial
Assignee: Not Assigned
Depends on:
Blocks: Arrow_Style
  Show dependency treegraph
Reported: 2019-06-21 13:52 UTC by Buovjaga
Modified: 2024-04-13 03:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Buovjaga 2019-06-21 13:52:57 UTC
1. In any LibO application, draw a line with no arrows
2. Right-click it, click Line
3. Click Arrow Styles tab
4. Click Load Arrow Styles button and load an .soe file OR if you don't have any, first click the Save button to save standard.soe somewhere
5. Click back to Line tab

Observe the start and end styles have changed from none to arrows.

Already in 3.3.0 (Win 10).

Arch Linux 64-bit
Build ID: ff6456b851cbe80f9fa03522c88699cc30ffcfb6
CPU threads: 8; OS: Linux 5.1; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 21 June 2019
Comment 1 Jacques Guilleron 2019-06-24 12:01:59 UTC
Hi  Buovjaga,

I reproduce this behavior since
LO Build ID: 4044db1653798618515c987464157abee9229c11 
on Windows 7 Home.
Before, Line dialog, Arrows Styles Tab displayed a line with arrows at least since LO

Comment 2 QA Administrators 2021-06-24 03:46:44 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2021-08-01 13:03:56 UTC
Still repro

Arch Linux 64-bit
Version: / LibreOffice Community
Build ID: 7b5922eb666e5f153060468b271d99510adb422e
CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 30 July 2021
Comment 4 QA Administrators 2024-04-13 03:14:58 UTC
Dear Buovjaga,

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