[Bug 1924576] New: Default font subpixel rendering does not work
well as other Linux
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1924576
Bug ID: 1924576
Summary: Default font subpixel rendering does not work well as
other Linux
Product: Fedora
Version: 33
Hardware: All
OS: All
Status: NEW
Component: freetype
Severity: medium
Assignee: mkasik(a)redhat.com
Reporter: zhaohongxinxin(a)163.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
kevin(a)tigcc.ticalc.org, mclasen(a)redhat.com,
mkasik(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Version-Release number of selected component (if applicable):
Problem:
when enable subpixel in gnome-tweaks, the default rendering config will not
work well as other Linux.
Temporary Resolve:
copy those files to this directory /etc/fonts/conf.d/
*/usr/share/fontconfig/conf.avail/10-sub-pixel-rgb.conf
*/usr/share/fontconfig/conf.avail/11-lcdfilter-default.conf
I hope packcage maintainer could change those files intend put them on right
place.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 5 months
[Bug 2018036] New: pango 1.49.1 broke multi-line text rendering in
Inkscape
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2018036
Bug ID: 2018036
Summary: pango 1.49.1 broke multi-line text rendering in
Inkscape
Product: Fedora
Version: 35
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: akiyks(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1837826
--> https://bugzilla.redhat.com/attachment.cgi?id=1837826&action=edit
Inkscape input and output
Description of problem:
I'm observing mis-placement of multi-line texts in .pdf converted
from .svg via Inkscape on pre-release Fedora 35.
On Fedora 34, they are rendered correctly.
Version-Release number of selected component (if applicable):
On Fedora 35, "incscape --debug-info" says:
Inkscape 1.1 (c68e22c387, 2021-05-23)
GLib version: 2.70.0
GTK version: 3.24.30
glibmm version: 2.66.1
gtkmm version: 3.24.5
libxml2 version: 2.9.12
libxslt version: 1.1.34
Cairo version: 1.17.4
Pango version: 1.49.1
HarfBuzz version: 2.8.2
Poppler version: 21.08.0
OS version: Fedora Linux 35 (Container Image)
On Fedora 34, "incscape --debug-info" says:
Inkscape 1.1 (c68e22c387, 2021-05-23)
GLib version: 2.68.4
GTK version: 3.24.30
glibmm version: 2.66.1
gtkmm version: 3.24.5
libxml2 version: 2.9.12
libxslt version: 1.1.34
Cairo version: 1.17.4
Pango version: 1.48.10
HarfBuzz version: 2.7.4
Poppler version: 21.01.0
OS version: Fedora 34 (Container Image)
How reproducible:
Always.
Steps to Reproduce:
Convert pubsub.svg in the attachment by Inkscape.
1. Run the command "inkscape -o pubsub-xxx.pdf pubsub.svg"
Actual results:
See pubsub-pango-1.49.1.pdf in the attachment.
Expected results:
See pubsub-pango-1.48.10.pdf in the attachment, which is converted
on Fedora 34.
Additional info:
On Fedora 35, by downgrading pango to 1.48.9
(https://kojipkgs.fedoraproject.org//packages/pango/1.48.9/1.fc35/x86_64/p...),
correct rendering can be restored.
The same issue is reported at upstream Inkscape project at:
https://gitlab.com/inkscape/inkscape/-/issues/2864
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2018036
2 years, 5 months
[Bug 1851919] New: Pango 1.45 crashes pidgin with any link click
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1851919
Bug ID: 1851919
Summary: Pango 1.45 crashes pidgin with any link click
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: zkabelac(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I've noticed instant crash of a pidgin - with this new pango 1.45 package.
I've downgraded to version pango-1.44.7-3.fc33 and pidgin is 'usable'
again (aka I can click on URL without getting instant core dump).
This is backtrace I'm getting on a crash:
(pidgin 2.13.0-20)
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
--Type <RET> for more, q to quit, c to continue without paging--
49 return ret;
[Current thread is 1 (Thread 0x7f2b86c61cc0 (LWP 100183))]
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007f2b883a78a4 in __GI_abort () at abort.c:79
#2 0x00007f2b886d5b6c in g_assertion_message
(domain=<optimized out>, file=0x7f2b88b7e19b "../pango/pango-context.c",
line=<optimized out>, func=<optimized out>, message=<optimized out>) at
../glib/gtestutils.c:2930
#3 0x00007f2b8873408f in g_assertion_message_expr
(domain=0x7f2b88b79e0d "Pango", file=0x7f2b88b7e19b
"../pango/pango-context.c", line=1435, func=0x7f2b88b7e3d0
"itemize_state_process_run", expr=<optimized out>) at ../glib/gtestutils.c:2956
#4 0x00007f2b88b603d6 in itemize_state_process_run () at
/lib64/libpango-1.0.so.0
#5 0x00007f2b88b61218 in pango_itemize_with_base_dir () at
/lib64/libpango-1.0.so.0
#6 0x00007f2b88b6a695 in pango_layout_check_lines.part () at
/lib64/libpango-1.0.so.0
#7 0x00007f2b88b6c539 in pango_layout_get_extents_internal () at
/lib64/libpango-1.0.so.0
#8 0x00007f2b88b6cac1 in pango_layout_get_pixel_size () at
/lib64/libpango-1.0.so.0
#9 0x000056100c9047f1 in gtk_imhtml_tip ()
#10 0x00007f2b8870ba51 in g_timeout_dispatch
(source=source@entry=0x56100ec326c0, callback=0x56100c9045b0
<gtk_imhtml_tip>, user_data=0x56100d93c2b0)
at ../glib/gmain.c:4800
#11 0x00007f2b8870aeaf in g_main_dispatch (context=0x56100d287540) at
../glib/gmain.c:3309
#12 g_main_context_dispatch (context=0x56100d287540) at ../glib/gmain.c:3974
#13 0x00007f2b8870b238 in g_main_context_iterate
(context=0x56100d287540, block=block@entry=1, dispatch=dispatch@entry=1,
self=<optimized out>)
at ../glib/gmain.c:4047
#14 0x00007f2b8870b553 in g_main_loop_run (loop=0x56100ea147e0) at
../glib/gmain.c:4241
#15 0x00007f2b88f37ba2 in gtk_main () at /lib64/libgtk-x11-2.0.so.0
#16 0x000056100c8bdb4c in main ()
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 5 months
[Bug 2012538] New: dnf group info fonts outputs
khmer-os-fasthad-fonts
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2012538
Bug ID: 2012538
Summary: dnf group info fonts outputs khmer-os-fasthad-fonts
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: khmeros-fonts
Severity: low
Assignee: gwync(a)protonmail.com
Reporter: kixbugzilla(a)pm.me
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
gwync(a)protonmail.com, pnemade(a)redhat.com
Target Milestone: ---
Classification: Fedora
User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101
Firefox/91.0
Build Identifier:
When using the dnf group info fonts command, some of the output is incorrect:
it is displayed as khmer-os-fasthad-fonts, but the correct name is
khmer-os-fasthand-fonts.
Reproducible: Always
Steps to Reproduce:
1. Run dnf group info fonts -v | grep khmer-os-fast.
2.
3.
Actual Results:
khmer-os-fasthad-fonts will be displayed.
Expected Results:
khmer-os-fasthand-fonts will be displayed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2012538
2 years, 5 months
[Bug 37984] [Freetype] Support for "locl" tables
by bugzilla-daemon@webkit.org
https://bugs.webkit.org/show_bug.cgi?id=37984
Carlos Alberto Lopez Perez <clopez(a)igalia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clopez(a)igalia.com
--- Comment #50 from Carlos Alberto Lopez Perez <clopez(a)igalia.com> ---
Comment on attachment 442519
--> https://bugs.webkit.org/attachment.cgi?id=442519
Patch
The in-test GTK LayoutTest EWS at the UAT (still behind a firewall) found a new failure with this patch:
imported/w3c/web-platform-tests/css/css-fonts/font-language-override-02.html [ ImageOnlyFailure ]
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 6 months
[Bug 37984] [Freetype] Support for "locl" tables
by bugzilla-daemon@webkit.org
https://bugs.webkit.org/show_bug.cgi?id=37984
Martin Robinson <mrobinson(a)webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #442519|review? |review-
Flags| |
--- Comment #49 from Martin Robinson <mrobinson(a)webkit.org> ---
Comment on attachment 442519
--> https://bugs.webkit.org/attachment.cgi?id=442519
Patch
View in context: https://bugs.webkit.org/attachment.cgi?id=442519&action=review
This is great! Looks like the test is still failing on Mac and this should handle a failed call to hb_language_from_string, but this is a good start.
> Source/WebCore/platform/graphics/harfbuzz/ComplexTextControllerHarfBuzz.cpp:548
> + hb_language_t language = hb_language_from_string(reinterpret_cast<const char*>(m_font.fontDescription().computedLocale().characters8()), -1);
I think it would be better to do this here:
hb_language_from_string(m_font.fontDescription().computedLocale().string().toUTF8().data()), -1);
This would allow you to avoid the reinterpret_cast.
It seems like this call should check for and handle (not set the language below) the situation where HB_LANGUAGE_INVALID is returned here.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 6 months