Bug 208692 - fc-cache abort during upgrade
Summary: fc-cache abort during upgrade
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact:
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-30 09:22 UTC by David Woodhouse
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-04 20:12:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Woodhouse 2006-09-30 09:22:40 UTC
During upgrade FC5->FC6, fc-cache is observed to fail

*** buffer overflow detected ***: /usr/bin/fc-cache terminated

from within sprintf_chk() from unnamed function from FcDirCacheWrite from FcDirSave.

Will install debuginfo and get proper backtrace when the install has finished.

Comment 1 Bug Zapper 2008-04-03 18:22:33 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 2 Behdad Esfahbod 2008-05-04 20:12:46 UTC
Too old a report to be useful.  The bug is most definitely fixed already.


Note You need to log in before you can comment on or make changes to this bug.