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

[Bug?] Creating a new container broke font cache #19

Closed
VortexAcherontic opened this issue Jan 17, 2024 · 2 comments
Closed

[Bug?] Creating a new container broke font cache #19

VortexAcherontic opened this issue Jan 17, 2024 · 2 comments

Comments

@VortexAcherontic
Copy link
Contributor

After opening the app for the very first time and creating a new container my font cache got broken.
I had to resoter this by running fc-cache --force on my host machine.

Bildschirmfoto vom 2024-01-17 19-46-56

Bildschirmfoto vom 2024-01-17 19-47-39

Bildschirmfoto vom 2024-01-17 19-48-08

@VortexAcherontic VortexAcherontic changed the title Creating a new container broke my font cache Creating a new container broke font cache Jan 17, 2024
@VortexAcherontic VortexAcherontic changed the title Creating a new container broke font cache [Bug?] Creating a new container broke font cache Jan 17, 2024
@Dvlv
Copy link
Owner

Dvlv commented Jan 17, 2024

BoxBuddy doesn't touch anything to do with the font cache, so I assume this is a flatpak issue or GTK issue outside of BoxBuddy's scope.

@VortexAcherontic
Copy link
Contributor Author

BoxBuddy doesn't touch anything to do with the font cache, so I assume this is a flatpak issue or GTK issue outside of BoxBuddy's scope.

I pretty much assume this as well. I had similar symptoms in the past with just the cli tools already. Sorry for the false positive report.

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

2 participants