Force fontconfig-parser version to v0.5.7 #1947
Merged
+13
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OBorce
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today I discovered that when built from master, node-gui UI looks like this on my Ubuntu machine:
The first bad commit is 8dbc6b9 where the only significant changes are those in
Cargo.lock. I managed to narrow it down to thefontconfig-parsercrate which was updated from v0.5.7 to v0.5.8 in that commit.So in this PR I forcibly set the version back to 0.5.7 via
[patch]. This is a hacky fix though, ideally we should find the real culprit (which may not befontconfig-parseritself) and at least file a bug report.Update: it seems that the issue is specific to MATE desktop. I.e. I was able to reproduce it on a fresh install of Ubuntu MATE, but not on a fresh install of the vanilla Ubuntu.