Easy to reproduce 1 - Launch Draw 2 - Add an arrow 3 - By right-click, choose Line 4 - Look at the arrow width, it should be 0.3 cm 5 - change the arrow width from 0 to 0.1 cm 6 - Look at arrow width it should have increased by 0.15 from 0.3 to 0.45 7 - Change the arrow size to whatever value you want or don't change it and close by OK 8 - Right click to line and look to the arrow width. The value is 0.15 more than what it was Expected behaviour : - The arrow width should be at the value left when clicking on OK
Reproducible with Version: 6.1.3.2 (x64) Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU threads: 12; OS: Windows 10.0; UI render: GL; Locale: ru-RU (ru_RU); Calc: CL
Not reproducible with Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) Reproducible with Version: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 Suspect dialog rework regression.
Same Problem with AOO 4.1.5
Bibisected to the following range using repo bibisect-41max. It's a single commit in the bibisect build, as the skipped commits failed to build. https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=d8d55787b81cdc955b73c8befa4ab608f46e32aa..6b412f8bb1397fe18e5213549c50839879206eb7
(In reply to Pierre C from comment #3) > Same Problem with AOO 4.1.5 Must be caused by one of the commits ported from AOO in that range, then.
Suspecting https://git.libreoffice.org/core/+/b8fe3f84a60ea73aed9748844aee80441eb0fc7d; CCed Armin Le Grand. https://gerrit.libreoffice.org/63071
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/9d93e030288aaa721761cb7991d1afdde6335777%5E%21 tdf#121116: don't adapt start/end widths if they are set explicitly It will be available in 6.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Let's call it fixed.