Summary: | No Emoji Support in Notifications and Panel Task Manager | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Chromer <downloader030> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | arojas, hardpenguin13, nate, plasma-bugs, sh.yaron, vanoudt |
Priority: | NOR | ||
Version: | 5.21.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
A Notification which contains emoji
Panel Task Manager |
Description
Chromer
2021-04-25 08:28:49 UTC
Created attachment 137895 [details]
Panel Task Manager
Here, some emoji's show as line art, others simply show the "blank rectangle(s)". For instance, notify-send "👍🏻" doesn't work. Ideally, it'd also be great to have these show as full colour emojis - and not simply line-art. This is on: Fedora 34 KDE Frameworks 5.80.0 Qt 5.15.2 (built against 5.15.2) The wayland windowing system Plasma: 5.21.4 Does it work in other Qt applications? Works for me; the issue points to an issue with your fontconfig. Unfortunately I don't know enough about how fontconfig files work to help you diagnose it; maybe someone from your distro can help? (In reply to Antonio Rojas from comment #4) > Does it work in other Qt applications? Doesn't work in kwrite either. Adding the fontconfig settings from https://gist.github.com/charveey/091b11ea554436d15c7fffcf01129a8a *does* fix the issue, at least here on Fedora 34. Thanks for the pointer, Nate. You're welcome! You might want to contact the Arch packagers and suggest that they adopt those changes upstream. I'm on Fedora here - bug reported upstream at https://bugzilla.redhat.com/show_bug.cgi?id=1954359 Perhaps @Chromer can report it to Arch> Thank you guys for solution. I reported it to Arch Bug Tracker : https://bugs.archlinux.org/task/70621 Arch doesn't do any (font or anything else) configuration on behalf of the users, so there's nothing Arch can do about this. This is ultimately caused by a long-standing Qt bug, which upstream doesn't have much interest in fixing, apparently https://bugreports.qt.io/browse/QTBUG-80434 The workaround found by Nicholas still works - thanks! (Debian Sid here). |