how do i fix kde font path errors and get proper config files?
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.
how do i fix kde font path errors and get proper config files?
Hi I have largely got my gentoo system working now and Im reasnably happy with it ........I wanted to run 3d games and run aas up to date stuff as possible .......I am using kde-3.5 anyway Im getting some errors about not being able to init font paths and others .......I dont no enough about kde to know what to alter on my own just yet so I submit my error logs to this thread and also my kde config files .....if people can see mistakes in them I would really appreciate it if they could let me no and especially how to get rid of the errors:
My error files
.xsession errors
xset: bad font path element (#118), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
kdecore (KLibLoader): WARNING: KLibrary: /usr/kde/3.5/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd
kio_file: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio_thumbnail: WARNING: KLocale: trying to look up "" in catalog. Fix the program
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x2200005
kio_system: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kde-config: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio_trash: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio (KIOConnection): ERROR: Could not write data
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x400005
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x400005
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x400005
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x400005
Launched ok, pid = 4704
kio_file: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio_thumbnail: WARNING: KLocale: trying to look up "" in catalog. Fix the program
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
# FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/lib/X11/rgb"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the Type1 and FreeType font modules
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
Load "speedo"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
Section "InputDevice"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
# Identifier and driver
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
EndSection
# Access to OpenGL ICD is allowed for all users:
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
Mode 0666
EndSection
# What display manager do you use ? [ xdm | gdm | kdm | entrance ]
DISPLAYMANAGER="kdm"
# XSESSION is a new variable to control what window manager to start
# default with X if run with xdm, startx or xinit. The default behavior
# is to look in /etc/X11/Sessions/ and run the script in matching the
# value that XSESSION is set to. The support scripts are smart enough to
# look in all bin directories if it cant find a match in /etc/X11/Sessions/,
# so setting it to "enlightenment" can also work. This is basically used
# as a way for the system admin to configure a default system wide WM,
# allthough it will work if the user export XSESSION in his .bash_profile, etc.
#
# NOTE: 1) this behaviour is overridden when a ~/.xinitrc exists, and startx
# is called.
# 2) even if ~/.xsession exists, if XSESSION can be resolved, it will
# be executed rather than ~/.xsession, else KDM breaks ...
#
# Defaults depending on what you install currently include:
#
# Gnome - will start gnome-session
# kde-<version> - will start startkde (ex: kde-3.0.2)
# Xsession - will start a terminal and a few other nice apps
XSESSION="kde-3.5"
rc.conf------------------------------------end
any information would be very useful to me as I have just upgraded kde to 3.5 and dont know enough about it :-) especially about the font paths and those other errors ^
Hi redwing26
There's nothing to worry about much in your .xsession-errors file:
Quote:
xset: bad font path element (#118), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
this message appears because the startkde script tries to 'add any user-installed font directories to the X font path' and there is no user fonts in them. You have not added fonts and KDE will work with the X fonts already present since the X server start. See how it works in the startkde script. This is not a real error. You can ignore it.
All the messages with the word 'WARNING' in them are just as the word says warnings not errors. You can also ignore them.
Quote:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x400005
Those are internal "errors" about synchronisation between the X and the QT layers, especially at the closing time of windows. They are without consequences and you can ignore them even if they are annoying.
Quote:
kio (KIOConnection): ERROR: Could not write data
This one may be a problem, but if you don't have any issue when using KDE, it could also be an internal "errors", I don't know for sure for this one.
The .xsession-errors file is rather a log file for KDE than a real errors file (I think it should be named '.kde.log' rather than '.xsession-errors'), like /var/log/messages for the system or /var/log/Xorg.0.log for the X layer. Many messages in them are internal informations, even debugging messages, and don't concern much the user, they rather may be more useful for the developpers.
I hope this may reassure you. What matters is to consider if everything works as you want or not. Do not be too worry about all the messages in the log files. Rather enjoy your well running computer with linux programs you like.
It's just my "wisdom counsel"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.