fonts-bugs December 2018

fonts-bugs@lists.fedoraproject.org

1 participants
38 discussions

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 12 Dec '18

12 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 --- Comment #13 from Akira TAGOH <tagoh(a)redhat.com> --- Exactly. this is a known issue and this happens because fonts are mmap'ed to open. if fonts has drastic changes, the location where tables points to are also changed. so unexpected behavior comes. my bad that I didn't add a flag to suggest logout. updated on bodhi that way. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 12 Dec '18

12 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 --- Comment #12 from Jens Petersen <petersen(a)redhat.com> --- (In reply to Nerijus Baliūnas from comment #6) > https://www.miestai.net/forumas/forum/kitos-diskusijos/visuomen%C4%97-ir- > %C5%ABkis/17938-xii-seimas-ir-xvii-vyriausyb%C4%97-po-2016- > rinkim%C5%B3?p=1688026#post1688026 Yes renders fine for me with google-noto-sans-fonts-20170919-2.fc29. I think it is a known issue that live updating fonts (with significant changes) may cause text rendering corruption particularly in browsers (maybe something could be done in FreeType(?) to address this, but surely non-trivial). This type of problem is a reason that gnome-software and Silvertree, etc require reboots for updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1645763] ClearType enablement: strong color fringing that is not present in vanilla build from freetype git
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1645763 --- Comment #39 from Christian Stadelmann <fedora(a)genodeftest.de> --- Created attachment 1513551 --> https://bugzilla.redhat.com/attachment.cgi?id=1513551&action=edit A screenshot of nautilus running in a GNOME/Wayland session on Fedora 29 (In reply to Marek Kašík from comment #37) > Under which application do you see the problem? I think that Thunderbird and > Firefox have their own cairo so the system one does not solve the issue. > Could you attach a screenshot so I can see the problem? Under both a GNOME/Xorg and a GNOME/Wayland desktop, it does seem to affect any application: Firefox (firefox-wayland and the default firefox builds), any GNOME application such as Nautilus, Evolution, GEdit; GNOME shell; Different Qt5 applications, … -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 --- Comment #11 from John Smith <gbrbgm+3ir2tgnee3494(a)sharklasers.com> --- testing in gnome terminal ^ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 John Smith <gbrbgm+3ir2tgnee3494(a)sharklasers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gbrbgm+3ir2tgnee3494@sharkl | |asers.com --- Comment #10 from John Smith <gbrbgm+3ir2tgnee3494(a)sharklasers.com> --- Created attachment 1513503 --> https://bugzilla.redhat.com/attachment.cgi?id=1513503&action=edit broken after upgrade -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 --- Comment #9 from John Smith <gbrbgm+3ir2tgnee3494(a)sharklasers.com> --- Created attachment 1513502 --> https://bugzilla.redhat.com/attachment.cgi?id=1513502&action=edit working before upgrade -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1645763] ClearType enablement: strong color fringing that is not present in vanilla build from freetype git
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1645763 Randy Barlow <rbarlow(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbarlow(a)redhat.com --- Comment #38 from Randy Barlow <rbarlow(a)redhat.com> --- A Fedora update associated with this bug has been pushed to the stable repository. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 Nerijus Baliūnas <nerijus(a)users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nerijus(a)users.sou | |rceforge.net) | --- Comment #8 from Nerijus Baliūnas <nerijus(a)users.sourceforge.net> --- As reverting (dnf downgrade google-noto-sans-fonts) made text OK even in a running browser session, I did not try to restart browser. Tried now, and it's OK, text is rendered correctly after restart. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1645763] ClearType enablement: strong color fringing that is not present in vanilla build from freetype git
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1645763 --- Comment #37 from Marek Kašík <mkasik(a)redhat.com> --- (In reply to Christian Stadelmann from comment #35) > (In reply to Kevin Kofler from comment #34) > > cairo-1.16.0-3.fc29.x86_64 sets the correct LCD filter by default (that's > > what the change in cairo-1.16.0-2.fc29.x86_64 was for), so it is normal that > > setting it manually has no effect. > > Oh, that makes sense, thanks for the hint. > > > If you are still not happy with the result, you will probably just have to > > disable subpixel antialiasing altogether. Subpixel antialiasing necessarily > > has to play with the colors of the pixels. > > Subpixel antialiasing is still way worse than the freetype-freeworld > solution from rpmfusion on Fedora 28. The rpmfusion/freeworld solution > looked good, but both the new cairo-1.16.0-2.fc29.x86_64 subpixel > antialiasing and the grayscale antialiasing do not as they do not give sharp > edges. The cairo-1.16.0-2.fc29.x86_64 subpixel antialiasing is exaggerated > too much to be comfortable to look at. Is it possible that it is being > applied twice? Under which application do you see the problem? I think that Thunderbird and Firefox have their own cairo so the system one does not solve the issue. Could you attach a screenshot so I can see the problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1636511] update Google Noto to 2017-09-19 release
by bugzilla＠redhat.com 11 Dec '18

11 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1636511 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(nerijus(a)users.sou | |rceforge.net) --- Comment #7 from Akira TAGOH <tagoh(a)redhat.com> --- Assuming that you saw this issue on your browser. did you try to restart your browser after upgrading the google-noto-fonts packages? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs December 2018