I ran into some weird problems myself when I recompiled & installed
freetype 2.1.7 with enabled bytecode interpreter. In my case, KDM/GDM
will always crash. Only XDM will work.
I do not know what is the root cause of this problem but I did manage
to fix the problem. I had installed 2.1.7 from the sources I got from
http://www.freetype.org/. Now, it turns out that SuSE does not like
this. So, I had to get the 2.1.7 source rpm that my suse 9.1 came
with, extract the sources from this source rpm, modify the sources to
reenable bytecode interprefer and then build the source rpm and
install it. This worked fine and my problems went away.
What I think is the root cause is that the font-config and freetype
supplied with suse are "tweaked" to go with each other. An easy way to
check is to do
fc-list
and make sure that it does not crash and gives you a list of fonts.
Osho
On Thu, 4 Nov 2004 10:15:59 +0100, Robert Graf-Waczenski
Hi folks!
Yesterday, i once again tweaked on the font installations on my Kernel 2.4.20 / SuSE 8.2 box running a recently upgraded KDE 3.3
I did four things:
1.) As root, recompiled & installed freetype 2.1.4 with enabled bytecode interpreter 2.) As root, mounted my windows partition 3.) As non-root, added *all* my windows fonts to OpenOffice by using "spadmin" and accessing the windows partition 4.) As non-root, using the KDE font installer, removed all user-specific fonts and then also added all windows fonts. (There are 250+ of them, this took some time but seemed to work ok)
Now the following happened (and is reproducible since then): I'm able to log in to KDE as root without unusual problems. But when trying to log in as the non-root user i was using in 3) and 4) above, the X server does start but *no* KDE splash screen appears. The disk is busy for a few minutes, still no splash screen. After a few seconds more, i become impatient and kill the X server and re-login as root, which works ok again.
So, effectively, my non-root account is unusable now.
Some initial ideas:
- I was running freetype with the enabled bytecode interpreter some time already but did not re-supply the fonts. Since the fonts still looked rather blurry and sub-optimal, i figured that i might have to remove and re-add them, which is what i did yesterday.
- Normally, my windows partition is *not* mounted. I will try to unmount it again this evening and see what happens.
- Before yesterday, i also never used the "spadmin" tool from OpenOffice, maybe this thingy freaked something up.
Can anybody give me a hint as to what of the steps above may have caused the problem or what else i can do to make my account usable again? (I don't want to wipe the system, of course...)
Thanks in advance,
Robert
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
-- Osho