package ttf-opensymbol 1:2.3.0~rc1-1ubuntu2 failed to install/upgrade:

Bug #144771 reported by Michael Vogt
10
Affects Status Importance Assigned to Milestone
fontconfig (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

Postinst failed during a test feisty->gutsy upgrade.

ProblemType: Package
Architecture: amd64
Date: Thu Sep 20 20:37:01 2007
Dependencies:

DistroRelease: Ubuntu 7.10
ErrorMessage:
 ErrorMessage: Unterprozess post-installation script gab den Fehlerwert 15 zurück
Package: ttf-opensymbol 1:2.3.0~rc1-1ubuntu2
PackageArchitecture: all
SourcePackage: openoffice.org
Title: package ttf-opensymbol 1:2.3.0~rc1-1ubuntu2 failed to install/upgrade:
Uname: Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux

Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Here is the error (ttf-opensymbol postinst):

Richte ttf-opensymbol ein (1:2.3.0~rc1-1ubuntu2) ...
Updating fontconfig cache...
/usr/share/fonts: failed to write cache
/usr/share/fonts/X11: failed to write cache
/usr/share/fonts/X11/100dpi: failed to write cache
/usr/share/fonts/X11/75dpi: failed to write cache
/usr/share/fonts/X11/Type1: failed to write cache
/usr/share/fonts/X11/misc: failed to write cache
/usr/share/fonts/X11/util: failed to write cache
/usr/share/fonts/truetype/baekmuk: failed to write cache
/usr/share/fonts/truetype/kochi: failed to write cache
/usr/share/fonts/truetype/ttf-bitstream-vera: failed to write cache
/usr/share/fonts/truetype/ttf-gentium: failed to write cache
/usr/share/fonts/truetype/ttf-lao: failed to write cache
/usr/share/fonts/truetype/ttf-mgopen: failed to write cache
/usr/share/fonts/type1: failed to write cache
/usr/local/share/fonts: failed to write cache

Revision history for this message
Matthias Klose (doko) wrote : Re: [Bug 144771] Re: package ttf-opensymbol 1:2.3.0~rc1-1ubuntu2 failed to install/upgrade:

Michael Vogt schrieb:
> Here is the error (ttf-opensymbol postinst):
>
> Richte ttf-opensymbol ein (1:2.3.0~rc1-1ubuntu2) ...
> Updating fontconfig cache...
> /usr/share/fonts: failed to write cache
> /usr/share/fonts/X11: failed to write cache
> /usr/share/fonts/X11/100dpi: failed to write cache
> /usr/share/fonts/X11/75dpi: failed to write cache
> /usr/share/fonts/X11/Type1: failed to write cache
> /usr/share/fonts/X11/misc: failed to write cache
> /usr/share/fonts/X11/util: failed to write cache
> /usr/share/fonts/truetype/baekmuk: failed to write cache
> /usr/share/fonts/truetype/kochi: failed to write cache
> /usr/share/fonts/truetype/ttf-bitstream-vera: failed to write cache
> /usr/share/fonts/truetype/ttf-gentium: failed to write cache
> /usr/share/fonts/truetype/ttf-lao: failed to write cache
> /usr/share/fonts/truetype/ttf-mgopen: failed to write cache
> /usr/share/fonts/type1: failed to write cache
> /usr/local/share/fonts: failed to write cache
>

this seems to be unrelated to ttf-opensymbol

Revision history for this message
Michael Vogt (mvo) wrote :

It looks like this is time releated (the cock on the test-system was not setup correctly).

Revision history for this message
Chris Cheney (ccheney) wrote :

This appears to be a bug in fontconfig fc-cache if it is considered to be a bug at all. I am not sure why fc-cache would 'failed to write cache' though. However, it may be related to the fact that the clock was set wrong on the system installing the packages.

Chris

Revision history for this message
Steve Langasek (vorlon) wrote :
Revision history for this message
Matti Lindell (mlind) wrote :

This is a duplicate of Bug #104553 and it's happening with feisty --> gutsy upgrades now.

Revision history for this message
orj (orjeda) wrote :

fontconfig crashes during dist-upgrade today.

Revision history for this message
Janne P. (jp-jannol) wrote :

sudo apt-get install locales
from a terminal window seems to solve it

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.