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

[5.7.2.2 -> 5.8.3.1] Fontconfig errors during upgrade #2922

Open
2 tasks done
gourvy opened this issue Jan 3, 2025 · 4 comments
Open
2 tasks done

[5.7.2.2 -> 5.8.3.1] Fontconfig errors during upgrade #2922

gourvy opened this issue Jan 3, 2025 · 4 comments
Labels
wontfix Nobody will work on this.

Comments

@gourvy
Copy link

gourvy commented Jan 3, 2025

Describe the issue

I use an instance of Weblate in kubernetes, with kustomize instead of helm. I tried to upgrade from 5.7.2.2 to 5.8.4.1 but got a problem (I'll create a different issue), so I I upgraded to 5.8.3.1 instead. It works fine but I have the following error messages at start:

celery-notify stderr | Fontconfig error: "/app/data/fonts/fonts.conf", line 1: no element found
celery-notify stderr | Fontconfig error: Cannot load config file from /app/data/fonts/fonts.conf
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories

I use a read-only filesystem with /app/data being a read/write volume.

After weblate started, I checked and the file /app/data/fonts/fonts.conf exists.

After restarting the container (pod/deployment) the problem doesn't seems to appear, so I guess it's only during migration.

I already tried

  • I've read and searched the documentation.
  • I've searched for similar filed issues in this repository.

Steps to reproduce the behavior

Start a weblate container 5.7.2.2 (with db, redis, data volume, etc.), then migrate to 5.8.3.1

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

Additional context

No response

@nijel
Copy link
Member

nijel commented Jan 6, 2025

Most likely, this is an outcome of #2923

@gourvy
Copy link
Author

gourvy commented Jan 7, 2025

After modifying my deployment to upgrade an other instance of weblate from 5.7.2.2 to 5.8.4.1 (with no error than the fontconfig errors), I encountered the same error messages. So, I don't think this minor problem is linked to #2923

@nijel
Copy link
Member

nijel commented Jan 9, 2025

Can you please share content of /app/data/fonts/fonts.conf?

Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants