2

Everything else is OK, but can not display right text on Popup and Menu.

character

Improve this question
0

1 Answer 1

Reset to default
3

This type of problems usually happen when you have invalid permissions on font files. The solution lies in detecting the font file and correcting its permission.

Since, Most of the font files reside in /usr/share/fonts, you can apply a generic fix on them.

First make root the owner of all files and dirs in /usr/share/fonts/

sudo chown -R root:root /usr/share/fonts -v

Then change all folders visitable by fixing permissions on them

find /usr/share/fonts -type d -exec sudo chmod -v 755 {} +

Then use this command to fix permissions on font files.

find /usr/share/fonts -iname '*.[ot]tf' -type f -exec sudo chmod -v 644 {} +

This command lists all files with .ttf and .otf extension and change the permissions of them to 644, required permission bits for fonts.

You can use this command to change all files permissions to 644.

sudo chmod -R a+rX /usr/share/fonts
Improve this answer
5
  • 1
    It might also be useful to assure that all find files are owned by root: sudo chown -R root:root /usr/share/fonts
    – David Foerster
    Nov 2, 2016 at 9:49
  • updated the answer
    – Anwar
    Nov 2, 2016 at 9:57
  • I also noticed that the first find may fail to discover some files if they're inside unreadable or untraversable directories, yet those are only fixed in the second find command.
    – David Foerster
    Nov 2, 2016 at 10:05
  • @DavidFoerster I had same suspicion, but In my test, with sudo order doesn't matter
    – Anwar
    Nov 2, 2016 at 10:06
  • find doesn't run with super-user privileges the way you wrote it so it couldn't find files inside directories without read and traversal permissions for the executing user. While chmod runs with super-user privileges it only acts on the files provided by find.
    – David Foerster
    Nov 2, 2016 at 10:16

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .