i18n-bugs May 2021

i18n-bugs@lists.fedoraproject.org

1 participants
87 discussions

[Fedora-i18n-bugs] [Bug 1815510] New: Input hangul -> cursor becomes ahead in preedit
by bugzilla＠redhat.com 24 Nov '21

24 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1815510 Bug ID: 1815510 Summary: Input hangul -> cursor becomes ahead in preedit Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-hangul Assignee: pwu(a)redhat.com Reporter: sangu.fedora(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Input hangul -> cursor becomes ahead in preedit Version-Release number of selected component (if applicable): 1.5.3-2.fc32.x86_64 How reproducible: always in haungul input state Steps to Reproduce: 1. gedit starts 2. switch hangul 3. input hangul Actual results: Expected results: Additional info: ibus-1.5.22-4.fc32.x86_64 gtk3-3.24.14-1.fc32.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[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 1930214] New: Please retire man-pages-es
by bugzilla＠redhat.com 03 Nov '21

03 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1930214 Bug ID: 1930214 Summary: Please retire man-pages-es Product: Fedora Version: rawhide Status: NEW Component: man-pages-es Severity: high Assignee: domingobecker(a)gmail.com Reporter: nforro(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: domingobecker(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, peter(a)thecodergeek.com Target Milestone: --- Link ID: Red Hat Bugzilla 1925829,Red Hat Bugzilla 1929938 Classification: Fedora Updated Spanish translation of man pages now exists as part of manpages-l10n project [1], which is already packaged in Fedora [2]. Could you please retire man-pages-es package so that it can be replaced with updated translations from man-pages-l10n? [1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/ [2] https://src.fedoraproject.org/rpms/man-pages-l10n -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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

[Bug 1965684] New: Fontconfig & Firefox font issues on KDE Spins since F32
by bugzilla＠redhat.com 24 Jul '21

24 Jul '21

https://bugzilla.redhat.com/show_bug.cgi?id=1965684 Bug ID: 1965684 Summary: Fontconfig & Firefox font issues on KDE Spins since F32 Product: Fedora Version: 34 Hardware: x86_64 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: pimk1n(a)gmx.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, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pnemade(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 1787942 --> https://bugzilla.redhat.com/attachment.cgi?id=1787942&action=edit reddit.com poor font rendering Description of problem: Since F32 the KDE Spin has required manual creation of a local fontconfig in order to restore font rendering quality in Firefox back to standards seen in prior releases. Version-Release number of selected component (if applicable): F32 KDE onwards, Firefox 78 onwards. How reproducible: 100% F32 KDE, F33 KDE, F34 KDE Spin Reproducible with Fedora packaged Firefox, mozilla flatpak and direct Mozilla download. Confirmed on various hardware, all under X11. Steps to Reproduce: 1. Open Firefox (KDE Spin) 2. Observe lack of smooth font rendering. eg: https://old.reddit.com, https://bugzilla.redhat.org 3. Actual results: Poor quality font rendering, see screenshots. Expected results: Better quality font rendering, as seen in earlier Fedora 31 KDE and all tested modern KDE distros. Additional info: I have tried reporting this against Firefox since F32 Beta, but no fix. https://bugzilla.redhat.com/show_bug.cgi?id=1830509 The single end user fix is simple, just create a ~/.config/fontconfig/fonts.conf as below, run fc-cache and restart Firefox. <?xml version='1.0'?> <!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <match target="font"> <edit name="antialias" mode="assign"> <bool>true</bool> </edit> <edit name="autohint" mode="assign"> <bool>false</bool> </edit> <edit name="hinting" mode="assign"> <bool>true</bool> </edit> <edit name="hintstyle" mode="assign"> <const>hintslight</const> </edit> <edit name="lcdfilter" mode="assign"> <const>lcddefault</const> </edit> <edit name="rgba" mode="assign"> <const>rgb</const> </edit> </match> </fontconfig> What changed with KDE or Firefox around F32 time that other distros have accounted for, but Fedora has not? Would love to see Firefox back to usual quality in KDE spin, by default, so new users do not get this. If this is still not the correct package to report against, please point me in the right direction. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[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 1943000] New: emacs-lookup: FTBFS with upcoming autoconf-2.71
by bugzilla＠redhat.com 18 Jun '21

18 Jun '21

https://bugzilla.redhat.com/show_bug.cgi?id=1943000 Bug ID: 1943000 Summary: emacs-lookup: FTBFS with upcoming autoconf-2.71 Product: Fedora Version: rawhide Status: NEW Component: emacs-lookup Assignee: dueno(a)redhat.com Reporter: odubaj(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Blocks: 1942967 Target Milestone: --- Classification: Fedora Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1942967 [Bug 1942967] FTBFS with upcoming autoconf-2.71 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1951861] New: switch to using %transfiletriggerin for updating ibus cache
by bugzilla＠redhat.com 17 Jun '21

17 Jun '21

https://bugzilla.redhat.com/show_bug.cgi?id=1951861 Bug ID: 1951861 Summary: switch to using %transfiletriggerin for updating ibus cache Product: Fedora Version: rawhide Status: NEW Component: ibus 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: Rather than having each ibus engine update in a dnf transaction running ibus write-cache --system twice (%post and %postun) or once separately in %posttrans, it would be better to do it centrally from ibus.spec using a file trigger on "/usr/share/ibus/component". I think you tested it locally once and I believe it should work well enough. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs May 2021