Split from bug 83754
Since 4.4, "♦︎" (BLACK DIAMOND SUIT, U+2666 U+FE0E) does not display correctly in the Find & Replace Dialog on Linux
Steps to reproduce:
- Open the attached document
- Select the "♦︎"
- Open "Find & Replace" (Ctrl+H)
- Diamond displays in the search box
- Missing character square displays
This is probably a related phenomenon to bug 86399, but began occurring at a different point in history
Created attachment 114513 [details]
Taking the liberty of setting this to NEW myself, as a commit has been identified.
This seems to have begun at the below commit.
Adding Cc: to firstname.lastname@example.org; Could you possibly take a look at this? Thanks
(note also bug 86399, which had a similar effect on some other characters, but was caused by a different commit)
Author: Matúš Kukan <email@example.com>
Date: Tue May 27 16:37:30 2014 +0200
Related bnc#822625: Cache FontEntry with the original FontSelectPattern.
Otherwise we never hit cache directly, only after expensive call to
(I was led up the garden path by a character picker in comment 0, the "U+FE0E", which is a modifier, is unnecessary to produce the character in question)
I was not able to reproduce this bug.
Perhaps, it was fixed too with b1030f75d3e47719ca63ec518f1da75196bead1a ? or is it something else?
I can still reproduce this on Linux (Ubuntu 14.04) after b1030f75d3e47719ca63ec518f1da75196bead1a.
(Caolan's commit appears to deal with compound characters, which this isn't)
This one works on the same machine prior to the commit mentioned in comment 2, so it shouldn't be e.g. a matter of missing fonts.
Migrating Whiteboard tags to Keywords: (bibisected)
** Please read this message in its entirety before responding **
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
I don't reproduce in Windows in 4.2 so not in 6.5+.