Sponsored Content
Operating Systems Linux Fedora Fedora 30 and Slackware 14.2, how to obtain the same rendering? Post 303036843 by Neo on Saturday 13th of July 2019 11:09:24 PM
Old 07-14-2019
Did you check the permissions of the font files to make sure the userids have permissions to access them?

I guess you have already checked all file ownership and permissions.

So then as the required user, you can run the command to list all the available fonts

I assume you did that already?

Edit: Sorry heading to the airport. Maybe someone else can help you.....

Cheers
 

6 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Unix GUI rendering

Does anyone know why Fonts and most Graphics in KDE and Gnome are rendered rather badly. There are some text editors in KDE where the font is just horrible as far as legible. Any links or knowledge on this topic would be grealy appreciated. A Huge Unix/Linux Fan Gregg (2 Replies)
Discussion started by: gdboling
2 Replies

2. Linux

Dual Boot Win XP And Fedora with Fedora Installed First

Hi everyone, I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies

3. UNIX for Advanced & Expert Users

Exceed and offscreen rendering

Hi everyone. I made a program which renders a 3D scene into a pbuffer/pixmap (if pbuffer aren't supported) in order to export it to a postscript file. On a RHEL4 (32/64 bits) or whatever distribution may be, it works just fine. I'm using Exceed when I'm working under WinXP and each time I run my... (0 Replies)
Discussion started by: JB007ROLV
0 Replies

4. Red Hat

Fedora temporarily obtain root previlages

Hii friends!! i am quite a bit dealing with linux stuff i worked mostly on macosx unix side i created a user phoenix during installation of fedora 14 now after installation i want some rights to do a task i usually use sudo to elevate to do a operation; i did the same here but its going on... (3 Replies)
Discussion started by: phoenix_nebula
3 Replies

5. Red Hat

fedora grub help, moving to tri boot (XP, ubuntu, fedora soemething)

I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies

6. Red Hat

XCB crash while Video Rendering in multithreded application

I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0 Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
INNCHECK(8)						      System Manager's Manual						       INNCHECK(8)

NAME
inncheck - check inn configuration and database files. SYNOPSIS
inncheck [ -a ] [ -v ] [ -pedantic ] [ -f ] [ -perm ] [ -noperm ] [ file=value | file ] DESCRIPTION
Inncheck examines various configuration files and databases and verifies things about them. Things verified depend on the file being checked, but generally are things like permissions, ownership, syntax errors in config files, etc. Inncheck does not make changes to any files -- it just reports what it thinks may be wrong, and it is up to the operator to fix the prob- lem. The set of files checked may be restricted by using file or file=value arguments. For example, putting incoming.conf causes only the incom- ing.conf file to be checked. Using incoming.conf=/tmp/incoming.conf on the command line will cause inncheck to only verify the incom- ing.conf file, and it will perform the checks on the file /tmp/incoming.conf file instead of the default one. Valid values for file are: active control.ctl expire.ctl incoming.conf inn.conf moderators newsfeeds nntpsend.ctl passwd.nntp readers.conf OPTIONS
-a If any ``file'' value or ``file=value'' pairs (see below) are given, then normally only the files they refer to are checked. Use the ``-a'' flag to specify that all files should be checked regardless. In this case the form file=value will be the more useful. -v Use the ``-v'' option to get more verbose output. -pedantic Use the ``-pedantic'' option to get reports on things that are not necessarily wrong, but may indicate a bad configuration -- such as inn.conf missing a key. -f Use the ``-f'' flag to have inncheck print the appropriate chown/chgrp/chmod command necessary to fix a problem that it reports. Any other output lines will be prefixed with a ``#'' character to make the output be valid input for a shell. Note that the ``-perm'' flag must be used as well when using this flag. -perm Inncheck checks all files for permission problems. If the ``-perm'' flag is used, then only the files specified by the file or file=value command line arguments will be checked for problems other than permission problems. -noperm To avoid doing any checking of file permissions or ownership, use the ``-noperm'' option. EXAMPLES
To have inncheck check all files for syntax and permission problems simply: inncheck To have inncheck check all files for permission problems and to verify the syntax of the active and incoming.conf files do: inncheck -perm active incoming.conf To fix the permissions problems noted in the output of the above command, modify it as follow: inncheck -f -perm | sh To have inncheck check the test newsfeeds file in /var/tmp/newsfeeds.testing, do: inncheck newsfeeds=/var/tmp/newsfeeds.testing To have inncheck check all the files as it normally does, but to specify a different location for the newsfeeds file, so: inncheck -a newsfeeds=/var/tmp/newsfeeds.testing BUGS
If the ``-f'' and ``-perm'' options are used together, along with ``-a'' or some ``file'' or ``file=value'' arguments that refer to a file with a syntax problem, then the output will no longer be valid input for a shell. HISTORY
Written by Brendan Kehoe <brendan@cygnus.com> and Rich Salz <rsalz@uunet.uu.net> This is revision 8409, dated 2009-04-11. SEE ALSO
active(5), expire.ctl(5), history(5), incoming.conf(5), inn.conf(5), newsfeeds(5) INNCHECK(8)
All times are GMT -4. The time now is 01:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy