Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Collabora Online (CODE)
  3. Fontconfig error: No writable cache directories

Fontconfig error: No writable cache directories

Scheduled Pinned Locked Moved Unsolved Collabora Online (CODE)
7 Posts 3 Posters 2.7k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W Offline
      W Offline
      warg
      wrote on last edited by warg
      #1

      Hello,

      I updated my Collabora instance and noticed that during the update and shutdown/startup process both times the app complains several times about:

      Fontconfig error: No writable cache directories

      Seems like some caching directory is read-only.

      Best Regards,

      1 Reply Last reply
      1
      • nebulonN nebulon marked this topic as a question on
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        Have you adjusted the app config somehow? At least on a fresh instance I can't reproduce the issue.

        1 Reply Last reply
        0
        • W Offline
          W Offline
          warg
          wrote on last edited by
          #3

          In the app settings I have just enabled the "Disable indexing" option for robots.txt and in coolwsd.xml I changed nothing.

          I just saw that in the Collabora settings (after logging in to the app) I saw this string:

          [a-zA-Z0-9_\-.]*

          Doesn't look like something I have maintained. Maybe my previous setting was overriden by an update? Sounds wrong to me because the hostname part is completely missing. Beside of that, I doubt it's related to the above error.

          I also noticed that the fonts directory of Collabora is empty.

          1 Reply Last reply
          0
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #4

            The fonts directory is only for custom fonts to place https://docs.cloudron.io/apps/collabora/#adding-fonts

            The regular expression actually has a bug, which is then fixed with the next package version. But this should not be related to your original cache issue, which I still can't reproduce.

            Since the app as such is basically stateless, if you haven't made any special setting adjustments, can you try to reinstall it to see if you still encounter the caching issue?

            1 Reply Last reply
            0
            • W Offline
              W Offline
              warg
              wrote on last edited by
              #5

              I have sent you the full log of a new/fresh installation via email.

              1 Reply Last reply
              0
              • necrevistonnezrN Offline
                necrevistonnezrN Offline
                necrevistonnezr
                wrote on last edited by necrevistonnezr
                #6

                I have the same error, albeit with the built-in CODE Server. Trying to open a document results in the app being non-responsive.

                EDIT: The non-responsiveness was due to not enough "mdm-workers" 😉

                1 Reply Last reply
                1
                • W Offline
                  W Offline
                  warg
                  wrote on last edited by
                  #7

                  Support couldn't reproduce it for now so they just ignore it for now as it's not critical. Maybe someday we have an idea on what causes this.

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • Bookmarks
                    • Search