Your message dated Sat, 8 May 2021 13:14:32 -0400
with message-id
<CANTw=moi4maual0+icqgzenfezjpg7gbxhhgexersne52ki...@mail.gmail.com>
and subject line Re: Bug#980945: chromium: Text displayed without subpixel
antialiasing
has caused the Debian Bug report #980945,
regarding chromium: Text displayed without subpixel antialiasing
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 ow...@bugs.debian.org
immediately.)
--
980945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 88.0.4324.96-0.1
Severity: normal
X-Debbugs-Cc: bren...@quantumfurball.net
Dear Maintainer,
On my systems, Chromium draws text with only grayscale antialiasing, and does
not use any subpixel (LCD, RGB) antialiasing. I actually found this trying to
determine why programs using Qt WebEngine (based on Chromium, as I understand)
were not showing subpixel antialiasing in certain content - the common element
seems to be something somewhere inside Chromium. The difference between
subpixel and grayscale antialiasing can be seen easily with magnifier programs
like kmag. Other programs (aside from where some use WebEngine) on my system
don't have this issue.
I got the portable binary of ungoogled-chromium 87 from the Chromium website
for comparison, and found that it does employ subpixel antialiasing. So that
seems to rule out some bug in the upstream code itself. I guess it's something
in the way both the Chromium package and the Qt WebEngine package are built, or
in common dependencies which that portable binary provided built-in. I haven't
noticed anything clearly pointing to a dependency being at issue, though, and
I'm out of ideas.
Peace,
Brendon
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (990, 'testing-debug'), (990, 'testing'), (500,
'unstable-debug'), (500, 'unstable'), (100, 'experimental-debug'), (100,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-1-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 88.0.4324.96-0.1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-2
ii libavcodec58 7:4.3.1-6
ii libavformat58 7:4.3.1-6
ii libavutil56 7:4.3.1-6
ii libc6 2.31-9
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op1-7
ii libdbus-1-3 1.12.20-1
ii libdrm2 2.4.103-2
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-1
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.2-1
ii libgcc-s1 10.2.1-6
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.66.4-1
ii libgtk-3-0 3.24.24-1
ii libharfbuzz0b 2.6.7-1
ii libicu67 67.1-6
ii libjpeg62-turbo 1:2.0.5-2
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.60-1
ii libopenjp2-7 2.3.1-1
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.1-1
ii libre2-9 20201101+dfsg-2
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp6 0.6.1-2+b1
ii libwebpdemux2 0.6.1-2+b1
ii libwebpmux3 0.6.1-2+b1
ii libx11-6 2:1.7.0-2
ii libxcb1 1.14-2.1
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxml2 2.9.10+dfsg-6.3+b1
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 88.0.4324.96-0.1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-9
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.0-2
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-2
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 88.0.4324.96-0.1
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 20.3.2-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii plasma-workspace [notification-daemon] 4:5.20.5-2
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-9
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Jan 24, 2021 at 1:48 PM Brendon Higgins wrote:
> On my systems, Chromium draws text with only grayscale antialiasing, and does
> not use any subpixel (LCD, RGB) antialiasing.
Harfbuzz's public API does not expose subpixel options, so this is
currently disabled in the debian package. The system harfbuzz shared
library is used, which does not expose private interfaces that the
upstream chromium currently uses.
Best wishes,
Mike
--- End Message ---
