starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

OpenType support for several fonts is missing, taking up a good chunk of console errors. #2182

New issue

Open

opened 2026-02-20 22:01:19 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-20 22:01:19 -05:00

Owner

Originally created by @SC1040-TS2 on GitHub (Apr 11, 2021).

Describe the bug
As of the latest 1.4.0 development snapshot (currently using the Windows x64 snapshot version), the Mumble console logs have a chance of reporting a myriad of missing OpenType fonts, designated Script 17 and Script 20 in most examples.
Steps to Reproduce
Unfortunately, I do not know how exactly to reproduce it. It may be a case of a first-time failure to load the fonts, or otherwise something else.
Expected behavior
OpenType not failing to load fonts and not reporting such a failure in the console.
Screenshots
Unfortunately, no screenshots exist of the phenomenon.
Desktop (please complete the following information):

OS: Windows 10 x64 Build Version 19042.906.
Version: Mumble 1.4.0 Developer Snapshot 4.

Additional context
This may relate to an existing issue or pull request, but I have yet to find the right one to cite.

Originally created by @SC1040-TS2 on GitHub (Apr 11, 2021). **Describe the bug** As of the latest 1.4.0 development snapshot (currently using the Windows x64 snapshot version), the Mumble console logs have a chance of reporting a myriad of missing OpenType fonts, designated Script 17 and Script 20 in most examples. **Steps to Reproduce** Unfortunately, I do not know how exactly to reproduce it. It may be a case of a first-time failure to load the fonts, or otherwise something else. **Expected behavior** OpenType not failing to load fonts and not reporting such a failure in the console. **Screenshots** Unfortunately, no screenshots exist of the phenomenon. **Desktop (please complete the following information):** - OS: Windows 10 x64 Build Version 19042.906. - Version: Mumble 1.4.0 Developer Snapshot 4. **Additional context** This may relate to an existing issue or pull request, but I have yet to find the right one to cite.

deekerman added the

client

windows

bug

labels

2026-02-20 22:01:19 -05:00

deekerman commented

2026-02-20 22:01:21 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Apr 13, 2021):

I suspect this is a Qt-related issue as we don't explicitly deal with fonts.

So you said that this only happened the first time you started Mumble but after that it never happened again?

Have you been using a different version of Mumble on that same machine before? (Maybe even an older snapshot)? If so: Did the issue occur there as well?

@Krzmbrzl commented on GitHub (Apr 13, 2021): I suspect this is a Qt-related issue as we don't explicitly deal with fonts. So you said that this only happened the first time you started Mumble but after that it never happened again? Have you been using a different version of Mumble on that same machine before? (Maybe even an older snapshot)? If so: Did the issue occur there as well?

deekerman commented

2026-02-20 22:01:22 -05:00

Author

Owner

@SC1040-TS2 commented on GitHub (Apr 15, 2021):

Seemingly, if not the first few times this occurred. Clearing the console once and saving it appears to have stopped that for whatever reason.

Yes I have, actually. Previously it was the 1.3.4 Stable build. However, the console messages had dated to after downloading and running the 1.4.0 Development Snapshot, on the day the original post was made.

@SC1040-TS2 commented on GitHub (Apr 15, 2021): Seemingly, if not the first few times this occurred. Clearing the console once and saving it appears to have stopped that for whatever reason. Yes I have, actually. Previously it was the 1.3.4 Stable build. However, the console messages had dated to after downloading and running the 1.4.0 Development Snapshot, on the day the original post was made.

deekerman commented

2026-02-20 22:01:22 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Apr 16, 2021):

Are perhaps the mentioned OpenType fonts missing on your system?

@davidebeatrici commented on GitHub (Apr 16, 2021): Are perhaps the mentioned OpenType fonts missing on your system?

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Apr 16, 2021):

Nevermind, I can reproduce the issue:

<W>2021-04-16 22:53:43.838   OpenType support missing for "MS Shell Dlg 2", script 20
<W>2021-04-16 22:53:43.840   OpenType support missing for "Arial", script 20
<W>2021-04-16 22:53:43.841   OpenType support missing for "MS UI Gothic", script 20
<W>2021-04-16 22:53:43.842   OpenType support missing for "SimSun", script 20
<W>2021-04-16 22:53:43.906   OpenType support missing for "MS Shell Dlg 2", script 17
<W>2021-04-16 22:53:43.907   OpenType support missing for "Arial", script 17
<W>2021-04-16 22:53:43.908   OpenType support missing for "MS UI Gothic", script 17
<W>2021-04-16 22:53:43.909   OpenType support missing for "SimSun", script 17
<W>2021-04-16 22:53:44.176   OpenType support missing for "Segoe UI", script 20
<W>2021-04-16 22:53:44.177   OpenType support missing for "Arial", script 20
<W>2021-04-16 22:53:44.179   OpenType support missing for "MS Shell Dlg 2", script 20
<W>2021-04-16 22:53:44.179   OpenType support missing for "MS UI Gothic", script 20
<W>2021-04-16 22:53:44.180   OpenType support missing for "SimSun", script 20

@davidebeatrici commented on GitHub (Apr 16, 2021): Nevermind, I can reproduce the issue: ``` <W>2021-04-16 22:53:43.838 OpenType support missing for "MS Shell Dlg 2", script 20 <W>2021-04-16 22:53:43.840 OpenType support missing for "Arial", script 20 <W>2021-04-16 22:53:43.841 OpenType support missing for "MS UI Gothic", script 20 <W>2021-04-16 22:53:43.842 OpenType support missing for "SimSun", script 20 <W>2021-04-16 22:53:43.906 OpenType support missing for "MS Shell Dlg 2", script 17 <W>2021-04-16 22:53:43.907 OpenType support missing for "Arial", script 17 <W>2021-04-16 22:53:43.908 OpenType support missing for "MS UI Gothic", script 17 <W>2021-04-16 22:53:43.909 OpenType support missing for "SimSun", script 17 <W>2021-04-16 22:53:44.176 OpenType support missing for "Segoe UI", script 20 <W>2021-04-16 22:53:44.177 OpenType support missing for "Arial", script 20 <W>2021-04-16 22:53:44.179 OpenType support missing for "MS Shell Dlg 2", script 20 <W>2021-04-16 22:53:44.179 OpenType support missing for "MS UI Gothic", script 20 <W>2021-04-16 22:53:44.180 OpenType support missing for "SimSun", script 20 ```

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Apr 17, 2021):

@davidebeatrici what did you have to do in order to reproduce this?

@Krzmbrzl commented on GitHub (Apr 17, 2021): @davidebeatrici what did you have to do in order to reproduce this?

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Apr 17, 2021):

Open the settings dialog.

@davidebeatrici commented on GitHub (Apr 17, 2021): Open the settings dialog.

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@SC1040-TS2 commented on GitHub (Apr 17, 2021):

Mumble 1.4.0 OpenType font support missing Full List.txt

Here is a full list of what the console output is, as further documentation of affected fonts.

@SC1040-TS2 commented on GitHub (Apr 17, 2021): [Mumble 1.4.0 OpenType font support missing Full List.txt](https://github.com/mumble-voip/mumble/files/6329864/Mumble.1.4.0.OpenType.font.support.missing.Full.List.txt) Here is a full list of what the console output is, as further documentation of affected fonts.

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Apr 18, 2021):

@SC1040-TS2 is this behavior also related to opening the settings for you or does it occur in other situations as well?

@Krzmbrzl commented on GitHub (Apr 18, 2021): @SC1040-TS2 is this behavior also related to opening the settings for you or does it occur in other situations as well?

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@SC1040-TS2 commented on GitHub (Apr 18, 2021):

It seems to be specific to opening the Settings dialogue, coinciding with a slight delay between clicking on it and the page opening.

However, I have also found a new bug which I will be documenting later.

@SC1040-TS2 commented on GitHub (Apr 18, 2021): It seems to be specific to opening the Settings dialogue, coinciding with a slight delay between clicking on it and the page opening. However, I have also found a new bug which I will be documenting later.

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Apr 19, 2021):

Okay then we "just" have to find out what parts of the settings dialog are causing this issue... 🤔

@Krzmbrzl commented on GitHub (Apr 19, 2021): Okay then we "just" have to find out what parts of the settings dialog are causing this issue... :thinking:

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@SC1040-TS2 commented on GitHub (Apr 19, 2021):

Okay then we "just" have to find out what parts of the settings dialog are causing this issue... 🤔

Having tested this somewhat already, it never seems to occur when opening various Settings submenus, such as Audio Output, Input, User Interface, and so on. It seems to be a broad thing for the Settings dialogue itself only. This may not help narrow down the cause that much, but it at least serves as further specification.

@SC1040-TS2 commented on GitHub (Apr 19, 2021): > Okay then we "just" have to find out what parts of the settings dialog are causing this issue... 🤔 Having tested this somewhat already, it never seems to occur when opening various Settings submenus, such as Audio Output, Input, User Interface, and so on. It seems to be a broad thing for the Settings dialogue itself only. This may not help narrow down the cause that much, but it at least serves as further specification.

deekerman commented

2026-02-20 22:01:23 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Apr 19, 2021):

Iirc all settings pages are initialized when the settings dialog gets shown. So it could still be specific to one of them.
However this does indicate that it's probably not the content (the settings) that is being displayed there as that only gets initialized once the respective settings page is shown. At least afaik.

@Krzmbrzl commented on GitHub (Apr 19, 2021): Iirc all settings pages are initialized when the settings dialog gets shown. So it could still be specific to one of them. However this does indicate that it's probably not the content (the settings) that is being displayed there as that only gets initialized once the respective settings page is shown. At least afaik.