Chrome version 154.0.8037.57-1 updated its statically linked libfontconfig, and now its cache is stomping on the user-level font cache.

To fix this, press Ctrl + Alt + t to open a terminal, and run

rm -rf ~/.cache/fontconfig

And then reboot.

Note that opening Chrome (or a Chromium-based program) will break it again. I edited my ~/.local/share/applications/google-chrome-beta.desktop to do this:

Exec=env XDG_CACHE_HOME=/home/user/.cache/chromecache/ /usr/bin/google-chrome-beta %U

More info:

https://issues.chromium.org/issues/565052667

https://gitlab.freedesktop.org/fontconfig/fontconfig/-/work_items/538

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 7 hours ago (1 child)

It's nice that it is Webkit based but the interface isn't great; for example a lot of wasted space at the top due to the very old fashioned menu bar. Hopefully it will come in to line with other KDE software like Dolphin and move to a hamburger style menu? But regardless it is generally a little clunky and old fashioned.

I think realistically, Konqueror is just too small a project to be able to compete with Firefox or Chromium. It's great that it's maintained, but a little worrying that the last release was in May when internet security risks move very fast. I'm not sure I could in all conscience recommend it but I'm happy to be corrected if these concerns are misplaced?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 6 hours ago

    I think KDE team maintains it, but I must admit I have no proof of such... it is just pure faith into them...

    Yet should I have no choice between chromium and konqueror, I would take the second without even trying the first.

    And I really loved konqueror before I became a gnome user... You can run konsole in konqueror, isn't that cool?

  • source
  • parent