i18n-bugs November 2020

i18n-bugs@lists.fedoraproject.org

1 participants
65 discussions

[Fedora-i18n-bugs] [Bug 1851919] New: Pango 1.45 crashes pidgin with any link click
by bugzilla＠redhat.com 24 Nov '21

24 Nov '21

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.

1 12

[Fedora-i18n-bugs] [Bug 1888536] New: Wrong shape in U+300D
by bugzilla＠redhat.com 09 Nov '21

09 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1888536 Bug ID: 1888536 Summary: Wrong shape in U+300D Product: Fedora Version: 33 Status: NEW Component: sil-nuosu-fonts Assignee: pwu(a)redhat.com Reporter: tagoh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: eng-i18n-bugs(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com, petersen(a)redhat.com, pwu(a)redhat.com, qe-i18n-bugs(a)redhat.com Depends On: 1762623 Target Milestone: --- Classification: Fedora +++ This bug was initially created as a clone of Bug #1762623 +++ Description of problem: The short horizontal line must be at the bottom but currently it is at the top. see attached and the legend in fontforge say. Version-Release number of selected component (if applicable): sil-nuosu-fonts-2.1.1-14.el8.noarch How reproducible: always Steps to Reproduce: 1.see U+300D (」) 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Akira TAGOH on 2019-10-17 05:43:53 UTC --- --- Additional comment from Peng Wu on 2019-10-18 08:42:28 UTC --- Okay, sent an message to Nuosu SIL upstream. URL: https://software.sil.org/nuosu/#contact --- Additional comment from Peng Wu on 2019-10-22 05:00:45 UTC --- They replied they will fix it when next release. But the next release may be some months later, not decided yet. --- Additional comment from Jens Petersen on 2020-06-05 10:36:54 UTC --- Not sure if there is any update on this yet? --- Additional comment from Peng Wu on 2020-06-08 04:00:25 UTC --- From https://software.sil.org/nuosu/ , it seems no updates. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1762623 [Bug 1762623] Wrong shape in U+300D -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1659748] New: Characters get deleted as you type
by bugzilla＠redhat.com 13 Oct '21

13 Oct '21

https://bugzilla.redhat.com/show_bug.cgi?id=1659748 Bug ID: 1659748 Summary: Characters get deleted as you type Product: Fedora Version: 29 Status: NEW Component: ibus-m17n Severity: high Assignee: pnemade(a)redhat.com Reporter: lohang(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: When you type Sinhala using Wijesekera keyboard layout through ibus the first character gets deleted as soon as you start typing the second character. This is similar to the bug previously reported for Fedora 28 https://bugzilla.redhat.com/show_bug.cgi?id=1617978 How reproducible: (1) Steps to Reproduce: 1. Open Libre Office Writer (6.1.2.1) 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ක වීන් Expected results: ඩනිෂ්ක නවීන් Additional info: (2) When you try this with emacs the results are a little different. I am including it here assuming this is related to the same issue: This is how to reproduce with emacs: 1. Open emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.23.2) of 2018-08-13 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ඩනිෂ් කනවී න් Expected results: ඩනිෂ්ක නවීන් This adds a space before the last character of the first word, not where you want the space to be. -- You are receiving this mail because: You are on the CC list for the bug.

1 49

[Fedora-i18n-bugs] [Bug 1786596] New: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE
by bugzilla＠redhat.com 26 Aug '21

26 Aug '21

https://bugzilla.redhat.com/show_bug.cgi?id=1786596 Bug ID: 1786596 Summary: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE Product: Fedora Version: 31 OS: Linux Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: abetakehiko(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, 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: Japanese chars and Latin chars in the same line do not vertically align when the pango context's gravity is set to PANGO_GRAVITY_EAST and its hint set to PANGO_GRAVITY_HINT_LINE. Version-Release number of selected component (if applicable): pango-1.44.7-1.fc31.x86_64 How reproducible: Always Steps to Reproduce: pango-view --text="あーいうえお abcde" --gravity east --gravity-hint line --font="NotoSerifJP 24" Actual results: Japanese chars and Latin chars in the same line do not vertically align. Expected results: Japanese chars and Latin chars in the same line vertically align as before. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1677534] New: texttopaps OOMs with 4GB text file!
by bugzilla＠redhat.com 28 Jun '21

28 Jun '21

https://bugzilla.redhat.com/show_bug.cgi?id=1677534 Bug ID: 1677534 Summary: texttopaps OOMs with 4GB text file! Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: paps Severity: high Assignee: tagoh(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net, tagoh(a)redhat.com Depends On: 1635160 Target Milestone: --- Classification: Fedora (Cloned from a RHEL7 report) +++ This bug was initially created as a clone of Bug #1635160 +++ Description of problem: Trying to print with cups a 4Gb text file fail. texttopaps consume all the memory and is killed bye the system: [1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or sacrifice child [1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB, anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB /usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt --- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT --- Hmm, that log says it all. I don't think OOM is a software bug. --- Additional comment from GV on 2018-10-03 13:00:48 SGT --- Of course OOM is not a software bug. Where exactly did I said that? The problem is texttopaps that allocate memory out of control. texttopaps should allocate memory, use-it, release-it. Like any sane program. The issue was not present on RHEL 6. I had printed the same file multiple times with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups filter involved). Printing the file does not work on RHEL 7 and it should. The 4Gb file is a testcase for our application we develop. --- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT --- I don't think the paps in RHEL7 is significantly different from RHEL6. As you say it could be due to changes in Cups? The cups versions in RHEL 6, 7 and Fedora are certainly quite different. Unless texttopaps really worked in RHEL6 it might make to reassign this to cups? --- Additional comment from GV on 2018-10-25 18:29:46 SGT --- Since the real computer running RHEL 6 was already scrapped, I tried to make a virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6 when printing the 4GB file. I can't recall how much memory was in that computer. The virtual machine had 8Gb of memory allocated. Still, it does not matter that much. I think texttopaps have an issue and it should be fixed or at least an workaround should be available (other than 'don't print a file that large'). I'm afraid this is not a cups issue since I can reproduce the issue running the texttopaps standalone. Sincerely, Gabriel --- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT --- paps isn't supposed to work with large files. to support it, most of code needs to rewritten. this isn't realistic to provide an update for existing products. for a workaround, you can remove paps package (or simply remove /usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops which CUPS originally provides. this should works for this issue and as long as you don't need the internationalization support for printing. Hope that helps. --- Additional comment from GV on 2018-12-07 14:03:33 SGT --- It helps. Thank you! Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1635160 [Bug 1635160] texttopaps OOMs with 4GB text file! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1832098] New: Due to socket path changes ibus not working in F32 Wayland for qt4 apps
by bugzilla＠redhat.com 27 May '21

27 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1832098 Bug ID: 1832098 Summary: Due to socket path changes ibus not working in F32 Wayland for qt4 apps Product: Fedora Version: 32 Status: NEW Component: ibus-qt Severity: high Assignee: tfujiwar(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Due to changes in socket path for Wayland, ibus input does not work for qt4 apps under Wayland in Fedora 32. https://github.com/ibus/ibus-qt/pull/5 Version-Release number of selected component (if applicable): ibus-qt-1.3.3-22.fc31 How reproducible: 100% -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1836327 Bug ID: 1836327 Summary: Hangul text commit and key forward don't preserve order sometimes Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: edward.park0203(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Hangul text commit and key forward don't preserve order sometimes Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1753295 Bug ID: 1753295 Summary: Pango no longer supports bitmap fonts Product: Fedora Version: 31 Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jsbillin(a)umich.edu 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: In pango 1.44, pango dropped support for bitmap fonts, so font packages like terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora 30 and were using a bitmap font like Terminus, all your terminals will show the rectangular placeholders the first time you start a terminal. Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a terminal since they are pixel perfect. If Fedora 31 is going to disable support for bitmap fonts, it needs to be announced and the package maintainers of those bitmap font packages are going to need to find a way to convert their fonts. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install 'terminus-fonts' 2. Start GNOME terminal 3. Open Terminal Preferences 4. Attempt to change the font to Terminus font Actual results: If you upgraded from Fedora 30 and had Terminus fonts as the default font, the first time you launch Terminal, all the text will be the rectangular placeholders. If you search for the Terminus font in the preferences, you won't be able to find it. Expected results: Use the Terminus font as usual Additional info: It appears that pango switched from using FreeType to HarfBuzz, which only supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31, downgraded it, and now my terminals are fine showing my bitmap fonts. -- You are receiving this mail because: You are on the CC list for the bug.

1 127

[Fedora-i18n-bugs] [Bug 1830709] New: Invalid metainfo files
by bugzilla＠redhat.com 17 May '21

17 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1830709 Bug ID: 1830709 Summary: Invalid metainfo files Product: Fedora Version: 32 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: mohd.akram(a)outlook.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, psatpute(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Metainfo files provided by the package are deemed invalid by appstream. Version-Release number of selected component (if applicable): 20181223-7.fc32 How reproducible: Always. Steps to Reproduce: 1. appstreamcli validate /usr/share/metainfo/google-noto-sans-sinhala-vf.metainfo.xml Actual results: E: google-noto-sans-sinhala-vf:~: font-no-font-data E: google-noto-sans-sinhala-vf:4: cid-is-not-rdns google-noto-sans-sinhala-vf I: google-noto-sans-sinhala-vf:~: font-description-missing E: google-noto-sans-sinhala-vf:~: component-summary-missing E: google-noto-sans-sinhala-vf:~: component-name-missing E: google-noto-sans-sinhala-vf:~: extends-not-allowed I: google-noto-sans-sinhala-vf:4: cid-contains-hyphen google-noto-sans-sinhala-vf Validation failed: errors: 5, infos: 2 Expected results: Validation was successful. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Fedora-i18n-bugs] [Bug 1900282] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 11 May '21

11 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1900282 Bug ID: 1900282 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 33 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: envelsavinds(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Hi, I ran gnome-tweaks to change the scaling of the Fonts to 1.15, then I logged out the session and logged back in and got idbus crash. Version-Release number of selected component: ibus-1.5.23-1.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service cmdline: ibus-daemon --panel disable crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=5359c96fc5a74c16855c30cc02dab947;i=3b12;b=82adf9e3e6a343a49c5517ad8258399e;m=15c02b9d;t=5b4a5165ddbf3;x=b683e2d11a292955 kernel: 5.9.8-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1842034 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs November 2020