Description: Font drop down has Linux Biolinum G selected, while the font being Verdana Steps to Reproduce: 1. Open Writer 2. Set font to: Linux Biolinum G (or some other font) 3. Type Hello World 4. Select "Hello World" 5. Format -> Character -> Font tab 6. Type: Verdana 7. Hit Enter (or Press OK) 8. Press the drop down arrow of the font box -> Linux Biolinum G being selected 9. Press drop down arrow again: still showing Linux Biolinum G 10. Click inside Hello World -> Verdana is back Actual Results: Linux Biolinum G marked as active Expected Results: Verdana marked as active Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c9916d9be9c060d43fc063b76d70629162650fea CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL threaded
Also in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL and in OpenOffice 2.2.0
On pc Debian x86-64 with master sources updated today, I could reproduce this. Nitpick: indeed at the steps 8 and 9, I see "Linux Biolinum G" selected by default in the list but at step 10 I can't say the new font (I don't have "Verdana" so used "Rubik") is back since it's always the one on the dialog (I mean above the list).
@Heiko Any opinion on how this should be fixed? Adding it to the list of last used fonts, or filtering the applied font in drop down?
It's a feature. You can _request_ any font name from the OS. Think of different workstations with Windows and Linux where on one a font is known while on the other not. So to enter a font name directly is the same as picking one from the list, with all the consequences such as what comes next.
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