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

[Pkg-fonts-devel] Bug#717620: marked as done (fonts-droid: Many applications giving droid-sans-font error)

Your message dated Tue, 20 Aug 2013 10:59:24 +0900
with message-id <20130820015924.GA31090@aqwa.igloo>
and subject line Re: Bug#717620: fonts-droid: Many applications giving droid-sans-font error
has caused the Debian Bug report #717620,
regarding fonts-droid: Many applications giving droid-sans-font error
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.)


-- 
717620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717620
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: fonts-droid
Version: 20111207+git-1
Severity: normal

Dear Maintainer,

After recent upgrade, I get this kind of error:

------------------------
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103:
Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138:
Having multiple values in <test> isn't supported and may not work as expected
Traceback (most recent call last):
  File "/usr/sbin/update-apt-xapian-index", line 97, in <module>
    if not indexer.setupIndexing(force=opts.force, system=opts.pkgfile is
None):
  File "/usr/lib/pymodules/python2.7/axi/indexer.py", line 518, in
setupIndexing
    addon.obj.init(dict(values=self.values), self.progress)
  File "/usr/share/apt-xapian-index/plugins/app-install.py", line 142, in init
    entry = DesktopEntry(os.path.join(APPINSTALLDIR, f))
  File "/usr/lib/python2.7/dist-packages/xdg/DesktopEntry.py", line 33, in
__init__
    self.parse(filename)
  File "/usr/lib/python2.7/dist-packages/xdg/DesktopEntry.py", line 42, in
parse
    IniFile.parse(self, file, ["Desktop Entry", "KDE Desktop Entry"])
  File "/usr/lib/python2.7/dist-packages/xdg/IniFile.py", line 81, in parse
    raise ParsingError("Invalid line: " + line, filename)
xdg.Exceptions.ParsingError: ParsingError in file '/usr/share/app-
install/desktop/spout.desktop', Invalid line:
Categories:Application:Game:ArcadeGame
-------------------

It happens with emacs, synaptic, reportbug...



-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  fontconfig     2.10.2-2     i386         generic font configuration librar
ii  libfreetype6:i 2.4.9-1.1    i386         FreeType 2 font engine, shared li
ii  libxft2:i386   2.3.1-1      i386         FreeType-based font drawing libra

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version:1:4.2.r1-1

Le Tue, Jul 23, 2013 at 08:08:43AM +0530, Rustom Mody a écrit :
> Package: fonts-droid
> Version: 20111207+git-1
> Severity: normal
> 
> Dear Maintainer,
> 
> After recent upgrade, I get this kind of error:
> 
> ------------------------
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103:
> Having multiple values in <test> isn't supported and may not work as expected
> Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138:

Dear Rustom,

I am not the maintainer, but I see that this problem (already reported as
http://bugs.debian.org/686685) has been solved in version 1:4.2.r1-1, so I am
closing this bug accordingly.

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan

--- End Message ---
Reply to: