Red Hat Bugzilla – Bug 176608
sylpheed-claws (FE) segfaults in libpangoft2-1.0.so.0
Last modified: 2007-11-30 17:11:19 EST
Description of problem:
When starting up sylpheed-claws (from extras), s-c segfaults almost immediately
in libpangoft2. gdb output attached.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start sylpheed-claws
Created attachment 122596 [details]
gdb session log
xchat goes down at exactly the same point
Looks like some font problem to me. What locale is this in ?
Do you have any strange fonts installed.
This is in en_US.UTF-8.
I have done some more digging on this and have come up with the following:
a) It has nothing do do with my user-font-config (I moved my locally installed
fonts and .fonts.conf aside and it still happens)
b) It has something to do with the "Fixed" font. I can persuade any gnome
program (including gnome-font-properties) which displays a font selection dialog
to crash by just clicking "Fixed" in the "Family" list.
c) 'fc-match "Fixed"' yields 'kaname-latin1.pcf.gz: "Fixed" "Regular"', which
seems to be owned by fonts-japanese-0.20050222-11.1. The files on the disk
verify against the RPM database.
d) removing fonts-japanese makes selecting "Fixed" safe again, and
sylpheed-claws does not crash any more. 'fc-match "Fixed"' now yields
'console9x15.pcf: "Fixed" "Regular"'. The font is ugly, btw :)
e) reinstall fonts-japanese, and everything goes south as soon as Fixed turns up.
I noticed yesterday that another font (from fonts-korean) showed the same
behaviour. I then hunted down all fontconfig cache files on the system
(fonts.cache-1, fonts.cache-2, /var/cache/fontconfig), deleted them and reran
fc-cache. Since then all fonts (including Fixed with fonts-japanese) seem to
Why does fc have to use different cache files for every other release?