-
-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Bottles Font install issue ? #3096
Comments
I also took a look at another Bottles C:\Windows\Fonts where I installed the Allfonts and other font dependencies, It had ttf files for alot of MS fonts like Tahoma, Lucon etc but Arial ttf was missing, I then Installed the Arial32 dependency and Arial ttf is still missing in there. |
The URLs provided in the |
I'm now facing the same issue |
Likewise, although I have installed Microsoft fonts on my system (Arch), both with and without installing allfonts on the bottle (using latest flatpak version), fonts appear terrible and unreadable. |
Describe the bug
I was trying to play the Windows version of Rimworld (GOG) inside a wineprefix, the game worked fine but it had no fonts.
As in places where there should be text was entirely blank.
https://www.reddit.com/r/RimWorld/comments/tb2265/rimworld_on_linux_kinda_broken/
According to this, I needed to have the Arial font installed.
I previously used Lutris, in Lutris using winetricks to install the necessary Arial font resolved my issue.
But in Bottles, even after I installed the Arial font dependency, text in the game still did not appear.
It was only after I downloaded a copy of Arial.ttf off of the internet and placed it in C:\Windows\Fonts did the text finally appear.
This leads me to believe this is a bug/regression in Bottles, as I also clearly remember using Bottles to play Rimworld a few months ago and the Arial font dependency install working fine just like Lutris.
To Reproduce
Package
Flatpak from Flathub
Distribution
Fedora Silverblue 39 Beta
Debugging Information
Troubleshooting Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: