Skip to content
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

Tahoma Fonts is installed with wrong permissions, making unable to use in a lot of games #2295

Open
edu-bm7 opened this issue Nov 13, 2024 · 3 comments

Comments

@edu-bm7
Copy link

edu-bm7 commented Nov 13, 2024

When we install Tahoma fonts through winetricks, it installs the font with 444 permissions, instead of the 644 standard of the corefonts package, simply changing that permission fixed a bug in the game I play. My OS is Fedora 41, but I had a friend having the same problem on Kubuntu
Screenshot From 2024-11-13 00-52-03

@Chiitoo
Copy link
Collaborator

Chiitoo commented Nov 13, 2024

I don't think Winetricks does anything with the permissions.

In fact, extracting them using something like 7-zip instead of cabextract for example will produce the same results: all files except the INF files are read-only.

At this time I don't remember if this happens with all cabinet archives when extracted on Linux, or if there's something that can be done on Windows to affect it while creating the archive.

I don't remember seeing reports about games failing due to this (not that me not remembering something necessarily means much), but could you give an example of one?

Thank you!

@edu-bm7
Copy link
Author

edu-bm7 commented Nov 15, 2024

Sorry for not giving an example, here I tested in a private Ragnarok server, and without the 644 permission on Tahoma the line spacing on text looks weird after typing a lot of text, after changing the permission the cursor went back to normal. It might be game related though! First SS is with 444 permisions, second with 644
Before
After

@austin987
Copy link
Contributor

This seems like an application bug. Have you tested this on Windows? On windows the files aren't writable either.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants