[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240674: marked as done (xfonts-scalable: postinst gripes 'fontconfig error: cannot load default config file')

Your message dated Thu, 25 Jun 2009 15:19:52 +0200
with message-id <20090625131952.GA19778@patate.is-a-geek.org>
and subject line Re: Bug#240674: xfonts-scalable: postinst error: cannot load default config file
has caused the Debian Bug report #240674,
regarding xfonts-scalable: postinst gripes 'fontconfig error: cannot load default config file'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
240674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=240674
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xfonts-scalable
Version: 4.3.0-7
Severity: normal

During installation the following error was shown:
Setting up xfonts-scalable (4.3.0-7) ...
fontconfig error: cannot load default config file
fontconfig error: cannot load default config file

This was during X Window System and KDE installation after a debian-installer test.
All other xfont files installed without problems.

The error is not shown if I now do 'apt-get install --reinstall xfonts-scalable'

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-1-686
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15

Versions of packages xfonts-scalable depends on:
ii  xutils                        4.3.0-7    X Window System utility programs

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, Apr  2, 2009 at 20:00:50 +0200, Petter Reinholdtsen wrote:

> I suspect this issue was really bug #422980, and that it is solved now.
> 
Thanks for the pointer, closing.

Cheers,
Julien

--- End Message ---
Reply to: