severity 387928 important
thanks
The only way I am able to reproduce this bug is if I have a fonts.conf
without a cache directive, and the only way I am able to get a
fonts.conf without a cache directive is by modifying this conffile and
then disallowing dpkg to update the conffile on upgrade.
Th
I do not believe this is still a problem. Probably can close unless someone
had this happen again!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
* Keith Packard ([EMAIL PROTECTED]) [061010 03:18]:
> On Mon, 2006-10-09 at 19:43 +0200, Andreas Barth wrote:
>
> > If fonts.conf is changed, the user is asked via debconf if the file can
> > be overwritten. So, the only issue is if (the file is changed) and (the
> > user denies overwritting it).
On Mon, 2006-10-09 at 19:43 +0200, Andreas Barth wrote:
> If fonts.conf is changed, the user is asked via debconf if the file can
> be overwritten. So, the only issue is if (the file is changed) and (the
> user denies overwritting it).
Note that there was a transient bug in one of the 2.4.0 versi
* Ross Boylan ([EMAIL PROTECTED]) [061009 18:22]:
> > Hi David,
> > * Keith Packard ([EMAIL PROTECTED]) [060917 15:17]:
> > > This problem stems from user-modified fonts.conf files which renders
> > > fontconfig unable to replace it with the new version that includes the
> > > necessary elements.
On Mon, Oct 09, 2006 at 01:22:21PM +0200, Andreas Barth wrote:
> clone 387928
> reassign -1 release-notes
> severity -1 normal
> retitle -1 user-modified fonts.conf-files needs to be overwritten
> submitter -1 [EMAIL PROTECTED]
> tags 387928 + moreinfo
> severity 387928 important
> thanks
>
> Hi D
clone 387928
reassign -1 release-notes
severity -1 normal
retitle -1 user-modified fonts.conf-files needs to be overwritten
submitter -1 [EMAIL PROTECTED]
tags 387928 + moreinfo
severity 387928 important
thanks
Hi David,
* Keith Packard ([EMAIL PROTECTED]) [060917 15:17]:
> This problem stems fro
I'm not sure after all that the lilypond failures were the same bug.
They are a different bug: that fontconfig doesn't reliably work right
if $HOME doesn't exist.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, 2006-09-17 at 17:23 +0300, David Baron wrote:
> Package: fontconfig
> Version: 2.4.1-1
> Severity: grave
> Justification: renders package unusable
>
> Recent Sid versions cannot write font caches.
> Will report scanning of # directories, # fonts in log or using -v option,
> but will not wr
Package: fontconfig
Version: 2.4.1-1
Severity: grave
Justification: renders package unusable
Recent Sid versions cannot write font caches.
Will report scanning of # directories, # fonts in log or using -v option,
but will not write caches. This renders X very slow (such a bug reported)
and KDE and
10 matches
Mail list logo
