Bug 399510 - Noto emojis do not work in application title bar
Summary: Noto emojis do not work in application title bar
Status: RESOLVED DUPLICATE of bug 376813
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-08 09:56 UTC by Bobby Wibowo
Modified: 2018-10-08 10:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bobby Wibowo 2018-10-08 09:56:51 UTC
SUMMARY

Noto emojis do not work in application title bars, and probably everywhere else in plasma workspace.

STEPS TO REPRODUCE

1. Install fonts-noto-color-emoji package.
2. Restart and observe.

OBSERVED RESULT

Screenshot of its behavior in Chromium: https://i.fiery.me/7wit.png

* Title bar: some glyphs are missing, except scissor, and even then scissor is using black&white emoji (not sure from where it comes from, I do not have fonts-symbola package installed).
* Browser's tab bar and tooltip: missing glyphs are being fulfilled by noto emojis, but the existing scissor emoji keeps on using black&white.
* Browser's content (web page): noto emojis are all being used properly (at least from what can be seen from the scissor emoji).

On another note, firefox does not want to use noto emojis in its interface (browser tab and tooltip), however it does use them on web page: https://i.fiery.me/IZjR.png.

EXPECTED RESULT

Only noto emojis being used everywhere.

SOFTWARE VERSIONS

KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

I upgraded to bionic about a week ago, then a few days after I noticed that fonts-noto-color-emoji became a require dependency of neon-desktop. After installing it, they don't really work that well apparently.
Comment 1 Christoph Feck 2018-10-08 10:00:09 UTC

*** This bug has been marked as a duplicate of bug 376813 ***