Your message dated Sun, 12 Apr 2020 19:45:15 +0900
with message-id 
<CAEQ9gEm10Dk5m8snDQW56pSQ4PnJy4T42bQpJyB-bJ=ydbj...@mail.gmail.com>
and subject line Re: [Pkg-privacy-maintainers] Bug#909369: torbrowser-launcher: 
fontconfig in torbrowser-launcher complains about blank element
has caused the Debian Bug report #909369,
regarding torbrowser-launcher: fontconfig in torbrowser-launcher complains 
about blank element
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 [email protected]
immediately.)


-- 
909369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909369
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.9-5
Severity: normal

Dear Maintainer,

I was looking at torbrowser in verbose mode and came across the
following statement -

Fontconfig warning:
"/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf",
line 85: unknown element "blank"

I looked at fonts.conf and sure enough on line 85

<!--
  These are the default Unicode chars that are expected to be blank
  in fonts.  All other blank chars are assumed to be broken and
  won't appear in the resulting charsets
 -->
                <blank>

I do not know whether it's an issue in fontconfig that is in debian or
an issue with the fonts.conf itself.

Please look into the same.

I also have no idea why the python packages are broken, probably
because everything is shifting to python3 .

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (100,
'unstable-debug'), (100, 'experimental-debug'), (100, 'experimental'),
(100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg             2.2.10-1
ii  libdbus-glib-1-2  0.110-3
ii  python            2.7.15-3
pn  python-gtk2       <none>
pn  python-lzma       <none>
pn  python-parsley    <none>
pn  python-psutil     <none>
pn  python-twisted    <none>
pn  python-txsocksx   <none>

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.4.8-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor       2.13-8
pn  python-pygame  <none>

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

--- End Message ---
--- Begin Message ---
control: tags -1 +upstream +wontfix
control: forwarded -1 https://trac.torproject.org/projects/tor/ticket/22787

On Sun, Sep 23, 2018 at 1:36 AM shirish शिरीष <[email protected]> wrote:
>
> I was looking at torbrowser in verbose mode and came across the
> following statement -
>
> Fontconfig warning:
> "/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf",
> line 85: unknown element "blank"

Thanks for your reporting!
However, this package is just a download & launch script.
The actually bug of the code comes from upstream, and there was
already a ticket upstream:
- https://trac.torproject.org/projects/tor/ticket/22787

I also find some related thread about this fontconfig issue:
- 
https://unix.stackexchange.com/questions/504335/fontconfig-warning-etc-fonts-fonts-conf-line-100-unknown-element-blank
- https://github.com/electron/electron/issues/15625

So I close this ticket as wontfix.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

--- End Message ---

Reply via email to