Issue metadata
Sign in to add a comment
|
ignores system antialiasing settings: it's disabled, but chromium performs antialiasing
Reported by
chromo...@gmail.com,
Sep 12
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/69.0.3497.81 Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. set system setting for anti-aliasing to "none" 2. also, set anti-aliasing setting in ~/.fonts.conf to "none" 3. run chromium What is the expected behavior? chromium should display "ugly" pixelized fonts (this is my preference, because then my eyes get distinct image, I don't like smoothed image -- it looks like as if my sight degrades) What went wrong? chromium smoothes fonts everywhere Did this work before? Yes previous version, before latest update: Version 68.0.3440.106 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit) Chrome version: 69.0.3497.81 Channel: stable OS Version: Ubuntu 18.04.1 LTS 64-bit Flash Version: Using PPAPI flash. some time before, chromium already ignored system settings, but it has never ignored ~/.fonts.conf setting, now did
,
Sep 12
,
Sep 14
,
Sep 14
btw, it worth mentioning imo: the bug has reproduced on both my machines -- these are completely different computers (notebook and desktop) running the same version of ubuntu and almost same set of extensions and other software. the bug has reproduced almost at the same time -- when the update of chromium has installed on it. me myself, i did nothing relevant at that time that could produce the bug, it is definitely caused by an update
,
Sep 14
Tried testing the issue on chrome reported version# 69.0.3497.81 using Ubuntu 14.04 with steps mentioned below: 1) Changed Antialiasing setting to "None"( find attached Tweaks screenshot) 2) Launched chrome version# 68.0.3440.0 and navigated to Chrome://Settings/help and observed the behavior of fonts 3) Again launched chrome version# 69.0.3497.0 and navigated to Chrome://Settings/help, seen same behavior of fonts as compared with step-2 @Reporter: Please find the above steps and attached screenshots for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which helps us in further triaging it in better way and let us know if this issue is specific to Ubuntu 18.04. Thanks!
,
Sep 14
> let us know if we missed anything in reproducing the issue yes, you did miss something > before, chromium already ignored system settings, > but it has never ignored ~/.fonts.conf setting, now did as i said, chromium already ignored system setting (that's a pity but this is an old bug, and therefore this is NOT a regression) but chromium didn't ignore ~/.fonts.conf directive, but now it did (and this actually IS a regression) you did miss reproducing step 2: > 2. also, set anti-aliasing setting in ~/.fonts.conf to "none" > here's how I disable antialiasing: > .fonts.conf > 593 bytes Download please download this .fonts.conf file and put it to your ubuntu user home directory "~" with chromium v68 it should make chromium disable antialiasing, with v69 -- id doesn't -- exactly THIS is a regression
,
Sep 14
the file should be ~/.fonts.conf, note the period in the beginning of the filename
,
Sep 14
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 15
i've just checked it on ubuntu 14.04.5 64-bit live usb -- the bug doesn't reproduces. i. e. both chromium v68 and v69 do not respect system setting but both of them do respect ~/.fonts.conf and disable antialiasing but i checked on other builds (because i don't know how to install exactly the same builds on a clean live usb): Version 69.0.3497.0 (Developer Build) (64-bit) https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/576753/ Version 68.0.3440.0 (Developer Build) (64-bit) https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/561732/ screenshots below
,
Sep 15
i've just checked it on a fresh ubuntu 18.04.1 lts 64-bit live usb -- just to be sure it has nothing to do with my specific soft installed on my computers -- the bug reproduced as described: both v68 and v69 ignore system setting, but only v69 ingnores .fonts.conf -- v68 respects it tested on same builds as in previous comment screenshots below
,
Sep 17
As per your comment #9 and comment #10, this issue seems to be fixed in Ubuntu 14.04 and issue specific to ubuntu 18.04.1 lts 64-bit live usb. Hence requesting some one from MTV team to look in to it and adding TE-NeedsTriageFromMTV label to it. Thanks..!
,
Sep 22
btw, on ubuntu 16.04.5 lts live usb 64-bit the bug reproduces also -- i've just checked. > let us know if this issue is specific to Ubuntu 18.04. > this issue seems to be fixed in Ubuntu 14.04 and > issue specific to ubuntu 18.04.1 lts 64-bit live usb so, this issue definitely is NOT specific to ubuntu 18.04, it also reproduces on ubuntu 16.04 lts screenshots attached below
,
Sep 22
*mistype: "the bug reproduces -also- _too_"
,
Sep 24
,
Sep 25
ligim...@chromium.org , i've checked it on 6 different computers: 4 desktops, 1 notebook and 1 netbook, of different manufacturing date and different companies. (i used same ubuntu 16.04.5 lts 64-bit live usb). On all of them the bug reproduces (i've made screenshots, but they're same as previous, nothing new, so i think there's no need to post them here, right? (i could though)). If it is a hardware problem, then all these 6 computers got this same problem exactly after recent chromium update. I hope my tests will help chromium developers fix this hardware problem (or whatever it is) to make chromium work again like it did recently. It'd be very disappointing to me if chromium will drop support of this feature on ubuntu. :( i understand though -- nothing personal, it's just business -- money should make money, ubuntu is less popular than other OSes
,
Sep 28
interesting thing is that the same version of Chrome (not Chromium) works fine, the bug doesn't reproduce. i. e. chrome somehow manages to respect .fonts.conf while chromium (on which chrome is based on) cannot do this. how can this be possible? i've tested on Version 69.0.3497.100 (Official Build) (64-bit) on ubuntu 18.04.1 lts 64-bit, screenshot below
,
Nov 19
***Mass UI Triage*** Thanks for the update!Marking the issue as Won't Fix as per comment#16. Please feel free to raise a new issue if reproduce the issue. Thank You. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chromo...@gmail.com
, Sep 1216.8 KB
16.8 KB View Download
593 bytes
593 bytes Download