[SOLVED] Having difficulty installing (and understanding) fonts
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On the surface one would expect it to ensure that ~/.fonts and all it contains belongs to owner gregory and group gregory. But, take a look in ~/.fonts with MC and see. An ordinary user doesn't have power to wrest ownership from root.
Case matters in FOSS commands and filesystems. Don't trust your memory. Do 'fc-cache --help' or 'man fc-cache' to see -r and -R are quite different. Take a look at 'chown --help' and/or 'man chown' as well.
It did not. One of the reasons for the #27 exercise was to present an opportunity to discover so. fc-cache updates the fontconfig cache, not the content of ~/.fonts. If ownership of the content of ~/.fonts was or is bad, it's not because of running fc-cache.
True.
In fact? Or, is that just something you think happened?
Look around in MC some more. I doubt anything in ~ is wrong on account of anything I've read in this thread, but if there is, MC in long listing mode, as would 'ls -al | less', should make bad ownerships readily apparent.
Thanks for the great post, teach. I will go over this tomorrow night (I have to talk to a friend who had a big medical test--I just wanted to check in) and explore MC for the answers to the issue here. I am a little confused in the macro though--in that there's nothing to worry about. Was there nothing to post 15 and the "weirdest errors" that might creep into the fonts? (And remember, I'm a writer!) Appreciate the help.
Was there nothing to post 15 and the "weirdest errors" that might creep into the fonts?
Only in that sudo has the potential to cause permissions trouble that can be difficult for those who don't understand permissions to diagnose. IMO that potential is entirely inapplicable in the context of fc-cache.
Only in that sudo has the potential to cause permissions trouble that can be difficult for those who don't understand permissions to diagnose. IMO that potential is entirely inapplicable in the context of fc-cache.
Quote:
Only in that sudo has the potential to cause permissions trouble that can be difficult for those who don't understand permissions to diagnose.
Uh, that would be me!
Hi mrmazda. I just got done going through MC again. I did the two exercises. In the first exercise all the owners and groups are 'gregory.' So no 'root' there.
And in the Chown window in MC (via exercise #2) the "User name" highlighted was 'gregory' and the "Group name" was also higlighted on 'gregory.'
So...no need for the command suggested in post #22 (or any other post)? Are the crops saved? (Were the crops never in danger?) Thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.