Some emojis are not displayed

[ArthurSib]

Steps to reproduce

1. Open a chat with emojis.
2. Open a list with emojis.

Expected behaviour

All emojis are displayed.

Actual behaviour

Not all emojis are displayed.

Diagnosis and logs

Diagnosis report

Diagnosis report

Nextcloud Talk Desktop
Version	v2.0.3
Built-in Talk version	v22.0.2
Release channel	stable
Operating system	Linux 6.14.0-33-generic (#33~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 17:02:30 UTC 2)
Executable Path	/app/lib/com.nextcloud.talk/Nextcloud Talk
Using Wayland	❌ no
Connected to	-
Nextcloud version	31.0.10
Nextcloud Talk version	21.1.5
notifications app enabled	✅ yes
notify_push app enabled	✅ yes

Application config

{
  "launchAtStartup": false,
  "theme": "dark",
  "systemTitleBar": true,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

[ShGKme]

Do you have this problem only in the desktop client, or on web client as well?

[ArthurSib]

@ShGKme, only in the desktop client v. 2.0.3.

In Firefox:

[criegerde]

On Desktop-Client 2.0.3 (Linux AppImage)

^ Wrong colour and some emojis are missing

Web seems to be OK

Desktop Version v. 2.0.2 was not affected (Linux AppImage)

[maxblome]

I tested it with Talk 21 (NC 31) and Talk 22 (NC 32). The problem only occurs with Talk 21.

Client Version: 2.0.3 (Flatpak) Server Version: 21.1.5

Client Version: 2.0.3 (Flatpak) Server Version: 22.0.2

Everything is displayed correctly in the browser.

[dejavix]

Hi, I have the same issue. From browser, emojis are OK (always were). From flatpak application, they are "blue" and a lot of them are missing. I remember this was working.

My client shows the following:

- Version: v2.0.3
- Built-in Talk version: v22.0.2
- Release channel: stable
- Operating system: Linux 6.8.0-85-generic (#85~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 16:18:59 UTC 2)
- Nextcloud version: 31.0.9
- Nextcloud Talk Version: 21.1.5

Output from "flatpak info com.nextcloud.talk":

          ID: com.nextcloud.talk
         Ref: app/com.nextcloud.talk/x86_64/stable
        Arch: x86_64
      Branch: stable
      Origin: talk-origin
  Collection: 
Installation: system
   Installed: 425,7 MB
     Runtime: org.freedesktop.Platform/x86_64/24.08
         Sdk: org.freedesktop.Sdk/x86_64/24.08

      Commit: f0d6eccebb01718d9773e47b69c026428d915b0b415aec2245852dbd19e71b00
     Subject: Export com.nextcloud.talk
        Date: 2025-10-27 18:00:17 +0000

[Fuseteam]

i have it aswell in the flatpak in v2.02 but in the picker it displayed correctly, but when i send it, it is not

[ShGKme]

Client Version: 2.0.3 (Flatpak) Server Version: 21.1.5

Client Version: 2.0.3 (Flatpak) Server Version: 22.0.2

Are you sure the versions are correct? Emojis are rendered completely on the client side in the Talk Desktop client. Server you are connected to cannot affect it...

[dejavix]

Hi, screenshot from "About":

[dejavix]

Anyway, I tend to agree that this must be something on client-side as the web-browser version has no issues with emojis.

[ArthurSib]

upd: On another PC, with the talk desktop v 2.0.3 and the same Nextcloud server, there are no issues with emojis. The OS version are identical on different PCs.

[ShGKme]

Thanks everyone for the details!

There are some problems with the v2.0.3 release on Linux due to a problem in Electron with different problems for different users.

• Too small cursor side
• No tray icon
• Crash on dev tools open
• Getting stuck on the load splash screen

Anyone with the emoji issue, could you:

• Confirm you have the same issue on v2.0.2
• Or wait for the v2.0.4 release with reverting Electron upgrade

[maxblome]

Client Version: 2.0.3 (Flatpak) Server Version: 21.1.5 Client Version: 2.0.3 (Flatpak) Server Version: 22.0.2

Are you sure the versions are correct? Emojis are rendered completely on the client side in the Talk Desktop client. Server you are connected to cannot affect it...

Yes, a production instance with Talk 21, a test instance with 22.

I also used a fresh Flatpak instance for Talk 22, maybe that's why. I'll try again with Talk 21 using a fresh Flatpak instance.

The same problem already existed in version 2.0.2 with Talk 21. Unfortunately, I didn't test it with Talk 22.

[dejavix]

Hi, I have reinstalled 2.0.2 (flatpak install --reinstall ...) - unfortunately, the same issue with emojis in Talk client.

"About" page of Talk client says:

• version v2.0.2
• Built-in Talk version: v22.0.0
• Nextcloud version: 31.0.10
• Nextcloud Talk version: 21.1.5

[ShGKme]

• Might be fixed by https://github.com/nextcloud/talk-desktop/pull/1526

[maxblome]

Problem still exists in version 2.0.4.

[dejavix]

Unfortunately I have the same experience. v2.0.4 did not fix the emojis.

[criegerde]

Error still exists in v. 2.0.4.

Current Workaround: Download and start the *.zip-Version :-(

[ShGKme]

According to the Flatpak documentation, it includes fonts from

• /usr/share/fonts
• /usr/local/share/fonts
• $XDG_DATA_HOME/fonts
• Ref: https://docs.flatpak.org/en/latest/desktop-integration.html#fonts

If fonts are not available in the app, they probably are located somewhere else (I'd guess).

Could you run the following commands and share the result?

To get the locations of locally installed emoji fonts:

fc-list | grep -i emoji

To get the locations of fonts available in flatpak:

# Enter Nextcloud Talk in Flatpak
flatpak run --command=sh com.nextcloud.talk

# List the emoji fonts
fc-list | grep -i emoji

Just to make sure there is no problem on the frontend side, could you also run the following command in the Talk Desktop console?

(await window.queryLocalFonts?.())?.map(font => font.fullName).filter(font => ["Segoe UI Emoji","Segoe UI Symbol","Segoe UI","Apple Color Emoji","Twemoji Mozilla","Noto Color Emoji","EmojiOne Color","Android Emoji"].includes(font)).toString()

And to make sure, Flatpak actually has the fonts mounted as it is supposed to:

flatpak run --command=ls com.nextcloud.talk /run/host/fonts
flatpak run --command=ls com.nextcloud.talk /run/host/local-fonts
flatpak run --command=ls com.nextcloud.talk /run/host/user-fonts

[ShGKme]

Do you have a custom fontconfig file?

[nickvergessen]

Output of my working setup for comparison

my user

$ fc-list | grep -i emoji
/home/nickv/.local/share/fonts/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular

flatpak

$ flatpak run --command=sh com.nextcloud.talk
[📦 com.nextcloud.talk profiler]$ fc-list | grep -i emoji
/usr/share/fonts/noto-emoji/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/run/host/user-fonts/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
[📦 com.nextcloud.talk profiler]$ 

js console

'Noto Color Emoji'

fonts commands:

$ flatpak run --command=ls com.nextcloud.talk /run/host/fonts
cmap  cMap  opentype  truetype	type1  X11
$ flatpak run --command=ls com.nextcloud.talk /run/host/local-fonts
$ flatpak run --command=ls com.nextcloud.talk /run/host/user-fonts
Droid+Sans+Mono+Awesome.ttf  OpenDyslexic3-Regular.ttf	  OpenDyslexic-Italic.otf	SourceCodePro+Powerline+Awesome+Regular.ttf
NotoColorEmoji.ttf	     OpenDyslexic-BoldItalic.otf  OpenDyslexicMono-Regular.otf
OpenDyslexic3-Bold.ttf	     OpenDyslexic-Bold.otf	  OpenDyslexic-Regular.otf

[fraenki]

Output of a non-working setup:

$ fc-list | grep -i emoji
/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular

$ flatpak run --command=sh com.nextcloud.talk
[📦 com.nextcloud.talk ~]$ fc-list | grep -i emoji
/usr/share/fonts/noto-emoji/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/run/host/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular

> (await window.queryLocalFonts?.())?.map(font => font.fullName).filter(font => ["Segoe UI Emoji","Segoe UI Symbol","Segoe UI","Apple Color Emoji","Twemoji Mozilla","Noto Color Emoji","EmojiOne Color","Android Emoji"].includes(font)).toString()
'Noto Color Emoji'

$ flatpak run --command=ls com.nextcloud.talk /run/host/fonts
cmap  cMap  opentype  truetype	type1  X11
$ flatpak run --command=ls com.nextcloud.talk /run/host/local-fonts
$ flatpak run --command=ls com.nextcloud.talk /run/host/user-fonts
ls: cannot access '/run/host/user-fonts': No such file or directory

Looks like the fonts are not mounted in flatpak. 🤔

[ShGKme]

According to the output, everythign is correct... Noto Color Emoji is mounted and even available on the UI.

[ShGKme]

I've just noticed that every diagnosis report with the problem has "Using Wayland: ❌ no", while Ubuntu 24 has it enabled by default.

Could you confirm that you are actually on X11 and it is expected?

[fraenki]

$ echo "$XDG_SESSION_TYPE"
x11

Yes, that's expected :)

[ShGKme]

Cannot reproduce with v2.0.4 on Mint with X11 :(

[dejavix]

Output of my non-working setup:

fc-list | grep -i emoji
/usr/share/fonts/truetype/emojione/emojione-android.ttf: Emoji One:style=Regular
/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular

In flatpak:

flatpak run --command=sh com.nextcloud.talk
fc-list |grep -i emoji
/usr/share/fonts/noto-emoji/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/run/host/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/run/host/fonts/truetype/emojione/emojione-android.ttf: Emoji One:style=Regular

Back in my shell:

flatpak run --command=ls com.nextcloud.talk /run/host/fonts
cmap  cMap  opentype  truetype	type1  X11
flatpak run --command=ls com.nextcloud.talk /run/host/local-fonts
flatpak run --command=ls com.nextcloud.talk /run/host/user-fonts

i.e. the last two commands do not output anything, but also no error is printed...

Javascript console in Talk client: 'Noto Color Emoji'

Finally

echo $XDG_SESSION_TYPE 
x11

[dejavix]

I cannot say if this is related, but I have seen flatpak-related issue when googling: https://github.com/flatpak/flatpak/issues/4770

[Fuseteam]

the locations of locally installed emoji fonts:

$ fc-list | grep -i emoji
/usr/share/fonts/opentype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/home/fuseteam/.local/share/fonts/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/home/fuseteam/.fonts/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular
/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular

the locations of fonts available in flatpak:

# Enter Nextcloud Talk in Flatpak
flatpak run --command=sh com.nextcloud.talk
[📦 com.nextcloud.talk ~]$ fc-list | grep -i emoji                                                               
sh: /dev/shm/byobu-fuseteam-y4XlOXXQ/timer.2: No such file or directory                                          
/usr/share/fonts/noto-emoji/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular                                   
/run/host/fonts/opentype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular                                 
/run/host/user-fonts/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular                                     
/home/fuseteam/.fonts/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular                                    
/run/host/fonts/truetype/noto/NotoColorEmoji.ttf: Noto Color Emoji:style=Regular                                 
[📦 com.nextcloud.talk ~]$  

The Talk Desktop console

(await window.queryLocalFonts?.())?.map(font => font.fullName).filter(font => ["Segoe UI Emoji","Segoe UI Symbol","Segoe UI","Apple Color Emoji","Twemoji Mozilla","Noto Color Emoji","EmojiOne Color","Android Emoji"].includes(font)).toString()
'Noto Color Emoji'

And to make sure, Flatpak actually has the fonts mounted as it is supposed to:

$ flatpak run --command=ls com.nextcloud.talk /run/host/fonts
cmap  cMap  opentype  truetype  type1  woff  X11  
$ flatpak run --command=ls com.nextcloud.talk /run/host/local-fonts
(no output)
$ flatpak run --command=ls com.nextcloud.talk /run/host/user-fonts
noto

This is under sway on wayland fwiw

[ShGKme]

@Fuseteam Do you also have emoji picker broken with call emoji blue and plain like on the screenshots above? Asking because previously only users on X11 had this issue.

[Fuseteam]

yes

i'm on v2.0.4, apologies for being late, i've had this since the start of the issue, i was following from the side lines, untill i saw the x11 comments today