Bug 85990

Summary:	Crash of font installer
Product:	kcontrol	Reporter:	mauro.sacchetto
Component:	kcmfontinst	Assignee:	Craig Drummond <craig>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:

Description mauro.sacchetto 2004-07-26 05:54:31 UTC

Version:            (using KDE KDE 3.2.3)
Installed from:    Slackware Packages
OS:                Linux

After I added for the first time some ttf and type 1 fonts
(fonts regularly added), I'm no more able to open font installer.
If I try to open it, I receive this error message:

"There was an error loading the module.
The diagnostics is:
Library files for "libkcm_fontinst.la" not found in paths
Possible reasons:
An error occurred during your last KDE upgrade leaving an orphaned control 
module
You have old third party modules lying around.
Check these points carefully and try to remove the module mentioned in the 
error message. If this fails, consider contacting your distributor or 
packager.

But I didn't upgrade KDE (in Slack 10.0
3.2.3 is the original version),
and there is no so called module (libkcm_fontinst.la)


Thanx
M. S.

Comment 1 Craig Drummond 2004-07-28 17:04:05 UTC

This would seem to be an installtion issue.

Can you find the "fontinst" libaraires in your KDE path? e.g. 

    find /opt/kde3/lib -name \*fontinst\*

???

What happens if you type "kcmshell kcmfontinst" from a konsole window?

Comment 2 mauro.sacchetto 2004-08-01 02:43:24 UTC

When I give that command, I receive a message
about the imporssibility to create an "io-slave".
Error in loading kio-fonts".
So: is it a problem in KDE
or there is something wrong
in Slack 10?
Thanx
M.

Comment 3 mauro.sacchetto 2004-08-01 03:11:10 UTC

Referring to your first question:
I find those libraries:
/opt/kde/lib/kde3/kcm_fontinst.la
/opt/kde/lib/kde3/kcm_fontinst.so
But where I can add it?
In which file, I mean?


Thanx
M.

Comment 4 Craig Drummond 2004-10-19 16:33:12 UTC

Have you solved your problem? Did you ever upgrade FreeType from 2.1.7 (or less) to 2.1.8 (or newer)? There were some binary incompatible changes - and it could be that these are affecting you. If you upgraded FreeType, then kfontinst needs to be reompiled. Anyway, this is more an installation issue, so I'm gonna close this report. Contact me if you need further assistance.