Description of problem: After various font rpm churn on rawhide my 32 bit application would crash with a malloc failure because of a messed up font cache. One could wonder: a) why is the 32 bit cache different from the 64 bit? b) why isn't fontconfig keeping them both uptodate? but I have a simpler request: "man fc-cache" states: Note that fc-cache must be executed once per architecture to generate font information customized for that architecture. but it isn't possible to do this on x86_64 because only the 64 bit version of /usr/bin/fc-cache is installed, even if both i386 and x86_64 fontconfig rpms are installed. ** Request that /usr/bin/fc-cache-64 and /usr/bin/fc-cache-32 both be installed, and that a new /usr/bin/fc-cache shell script be created that runs them both. The man page also says: On a subsequent run, fc-cache will augment the cache information files with the information for the new architecture. but apparently this didn't work through some series of font rpm upgrades. Version-Release number of selected component (if applicable): fontconfig-2.6.95-1.git.66.gb162bfb.fc11 How reproducible: 100% Steps to Reproduce: 1. cd /var/cache/fontconfig 2. rm * 3. fc-cache Actual results: Only *x86-64.cache-2 files created Expected results: Both *x86.cache-2 and *x86-64.cache-2 files created Additional info: Any ugly workaround to the current situation is: rpm -e --nodeps --allmatches fontconfig fontconfig-devel yum install fontconfig.i386 fc-cache yum install fontconfig.x86_64 fontconfig-devel.x86_64 fc-cache
I plan to do that. Not sure if for f11.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
I'd very much like to have this reopened and fixed. Just got bitten badly by this. Adobe's Flash plugin failes for me on a x86-64 system. I'd installed nspluginwrapper and flash-plugin as normal, however I could not get the plugin to actually work in Firefox. It just consumed 100% for 10-15 seconds after which npviwer.bin was terminated. Attaching GDB eventually revealed that it was spending almost all its time in fontconfig. It seem nspluginwrapper has some timeout after which t stops the wrapped plugin if it isn't considered to be 'alive'/respond. Without an up to date fontconfig cache the time spend in startup, building the cache info, is longer than this timeout. I guess this could happen for anyone depending on CPU/disk speed or how many fonts are installed. As fc-cache only rebuilds the le64 and not le32d4 cache files they right ones are never present and suggestions found googling does not work.