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

Fonts in ~/.local/share/fonts are not taken into account #21

Closed
pieqq opened this issue May 14, 2018 · 11 comments
Closed

Fonts in ~/.local/share/fonts are not taken into account #21

pieqq opened this issue May 14, 2018 · 11 comments

Comments

@pieqq
Copy link

pieqq commented May 14, 2018

Tested on Ubuntu 18.04 with gimp 2.10 (rev 38) installed from stable channel.

Steps to reproduce

  1. Download a font from the Internet, double click on it (it should open with Gnome Fonts)
  2. Press Install
  3. Open Gimp 2.10 (snap version), create a text layer and try to find the newly installed font

Actual results

In step 2, the font is installed in ~/.local/share/fonts. In step 3, this font is not available on Gimp 2.10 (but it is available on Gimp 2.8 installed through apt).

If I manually copy the font from ~/.local/share/fonts to ~/.fonts/ and restart Gimp 2.10, the font is available.

@lucyllewy
Copy link
Member

lucyllewy commented May 14, 2018

Does removing the gimp snap and reinstalling, after you've added to font to ~/.local/share/fonts, fix it?

@pieqq
Copy link
Author

pieqq commented May 14, 2018

Yes. After I reinstall GIMP (sudo snap install gimp), the font in ~/.local/share/fonts is available.

@lucyllewy
Copy link
Member

This is a problem with the desktop-helpers and not specific to gimp. The desktop-helpers only recompile the font cache after a refresh of the snap happens. They do it this way to prevent slow launch times beyond the first after the refresh. Rebuilding the fonts every launch would incur a performance penalty.

@pieqq
Copy link
Author

pieqq commented Aug 6, 2018

Thanks for the feedback.

But...

If I manually copy the font from ~/.local/share/fonts to ~/.fonts/ and restart Gimp 2.10, the font is available.

Why does it work with one directory and not the other?

Should I file a bug in the desktop-helpers project?

@anthony-coble
Copy link

@pieqq did you submit this issue to another repo somewhere? I am experiencing this and would like to follow the resolution.

@hadware
Copy link

hadware commented Oct 18, 2019

Experiencing this as well (Gimp 2.10 on ubuntu 18.04)

@astrojuanlu
Copy link

I tested sudo snap remove gimp && sudo snap install gimp and it worked.

@freechelmi
Copy link

Juste a note :

Copying the font to the system-wide dir

/usr/local/share/fonts

makes it available in snap Gimp directly.

We should have a way in gnome font viewer to install it system-wide

@ChemoCosmo
Copy link

Same problem here with GImp 4.10.20 on Ubuntu 18.04.
Only that no solution works: Neither putting the font in ~/.local/share/fonts or ~/fonts nor reinstalling Gimp (via snap) afterwards gives acces to the font (Impact) in Gimp.
Other programs like writer can find and can use the font.

@mapto
Copy link

mapto commented Nov 29, 2020

Had same situation as @ChemoCosmo (on Ubuntu 20.04 and Gimp 2.10.20). Funny thing is that reinstalling Gimp via snap also solved the same problem on Inkscape.

@jabowery
Copy link

# sudo snap remove gimp && sudo snap install gimp
gimp removed
gimp 2.10.28 from Snapcrafters installed

fixed it for me, but I have to wonder why it is I'm getting version 2 while ChemCosmo reports version 4. Did gimp do a version reset and start numbering over or do I have a fault snap installation?

Also, if some folks are doing a snap reinstall but failing to fix the problem the issue seems to remain open.

Finally, a comment on dependencies:

If desktop-helpers takes it upon itself to defer recompilation of fonts until a snap reinstall, then desktop-helpers needs to be integrated into the version updating system so as to notify the user that they need to update gimp and it should notify the moment a new font is installed.

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

9 participants