Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] godot 3.5: Font rendering in editor broken.
Date: Mon, 08 Aug 2022 19:10:10 +0200	[thread overview]
Message-ID: <20220808171010.rO_N4NQcVPNOjibTTSMVZBfj9DcrrwBzDDEHE-l50to@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38526@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

Closed issue by chili-b on void-packages repository

https://github.com/void-linux/void-packages/issues/38526

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.16_1 x86_64 GenuineIntel uptodate FFFFFFFFFF

### Package(s) Affected

godot-3.5_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Font rendering in the editor should work.

### Actual behaviour

Font rendering in the editor is broken:
![image](https://user-images.githubusercontent.com/21281636/183323515-56d42543-7c57-41be-bee3-2b10342d9d03.png)

Godot writes the following error message:
```
ERROR: Unknown font format.
   at: _load (scene/resources/dynamic_font.cpp:178)
```
here is the relevant line in godot's source: https://github.com/godotengine/godot/blob/3.5-stable/scene/resources/dynamic_font.cpp#L178

### Steps to reproduce

1. Install Godot 3.5
2. Open the editor

      parent reply	other threads:[~2022-08-08 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  1:59 [ISSUE] " chili-b
2022-08-08  5:47 ` classabbyamp
2022-08-08 12:23 ` chili-b
2022-08-08 13:34 ` Relected
2022-08-08 13:50 ` Relected
2022-08-08 17:10 ` Duncaen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220808171010.rO_N4NQcVPNOjibTTSMVZBfj9DcrrwBzDDEHE-l50to@z \
    --to=duncaen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).