https://bugs.documentfoundation.org/show_bug.cgi?id=174052
Bug ID: 174052
Summary: Windows: Emoji font fallback can fail in Writer when
Adobe Creative Cloud is running, depending on
installed font set
Product: LibreOffice
Version: 26.2.6.3 release
Hardware: x86 (IA32)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Description:
On Windows 11, LibreOffice Writer can lose its normal font fallback to Segoe UI
Emoji when Adobe Creative Cloud is already running before LibreOffice is
started.
The issue affects text formatted with normal fonts such as Arial, Times New
Roman or Liberation Sans. Emoji characters that are not contained in those
fonts are normally rendered correctly through font fallback to Segoe UI Emoji.
On the affected system, the following happens:
- If LibreOffice is started before Adobe Creative Cloud, emoji fallback works
correctly.
- If LibreOffice is completely closed, Adobe Creative Cloud is started, and
LibreOffice is then started again, the same emoji characters may be displayed
as tofu/missing-glyph boxes.
- The Unicode characters themselves remain intact. Copying the missing-glyph
box to another application produces the correct emoji.
- Explicitly formatting the same character with Segoe UI Emoji always renders
it correctly.
- A LibreOffice process that was started before Creative Cloud continues to
display the emojis correctly even if Creative Cloud is started afterwards. The
problem appears only after LibreOffice is fully restarted while Creative Cloud
is already running.
The behavior also depends on the installed font set.
During testing, different font combinations could switch the problem on or off.
This is not simply related to the number of fonts or font descriptors:
- With DIN Medium installed, emoji fallback works.
- With DIN Medium + DIN Light installed, emoji fallback still works.
- With DIN-Black installed instead, emoji fallback fails.
- Other unrelated TrueType fonts can also trigger the failure in another font
combination.
Therefore DIN-Black appears to be one possible trigger, but not the only one.
The problem does not occur on a second Windows 11 computer with the same
LibreOffice version and Adobe Creative Cloud setup but a different installed
font set.
A fresh LibreOffice user profile and a LibreOffice reinstall did not change the
behavior.
Segoe UI Emoji itself is installed correctly and works when selected
explicitly.
This may be related to bug 173967, which also concerns Windows font enumeration
/ emoji fallback, but in this case Segoe UI Emoji and Segoe UI Symbol remain
present and their registry order does not change.
Steps to Reproduce:
On the affected Windows system:
1. Exit Adobe Creative Cloud completely.
2. Start LibreOffice Writer.
3. Enter or paste emoji characters into text formatted with Arial, Times New
Roman or Liberation Sans.
4. Verify that the emojis are displayed correctly through font fallback.
5. Close LibreOffice completely.
6. Start Adobe Creative Cloud.
7. Start LibreOffice Writer again.
8. Open the same document or enter the same emoji characters.
Result: the emoji characters may now appear as missing-glyph/tofu boxes.
Additional reproduction on this system:
9. With Adobe Creative Cloud running, change the installed font set and restart
LibreOffice completely after each change.
10. With DIN Medium installed, emoji fallback works.
11. With DIN Medium + DIN Light installed, emoji fallback still works.
12. With DIN-Black installed instead, emoji fallback fails.
Other unrelated fonts can also trigger the same failure, so the issue appears
to depend on the exact font environment.
Actual Results:
Emoji characters in fonts such as Arial, Times New Roman and Liberation Sans
are displayed as missing-glyph/tofu boxes instead of falling back to Segoe UI
Emoji.
The characters themselves are still correct Unicode characters.
Segoe UI Emoji remains installed and available, and the same characters are
rendered correctly if Segoe UI Emoji is explicitly selected.
Whether the problem occurs depends on the current font environment and on
whether LibreOffice was started before or after Adobe Creative Cloud.
Expected Results:
LibreOffice Writer should consistently use the appropriate fallback font, such
as Segoe UI Emoji, for emoji characters that are not available in the currently
selected text font.
Starting Adobe Creative Cloud or changing unrelated installed fonts should not
cause emoji fallback to stop working.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
System:
- Windows 11
- LibreOffice 26.2.6.3
- Adobe Creative Cloud installed and current
- Segoe UI Emoji and Segoe UI Symbol are both installed
Additional observations:
- Explicit use of Segoe UI Emoji always works.
- The problem affects generic missing-glyph fallback, not the ability of
LibreOffice to render Segoe UI Emoji itself.
- The Unicode content is not corrupted.
- A fresh LibreOffice user profile did not solve the problem.
- Reinstalling LibreOffice did not solve the problem.
- Segoe UI Emoji and Segoe UI Symbol font files were compared with a second
Windows computer where the problem does not occur; the files are identical.
- The registry order of Segoe UI Emoji and Segoe UI Symbol is identical on both
computers.
- Segoe UI Emoji remains listed before Segoe UI Symbol in LibreOffice font
enumeration.
- A LibreOffice process started before Creative Cloud remains unaffected after
Creative Cloud is started.
- The issue appears only after LibreOffice is fully restarted while Creative
Cloud is already running.
- The total number of font descriptors is not sufficient to explain the
problem: configurations with the same or even a higher descriptor count can
work, while another font combination with the same count can fail.
- The second Windows computer uses the same LibreOffice and Adobe Creative
Cloud setup but has a different font set and does not show the problem.
Possibly related:
https://bugs.documentfoundation.org/show_bug.cgi?id=173967
--
You are receiving this mail because:
You are the assignee for the bug.
