This is a regression to LO 6.0.5: - open the master view - click into an item list - in the sidebar select "More Bullets" to specify the item symbol - in the appearing dialog go to the tab Customize and press there the button Select - choose there a character of your choice and apply your selection now clos the dialog and repeat the procedure: - click into an item list - in the sidebar select "More Bullets" to specify the item symbol - in the appearing dialog go to the tab Customize and press there the button Select result: the character you just applied previously does not appear in the recent character list
I cannot reproduce with Version: 6.2.0.0.alpha0+ Build ID: b7e139fa21607f488465fd87333db757ad0c91a2 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; and Version: 6.2.0.0.alpha0+ (x64) Build ID: b7e139fa21607f488465fd87333db757ad0c91a2 CPU threads: 1; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-07-20_01:39:32 Seems to be fixed in dev version. Please could you test it with dev version? You can download it here: http://dev-builds.libreoffice.org/daily/master/
> I cannot reproduce with Version: 6.2.0.0.alpha0+ > Please could you test it with dev version? Dear developers, please rethink your behavior. I am a normal user. I reported other bugs in LO 6.0.5. Then I got the feedback I should use the unreleased LO 6.1 to test. I did so and found this bug. So your banner on the website states people should help to find bugs in LO 6.1 but when they do so you tell them they should use LO 6.2 alpha. Really? Why should users test out an alpha version when there is a bug in a release candidate? The goal must be to fix bugs in RC versions and stable releases!
Thanks for reporting this issue. This has been fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-6-1&id=a32d9ec1fa48296ffba713bc4593cad45a1c83ad and it will be fixed in LibreOffice 6.1 RC3 if this patch gets submitted: https://gerrit.libreoffice.org/#/c/57765/ Closing as RESOLVED DUPLICATED *** This bug has been marked as a duplicate of bug 118304 ***