January 2021 - i18n-bugs - Fedora mailing-lists

[Fedora-i18n-bugs] [Bug 1919932] New: Culmus Hebrew fonts aren't usable by TeXLive after installation
by bugzilla＠redhat.com 01 Jul '26

01 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=1919932 Bug ID: 1919932 Summary: Culmus Hebrew fonts aren't usable by TeXLive after installation Product: Fedora Version: 33 Status: NEW Component: culmus-fonts Assignee: petersen(a)redhat.com Reporter: nikita(a)leshenko.net QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pnemade(a)redhat.com, psatpute(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1750496 --> https://bugzilla.redhat.com/attachment.cgi?id=1750496&action=edit Basic Hebrew document Description of problem: On a clean Fedora 33 after installing texlive, babel-hebrew, and tex-fonts-hebrew, I can't use pdflatex to render a Hebrew document. Detailed steps to reproduce and a possible fix are provided below. Version-Release number of selected component (if applicable): texlive 9:2020-34.fc33 texlive-babel-hebrew 9:svn30273.2.3h-34.fc33 tex-fonts-hebrew 0.1-33.fc33 How reproducible: Always Steps to Reproduce: 1. Start a new Fedora 33 container: podman run -it fedora:33 2. dnf install texlive texlive-babel-hebrew tex-fonts-hebrew 3. Try to render hello.tex document attached to this bug report (this is a basic Hebrew document). \documentclass{article} \usepackage[utf8x]{inputenc} \usepackage[english,hebrew]{babel} \begin{document} שלום! \end{document} Actual results: We get the following error message: !pdfTeX error: pdflatex (file rdavid): Font rdavid at 600 not found ==> Fatal error occurred, no output PDF file produced! Full log is at first.log. Expected results: Document is rendered :) Additional info: We need two steps to resolve the problem here. I'm not sure if these steps are the idiomatic way to fix the issue, but it worked for me... The first issue that that culmus.map is not included in the pdflatex.map, even though culmus.map is enabled in /etc/texlive/web2c/updmap.cfg. I was able to solve it with - updmap-sys --syncwithtrees - updmap-sys to recreate the map file. It would be nice the Culmus will do this by default as part of the installation. (Another temporary per-document solution is to add \pdfmapfile{culmus.map} to the Hebrew document.) Now if we re-run pdflatex we get a new error: !pdfTeX error: pdflatex (file DavidCLM-Medium.pfa): cannot open Type 1 font file for reading ==> Fatal error occurred, no output PDF file produced! The full log is in second.log. There are multiple ways around this problem: 1. Note that /usr/share/texmf/fonts/type1/public/ has a broken symlink to culmus. Even if we fix the symlink to point to /usr/share/fonts/culmus/, it doesn't work because pdflatex doesn't seem to follow directory symlinks. But if we actually create a directory and symlink fonts individually, it will work, like this: mkdir /usr/share/texmf/fonts/type1/public/culmus2 for i in /usr/share/fonts/culmus/*; do ln $i /usr/share/texmf/fonts/type1/public/culmus2/${i##*/}; done 2. A more "general" fix is to edit /etc/texlive/web2c/texmf.cnf instead and set OSFONTDIR to /usr/share/fonts/, but it seems like this change extends beyond Culmus so I'm not sure how practical is it to edit OSFONTDIR as part of installation. After building the map file and teaching latex to find Type1 Culmus fonts the Hebrew document can compile successfully. I hope that it will be possible to adjust the Culmus package so that Hebrew latex works out of the box. Thanks! I'm available for questions and clarifications. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1683395] New: emacs-common-ddskk-20150927 is available
by bugzilla＠redhat.com 29 Mar '26

29 Mar '26

https://bugzilla.redhat.com/show_bug.cgi?id=1683395 Bug ID: 1683395 Summary: emacs-common-ddskk-20150927 is available Product: Fedora Version: rawhide Status: NEW Component: emacs-common-ddskk Keywords: FutureFeature, Triaged Assignee: dueno(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 20150927 Current version/release in rawhide: 16.2-5.fc30 URL: http://openlab.ring.gr.jp/skk/maintrunk/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/679/ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com 02 Feb '26

02 Feb '26

https://bugzilla.redhat.com/show_bug.cgi?id=1790554 Bug ID: 1790554 Summary: Keyboard layout of Kana Kanji wont show up Product: Fedora Version: rawhide Hardware: x86_64 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: sumukher(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: The keyboard layout for Kana Kanji Japanese doesnt show up Version-Release number of selected component (if applicable): Fedora-Rawhide-20200112.n.0 How reproducible: Everytime Steps to Reproduce: 1. Install Fedora-Rawhide-20200112.n.0 WS from live boot 2. Open settings and navigate to Region and Language 3. Add Japanese Kana Kanji in the input source 4. Click the icon looking like an eye button which should open the keyboard layout Actual results: Doesn't show up the keyboard layout Expected results: The keyboard layout should show up like it shows up for english Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Fedora-i18n-bugs] [Bug 1897782] New: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1897782 Bug ID: 1897782 Summary: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications Product: Fedora Version: 33 Status: NEW Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: yemoran-2020(a)outlook.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: In Fedora 33 Workstation, with a Chinese system language, when I try to input with the ibus input (intelligent pinyin), and I pressed the slash key'/', then the slash character '/' will automatically keep repeating itself, even if I only pressed the slash key '/' once. Not only this caused unwanted '/' to spam, but: 1. Also prevents me from pressing alphabetical characters to use pinyin input normally, unless I delete all my remaining characters to exit pinyin prompt and start over; 2. Can possibly delete my already-saved text, in combination with <Ctrl-Backspace>. It seems that I have completely lost control within the pinyin prompt. I have met with other surprising conditions, though cannot be immediately reproduced now, but I believe more combinations of inputs triggering different bugs will be confirmed later. Version-Release number of selected component (if applicable): Any kind of version. I also tested with Fedora 32 Workstation, still have this bug. How reproducible: Always Steps to Reproduce: 1. Fetch any Fedora Workstation version, be it 32 or 33 or any updates applied. 2. Add Chinese input method 'Intelligent Pinyin' and switch to it 3. In GNOME(Wayland), open any GTK-based application, be it Firefox, GNOME Terminal, gedit, Libreoffice, ... (take gedit as an example) 4. Input 你好，今天天气 (keypress: nihao<1>，jintian<1>) as a start up example, confirm input use number key '1'. or keys like <Enter> or <Space>. 5. Input 怎么样/ (keypress: zenmy/）. Do not confirm immediately after 'zenmy', but press '/' exactly once. 6. The '/' character is repeating itself within several hundred milliseconds. 7. Press <Ctrl-Backspace>. gedit will highlight "你好，今天天气" (with a lot of trailing '/'). 8. Press <Backspace> to delete these Chinese characters. Actual results: Not only '/' is repeating itself, but also I lost control to gedit and gedit thinks you want to press '/' forever or even wants to delete my already-confirmed characters before this input. Expected results: 1. '/' Should not trigger anything, unless I have pressed this key and did not release this key press (but I always release keys) 2. '/' Should not make me lost control over pinyin prompt to gedit 3. <Backspace> Should only delete pinyin alphabets in pinyin prompt panel, and should not do anything to the background gedit texts, unless I have exited the pinyin prompt panel (because I confirmed my input or have deleted every pinyin alphabet in it) Additional info: 1. I did not found this bug on Debian buster or Arch with latest updates. Additionally, '/' did not even input a single character '/' in these distributions, but I cannot confirm if this is the expected behaviour. In Fedora 33 KDE, '/' did input a single character '/', but immediately stopped. 2. I didn't find this behaviour in qt-based applications (like Fedora Image Writer or Octave) in GNOME, or any application in other desktop environments (including KDE, or even GTK-based Cinnamon Desktop). This bug seems to only occur on GTK-based applications on GNOME. 3. I can be very sure that this is not caused by something wrong with my specific keyboard, because (a) Other distributions worked very well (b) Other Fedora spins worked very well (c) Qt-based applications in GNOME worked very well (d) GNOME X11 session worked very well (e) I replicated this bug on a fresh install of Fedora 32 Workstation in another laptop of mine. 4. I guess other special characters (or keys) like '[', ']', '\', '<Esc>', '<Backspace>', etc. may trigger similar bugs, but I cannot confirm. '/' will surely trigger this. ',' and '.' are used in pinyin input method to flip candidate characters pages, so they doesn't trigger this bug. ' does not trigger this bug (used in xi'an for 西安) -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1847347 Bug ID: 1847347 Summary: gnome-terminal and xfce4-terminal get surrounding text from previous application Product: Fedora Version: 32 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(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 I made the following screenshots and video by testing on Gnome-Xorg, but the problem occurs on Gnome-Wayland as well. How to reproduce (see also attached screenshots and video): - To show what happens with the surrounding text, I first opened the setup tool of ibus-typing-booster and set the debug level in the options tab to 3. When the debug level is high, the auxiliary text above the candidate list shows what context has been obtained by using surrounding text (if surrounding text is available, if it is not available like when using xterm, the context is just remembered from what was typed last). - I opened 3 windows: gedit, firefox, and gnome-terminal. - I focus on gedit and type "a b c d e" On top of the candidate list one can see: "Context: b c d" This is because when the letter "e" was typed, ibus-typing-booster got the surrounding text at the cursor position and parsed the last 3 tokens left of the cursor out of the result. And these last 3 tokens left of the cursor are "b c d". - Now I focus on firefox and type "f g h i j" On top of the candidate list one can see: "Context: g h i" I.e. the correct context "g h i" to the left of the just typed "j" (which is still in preedit) has been found using surrounding text. - Now I focus on gnome-terminal and type "k l m" On top of the candidate list one can see: "Context h i j" This comes from the surrounding text left of the cursor in *firefox*, *not* from gnome-terminal. Although gnome-terminal reports that surrounding text is supported, i.e. self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT is True (see the code to get the context at: https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hunsp… ) gnome-terminal does not really seem to support surrounding text. The surrounding text comes from the previous client which really supported surrounding text. If the previous client was firefox, one still gets the surrounding text from firefox while typing in gnome-terminal. Same with gedit, if the previous client before focussing on gnome-terminal was gedit, one still gets the surrounding text from gedit while typing in gnome-terminal. - The same problem occurs when using xfce4-terminal instead of gnome-terminal. - When using xterm, the problem does *not* occur because when using xterm self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT is False and then the get_context() immediately returns and the context remembered from the last text typed is used as a fallback. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1919963] New: /usr/share/doc/libunistring-devel/libunistring.html missing in devel
by bugzilla＠redhat.com 27 Nov '23

27 Nov '23

https://bugzilla.redhat.com/show_bug.cgi?id=1919963 Bug ID: 1919963 Summary: /usr/share/doc/libunistring-devel/libunistring.html missing in devel Product: Fedora Version: 32 Hardware: All OS: All Status: NEW Component: libunistring Severity: medium Assignee: p(a)draigbrady.com Reporter: reini.urban(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jim(a)meyering.net, p(a)draigbrady.com, redhat-bugzilla(a)linuxnetz.de Target Milestone: --- Classification: Fedora Description of problem: after installing libunistring and libunistring-devel the main doc entrypoint for html is missing. /usr/share/doc/libunistring-devel/libunistring.html Version-Release number of selected component (if applicable): libunistring-devel-0.9.10-7.fc32.x86_64 How reproducible: Open a html doc, and click on Contents. e.g firefox /usr/share/doc/libunistring-devel/libunistring_1.html Haven't checked if that is an upstream problem, or just a bad rpm spec. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1910836] New: stardict-3.0.6.2 is available
by bugzilla＠redhat.com 06 Jun '23

06 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1910836 Bug ID: 1910836 Summary: stardict-3.0.6.2 is available Product: Fedora Version: rawhide Status: NEW Component: stardict Keywords: FutureFeature, Triaged Assignee: psatpute(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com, petersen(a)redhat.com, psatpute(a)redhat.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 3.0.6.2 Current version/release in rawhide: 3.0.6-15.fc33 URL: http://sourceforge.net/projects/stardict-4 Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/4887/ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla＠redhat.com 02 Jun '23

02 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1813728 Bug ID: 1813728 Summary: Square four dot Unicode character has incorrect glyph Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: pango Severity: low Assignee: pwu(a)redhat.com Reporter: guillaumepoiriermorency(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: The glyph for the Unicode "square four dot" character is incorrect. Version-Release number of selected component (if applicable): I think this problem arose when upgrading from Fedora 30 to Fedora 31. How reproducible: The simplest way is to start GNOME Characters Map and search for "square four dot". -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Fedora-i18n-bugs] [Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com 25 Apr '23

25 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1779123 Bug ID: 1779123 Summary: Pango no longer supports type1 fonts Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: mjg(a)fedoraproject.org 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 type1 fonts. Therefore, no application which uses pango for font loading can use type1 fonts any more. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 (and later) How reproducible: always Steps to Reproduce: 1. Upgrade F31 or rawhide 2. Open any pango-using application 3. Try to use type1 font Actual results: No type1 font is usable Expected results: Type1 font is usable Additional info: bug 1753295 is the same bug for dropped bitmap font support. Over there, workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are discussed. An attempt to discuss type1 there failed. This bug here is specifically about type1 fonts to discuss ways (or their absence) to deal with pangos dropped type 1 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Fedora-i18n-bugs] [Bug 1895482] New: Liberation Fonts Support For Serbian locl Glyphs Incomplete
by bugzilla＠redhat.com 04 Apr '23

04 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1895482 Bug ID: 1895482 Summary: Liberation Fonts Support For Serbian locl Glyphs Incomplete Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: aleslavista(a)outlook.it 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, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1727218 --> https://bugzilla.redhat.com/attachment.cgi?id=1727218&action=edit Correctly Localized Glyphs Description of problem: Liberation Fonts do NOT provide full support for Serbian localized glyphs. Version-Release number of selected component (if applicable): Liberation-Fonts 2.1-1-1 How reproducible: You need a program that is able to access the font's localized glyphs: usually that's LibreOffice Writer. Steps to Reproduce: 1. Open LibreOffice Writer 2. Type бгдпт, then бгдпт in Italic, бгдпт in Bold and finally бгдпт in Italic Bold with Liberation Serif, and do the same with Liberation Sans 3. Set the language to "Serbian Cyrillic" Actual results: Not all glyphs are correctly localized Expected results: See attachment for correctly localized glyphs Additional info: Liberation Mono has slanted Italic, therefore only the first glyph should be localized: CYRILLIC LETTER SMALL BE. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1842034] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 14 Dec '22

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1842034 Bug ID: 1842034 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: niki.guldbrand(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 Version-Release number of selected component: ibus-1.5.22-7.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=f592520f518043e0bf22bcb1059f85fa;i=5f0d;b=e5641f6c2ed84e629455c7ec8e6a1276;m=1c9e25e;t=5a6dbe50f3604;x=b9e38dca02503832 kernel: 5.6.15-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 42 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Fedora-i18n-bugs] [Bug 1767976] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 14 Dec '22

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1767976 Bug ID: 1767976 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: rauch.christian(a)gmx.de 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 Version-Release number of selected component: ibus-1.5.21-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=3ad93f33cf144f27b2bc4f480d8f3f2e;i=4b9e;b=9037b22bbad44adc83ebb6c1be09e1fc;m=1975f869;t=594e3ce75700c;x=34f5463c97ecc8bd kernel: 5.3.5-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Fedora-i18n-bugs] [Bug 1850832] New: The Gujarati & Hindi itrans methods are not able to type sentences correctly.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1850832 Bug ID: 1850832 Summary: The Gujarati & Hindi itrans methods are not able to type sentences correctly. Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-m17n Severity: high Assignee: pnemade(a)redhat.com Reporter: nirmalpathak(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1698739 --> https://bugzilla.redhat.com/attachment.cgi?id=1698739&action=edit Actual result while typing in GEdit using Gujarati and Hindi using itrans(m17n) input method. Description of problem: The Gujarati & Hindi itrans methods are not able to type sentences correctly. When you start typing in Gujarati or Hindi using itrans(m17n) input method, the letters at times are replaced by 'space' or it simply doesn't print. At times, the special characters like "?" are printed before the previously typed/printed character. This happens abruptly but in most cases, once you enter a new line by pressing 'enter' or 'return' key and start new sentence. Version-Release number of selected component (if applicable): m17n-db-1.8.0-9.fc32.noarch ibus-m17n-1.4.2-2.fc32.x86_64 m17n-lib-1.8.0-7.fc32.x86_64 How reproducible: Type in Gujarati or Hindi language using ibus itrans(m17n) method. Steps to Reproduce: 1. Select Gujarati (itrans - m17n) or Hindi (itrans - m17n) method from ibus input method. 2. Start typing multiple sentences in Gujarati or Hindi. 3. Press 'enter' or 'return' key to start a new sentence in a new line. Actual results: - કે મછે? - બરાબ રનથી લખાતું - कै से ?हो - ऐसा क्युं छ परहा है? Expected results: - કેમ છે? - બરાબર નથી લખાતું - कैसे हो? - ऐसा क्युं छप रहा है? Additional info: Please check attached GIF image for actual results. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Fedora-i18n-bugs] [Bug 1751061] New: Compose doesn’t work when using ibus
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1751061 Bug ID: 1751061 Summary: Compose doesn’t work when using ibus Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(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 I installed Fedora-Everything-netinst-x86_64-31-20190909.n.0.iso in qemu. Ibus version is: ibus-1.5.21-1.fc31.x86_64 I installed the gnome-tweaks package and set the compose key (Multi_key) to “Scroll Lock”. Configured input methods and keyboard layouts (as seen in the gnome panel) are: English (US, euro on 5) en 日本語　　　　　　　 ja 日本語（かな漢字） ja その他（Typing Booster） 🚀 I choose the "English (US, euro on 5)" keyboard layout and try to type into gedit. When pressing <Multi_key> , I see ⎄ i.e. I see U+2384 COMPOSITION SYMBOL as expected. But if I wait about a second, it disappears again. Now I type <Multi_key> <'> fast, not waiting after <Multi_key> I see ⎄' and it disappears again after about a second. <Multi_key> <'> <a> fast and I see: á After waiting for about a second, it turns into á⎄ i.e. U+2384 COMPOSITION SYMBOL is added after the á without pressing any more keys, just by waiting. This U+2384 COMPOSITION SYMBOL stays there, even if I wait more. If I continue to type <'> <a>, I finally get: áá i.e. I have produced this “áá” by typing <Multi_key> <'> <a> <'> <a>. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1733869 Bug ID: 1733869 Summary: gettext: Getting errors in double free with msgfmt command. Product: Fedora Version: 30 Status: NEW Component: gettext Assignee: panovotn(a)redhat.com Reporter: poyadav(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jjanco(a)redhat.com, nphilipp(a)redhat.com, panovotn(a)redhat.com, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Error in poc, please refer the result section for details. Version-Release number of selected component (if applicable): gettext-0.19.8.1-18.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1. Clone https://github.com/CCCCCrash/POCs.git. 2. Run valgrind msgfmt poc command. 3. Observe the output. Actual results: [poyadav@localhost doublefree]$ valgrind msgfmt poc ==8072== Memcheck, a memory error detector ==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==8072== Command: msgfmt poc ==8072== ==8072== Conditional jump or move depends on uninitialised value(s) ==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so) ==8072== by 0x487E8EA: po_lex_charset_set (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487E098: po_gram_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487A773: catalog_reader_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt) ==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt) ==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so) ==8072== poc:17: duplicate message definition... poc:16: ...this is the location of the first definition poc:18:3: syntax error poc:18: keyword "n" unknown poc:19: end-of-line within string poc:28: duplicate message definition... poc:24: ...this is the location of the first definition poc:35: keyword "msgud_plural" unknown poc:34: missing 'msgstr' section poc:35:13: syntax error poc:40: end-of-line within string poc:46: end-of-line within string poc: warning: Charset missing in header. Message conversion to user's charset will not work. poc:42: duplicate message definition... poc:6: ...this is the location of the first definition poc:46:2: syntax error poc:46: keyword "Ep" unknown poc:47: keyword "C" unknown poc:48: keyword "s" unknown poc:49: keyword "bo" unknown poc:50: keyword "S" unknown poc:50:236: invalid control sequence poc:50:397: invalid control sequence poc:51: end-of-line within string msgfmt: too many errors, aborting ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 59,783 bytes in 123 blocks ==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 650 bytes in 82 blocks ==8072== indirectly lost: 0 bytes in 0 blocks ==8072== possibly lost: 0 bytes in 0 blocks ==8072== still reachable: 59,133 bytes in 41 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== Use --track-origins=yes to see where uninitialised values come from ==8072== For lists of detected and suppressed errors, rerun with: -s ==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Expected results: No errors. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1771836] New: ibus not responsive on wayland with sway as windowmanager
by bugzilla＠redhat.com 30 Nov '22

30 Nov '22

https://bugzilla.redhat.com/show_bug.cgi?id=1771836 Bug ID: 1771836 Summary: ibus not responsive on wayland with sway as windowmanager Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: chorn(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 Created attachment 1635626 --> https://bugzilla.redhat.com/attachment.cgi?id=1635626&action=edit strace when running ibus-wayland from a terminal in sway Description of problem: ibus not responsive on wayland with sway as windowmanager Version-Release number of selected component (if applicable): ibus-wayland-1.5.21-3.fc31.x86_64 ibus-1.5.21-3.fc31.x86_64 ibus-mozc-2.23.2815.102-8.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora31, select lxde-desktop-environment to get wayland installed 2. dnf -y install sway ibus-wayland ibus-mozc 3. useradd -m chris; passwd chris 4. Use this in the users .bashrc : [[ $(pgrep ibus-daemon) ]] || ibus-daemon --xim --daemonize -r export IMSETTINGS_INTEGRATE_DESKTOP=yes export IMSETTINGS_MODULE=ibus export QT_IM_MODULE=ibus export XMODIFIERS=@im=ibus export GTK_IM_MODULE=ibus 5. Boot system into multi-usermode, for example in setting it as default target and rebooting 6. login as user chris 7. run sway in executing 'sway' 8. get a terminal in pressing $mod + return (by default, $mod is the windows-key) 9. verify ibus-daemon is running: 'ps ax|grep ibus' 10. try to run ibuswayland: '/usr/libexec/ibus-wayland' Actual results: No input_method global Expected results: ibus-wayland should run, and I should be able to switch input method to mozc as configured with 'ibus-setup'. Additional info: - Might very well be an issue on my side.. but after trying this now for a week, taking that to bugzilla. - fcitx4 from Fedora works under sway. - When setting up ibus as above, I was never able to run ibus-wayland, and ibus did never react to attempts to switch the input method with shift+space or ctrl+space, I tried these combinations after setting them up with ibus-setup - Instead of running ibus-daemon from user .bashrc, I did run it from sway directly. Steps: mkdir ~/.config/sway cp /etc/sway/config ~/.config/sway/config echo 'exec /usr/bin/ibus-daemon --xim --daemonize' >>~/.config/sway/config The result is the same though. - When running ibus-daemon non-daemonizing from a terminal, I get this: [chris@космос ~]$ ibus-daemon -r -v (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.303: panel.vala:255: If you launch KDE5 on xterm, export XDG_CURRENT_DESKTOP=KDE before launch KDE5. (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.335: ibus_bus_call_sync: org.freedesktop.DBus.Properties.Get: GDBus.Error:org.freedesktop.DBus.Error.Failed: No global engine. (and ibus-daemon stays running) - I tried various terminals, for example xterm and terminator -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1858617] New: vlgothic-fonts-20200719 is available
by bugzilla＠redhat.com 12 Oct '22

12 Oct '22

https://bugzilla.redhat.com/show_bug.cgi?id=1858617 Bug ID: 1858617 Summary: vlgothic-fonts-20200719 is available Product: Fedora Version: rawhide Status: NEW Component: vlgothic-fonts Keywords: FutureFeature, Triaged Assignee: tagoh(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 20200719 Current version/release in rawhide: 20141206-16.fc32 URL: https://osdn.jp/projects/vlgothic/releases/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/5103/ -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1916743] New: Fedora Scientific Spin does not include ibus-table* packages
by bugzilla＠redhat.com 12 Jul '22

12 Jul '22

https://bugzilla.redhat.com/show_bug.cgi?id=1916743 Bug ID: 1916743 Summary: Fedora Scientific Spin does not include ibus-table* packages Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-table Severity: high Assignee: mfabian(a)redhat.com Reporter: pa_ubach(a)alum.mit.edu QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com, mfabian(a)redhat.com, pwu(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: Clean install of Fedora Scientific (KDE) does not include the ibus-table* packages that are necessary for local distributions of the keyboard. Version-Release number of selected component (if applicable): How reproducible: Haven't tried Steps to Reproduce: 1. Install Fedora Scientific 2. Try to type using dead keys in any KDE program or LibreOffice. 3. Actual results: Vowel letters don't include accents. Expected results: áàäâéèéêíïîóòöôúùüû Additional info: To fix the problem, the user must install ibus-table* packages, which is not described in the documentation, but it should not be necessary to search it in the documentation anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Fedora-i18n-bugs] [Bug 1757760] New: Hiragana to English conversion with F10 key adds unwanted letters
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1757760 Bug ID: 1757760 Summary: Hiragana to English conversion with F10 key adds unwanted letters Product: Fedora Version: rawhide Status: NEW Component: ibus-kkc Assignee: dueno(a)redhat.com Reporter: ykatabam(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: When we enter an English word with consecutive double letters (e.g. assembly) in Hiragana mode and use F10 to convert into English, the double letters becomes the triple letters in some cases (e.g. asssembly). This happens irregularly, but tends to happen more often for longer words. Here are some examples: communication becomes commmunication bugzilla becomes bugzilla Pittsburgh becomes Pitttsburgh FYI, auto-correct is disabled, as auto-correct changes the input when it's not a dictionary word so it doesn't allow us to convert into English properly in hiragana mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1787124] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by bugzilla＠redhat.com 16 May '22

16 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=1787124 Bug ID: 1787124 Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR IANT_ID=matecompiz; Component: mozc Assignee: tagoh(a)redhat.com Reporter: ryutaroh2006(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I don't know how or why ibuz-engine-mozc was killed by SIGABRT... Version-Release number of selected component: ibus-mozc-2.23.2815.102-8.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service cmdline: /usr/libexec/ibus-engine-mozc --ibus crash_function: __fdelt_chk executable: /usr/libexec/ibus-engine-mozc journald_cursor: s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9 kernel: 5.3.16-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #6 __fdelt_chk at fdelt_chk.c:25 #7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108 #8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157 #9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1899794] New: Fails to run on KDE in Rawhide
by bugzilla＠redhat.com 13 May '22

13 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=1899794 Bug ID: 1899794 Summary: Fails to run on KDE in Rawhide Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: system-config-language Severity: high Assignee: pnemade(a)redhat.com Reporter: awilliam(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com, pnemade(a)redhat.com, psatpute(a)redhat.com Target Milestone: --- Classification: Fedora In current Rawhide, system-config-language is installed on KDE out of the box, but fails to run. Running from a console, after you are prompted for the root password, you get these errors: No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused (system-config-language.py:2146): Gtk-WARNING **: 18:09:41.831: cannot open display: :1 then it exits back to the console. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1903877] New: kde-l10n-pa missing translated file
by bugzilla＠redhat.com 03 Apr '22

03 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=1903877 Bug ID: 1903877 Summary: kde-l10n-pa missing translated file Product: Fedora Version: 33 Status: NEW Component: kde-l10n Keywords: i18n Assignee: than(a)redhat.com Reporter: aalam(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz, rdieter(a)gmail.com, smparrish(a)gmail.com, than(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1735891 --> https://bugzilla.redhat.com/attachment.cgi?id=1735891&action=edit KDE system Tray (software, Keyboard Indicator) Description of problem: Version-Release number of selected component (if applicable): kde-l10n-pa-17.08.3-9.fc33.noarch apper-1.0.0-6.fc32.x86_64 How reproducible: every time Steps to Reproduce: 1. translation is not available for various KDE packages 2.rpm -q kde-l10n-pa -l|grep apper||grep rpm -q kde-l10n-pa -l|grep kdeplasma 3. Actual results: applications are untranslated. Various untranslated section on KDE desktop in Punjabi No output for file search Expected results: 4 following files apper._desktop_.po apper.po org.kde.apper.appdata.po plasma_applet_org.packagekit.updater.po Additional info: KDE svn source has apper fully transalted files for Punjabi since 2011: https://websvn.kde.org/trunk/l10n-kf5/pa/messages/apper/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1809989] New: By default install Noto fonts for Unicode scripts not already covered by default
by bugzilla＠redhat.com 02 Apr '22

02 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=1809989 Bug ID: 1809989 Summary: By default install Noto fonts for Unicode scripts not already covered by default Product: Fedora Version: 31 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: hsivonen(a)hsivonen.fi 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 There is currently movement towards protecting browser users from font fingerprinting. This means refusing, by default, to load user-installed fonts, which makes the set of fonts that each OS installs by default even more important than before. Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1582687 W3C CSS WG issue: https://github.com/w3c/csswg-drafts/issues/4497 Currently, Windows 10, macOS, Android, and Chrome OS provide broader installed-by-default Unicode coverage than Fedora. Examples of living scripts that have enough active users to make it to the list at https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scrip… but are not supported by default in Fedora 31 include Javanese, Sundanese, Batak, Balinese, Mongolian, and New Tai Lue. Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't support out of the box but Windows 10, macOS, Chrome OS, and Android do. To remedy this with minimal disk space impact, I suggest the same approach that Apple took. Apple bundles with macOS those Noto fonts that cover scripts that were not already covered by the previous installed-by-default set of fonts on macOS. In the macOS case, the on-disk footprint of the Noto fonts that were required to take macOS to Android/Chrome OS-competitive Unicode coverage was only a couple of megabytes. (The fonts are hidden in /Library/Application Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto fonts required to reach the Chrome OS / Android level of script coverage is a bit larger than in the macOS case but should still be manageable. Please install, by default, those Noto fonts that provide support for scripts that are not properly supported by the fonts that Fedora already installs by default. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Fedora-i18n-bugs] [Bug 1832351] New: Macintosh keyboard variants not available
by bugzilla＠redhat.com 24 Mar '22

24 Mar '22

https://bugzilla.redhat.com/show_bug.cgi?id=1832351 Bug ID: 1832351 Summary: Macintosh keyboard variants not available Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Component: xkeyboard-config Severity: medium Assignee: peter.hutterer(a)redhat.com Reporter: mthoemme(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, negativo17(a)gmail.com, peter.hutterer(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I do not have any variants for Macintosh available when trying to change the keyboard layout via the GUI (Region & Language Settings). Trying to manually set the keymap in the locale works for the VC keymap, but not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac" respectively, leave the X11 Layout at "de" localectl set-keymap de-mac Digging even deeper, the following commands all yield the same errors: localectl set-x11-keymap de-mac localectl set-x11-keymap de_mac localectl set-x11-keymap de macintosh de_mac All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing as invalid." Version-Release number of selected component (if applicable): dnf info xkeyboard-config Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST. Installed Packages Name : xkeyboard-config Version : 2.29 Release : 1.fc32 Architecture : noarch Size : 5.5 M Source : xkeyboard-config-2.29-1.fc32.src.rpm Repository : @System From repo : anaconda Summary : X Keyboard Extension configuration data URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig License : MIT Description : This package contains configuration data used by the X Keyboard Extension (XKB), : which allows selection of keyboard layouts when using a graphical interface. How reproducible: Happens consistently. I'm on a fresh Fedora 32 install. Steps to Reproduce: 1. localectl set-x11-keymap de macintosh de_mac Actual results: "Failed to set keymap: Specified keymap cannot be compiled, refusing as invalid." Expected results: Successfully sets the keyboard layout to a Macintosh variant. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1784650] New: Fontconfig is slow, causing stuttering and freezing
by bugzilla＠redhat.com 03 Mar '22

03 Mar '22

https://bugzilla.redhat.com/show_bug.cgi?id=1784650 Bug ID: 1784650 Summary: Fontconfig is slow, causing stuttering and freezing Product: Fedora Version: 31 Status: NEW Component: fontconfig Severity: high Assignee: tagoh(a)redhat.com Reporter: bepvte+bugzilla(a)gmail.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, john.j5live(a)gmail.com, 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 Description of problem: Fontconfig is much much slower than on other distros, and it stutters or freezes applications that use it. Version-Release number of selected component (if applicable): Name : fontconfig Version : 2.13.92 Release : 3.fc31 Architecture: x86_64 How reproducible: I can reproduce this bug on a fresh Fedora 31 vm with the Xfce desktop and google-noto-sans-* fonts installed. Steps to Reproduce: 1. dnf install google-noto-sans-* 2. run gedit on the attached example file alternatively 1. dnf install google-noto-sans-* 2. open firefox and browse to https://www.wikidata.org/wiki/Q52 (page with lots of languages) Actual results: It takes around 60 seconds for gedit to become responsive to scrolling and input. Mousepad is faster but still slow. It takes firefox upwards of 5 minutes to get to first paint on a page with many fonts or languages, compared to a simpler page. Expected results: Gedit should load files with many fonts at a similar speed as other distros. The page should load quickly, like on Debian and others. Additional info: I have tried to diagnose the source of this issue in many ways. Running `perf trace` on what sysprof indicated was the most busy function (FcStrCmpIgnoreCaseAndDelims), shows that every name of every font family is being compared to every other name of every other font family. I do not know if this is a normal behaviour of fontconfig. I have noticed the amount of calls to "FcStrCmpIgnoreCaseAndDelims" and program startup time both drop to a similar amount as Debian's when all of the "google-noto" configuration files in /etc/fonts/conf.d/ are deleted (These files are not present in Debian). However, this might not be the source of the problem: In the Debian vm, with a copy of my computer's /etc/fonts/, including the google-noto files, (I took care to ensure that there would be no broken symlinks) and /usr/share/fonts, fontconfig does not stall any programs. The amount of calls to FcStrCmpIgnoreCaseAndDelims is also much lower as well. This led me to believe that it was a difference caused by compiler flags but this does not seem to be the case. I tried to replace the optflags in the package, except for the rpmbuild required debug ones, and found no difference. I also checked to ensure that it was not caused by GCC version differences. Debian results for mousepad: 1,845,449 calls to FcStrCmpIgnoreCaseAndDelims Time: 5 seconds Fedora results for mousepad: 11,658,380 calls to FcStrCmpIgnoreCaseAndDelims Time: 23 seconds https://perfht.ml/2tleJxN Here is a link to a Firefox profiler result of the wikidata page, where in the flame graph you can see that Firefox is spending most of its time in fontconfig. You can also see "FirstNonBlankPaint" is at 50 seconds in the marker table. TLDR: Fontconfig matching is slow with all google-noto fonts installed, unless you remove the noto config files. Using the same exact font directory and config directory (including the noto config files) on Debian does not cause the same problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1919760] New: [abrt] ibus: invoke_get_property_in_idle_cb(): ibus-ui-gtk3 killed by SIGABRT
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1919760 Bug ID: 1919760 Summary: [abrt] ibus: invoke_get_property_in_idle_cb(): ibus-ui-gtk3 killed by SIGABRT Product: Fedora Version: 33 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:1550d568515be5da0d8fa0ca9eb0b2e4d8db85bc; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: alain.thiaville(a)sfr.fr 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 Version-Release number of selected component: ibus-1.5.23-2.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/dbus\x2d:1.3\x2dcom.redhat.imsettings.slice/dbus-:1.3-com.redhat.imsettings@0.service cmdline: /usr/libexec/ibus-ui-gtk3 crash_function: invoke_get_property_in_idle_cb executable: /usr/libexec/ibus-ui-gtk3 journald_cursor: s=9fdab79de00a4521972b23b84b3df8a6;i=9604;b=1a89d997ec324b54ade433d343bd315b;m=b4c8678a9;t=5b9b18c4cc4b5;x=749fe5d392007729 kernel: 5.10.9-201.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 xsession_errors: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1910907] New: [abrt] ibus-kkc: gee_array_list_real_get(): ibus-engine-kkc killed by SIGABRT
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1910907 Bug ID: 1910907 Summary: [abrt] ibus-kkc: gee_array_list_real_get(): ibus-engine-kkc killed by SIGABRT Product: Fedora Version: 33 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:88de9664ac0f50184e02ce3df98d857f4c9334f0;VAR IANT_ID=workstation; Component: ibus-kkc Assignee: dueno(a)redhat.com Reporter: ramot(a)ramottamado.dev QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-kkc-1.5.22-14.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: /usr/libexec/ibus-engine-kkc --ibus crash_function: gee_array_list_real_get executable: /usr/libexec/ibus-engine-kkc journald_cursor: s=b9a02946f72241c5826b5804d8ded9b6;i=13b91a;b=f6f1121902224e3c95d41e6edabda311;m=72e3e2286;t=5b749367c7aab;x=4eeb00e5e71d231f kernel: 5.9.14-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 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 26 May '21

26 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 16 May '21

16 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

[Fedora-i18n-bugs] [Bug 1879106] New: In add input source "SEARCH" for input not working properly.
by bugzilla＠redhat.com 11 May '21

11 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1879106 Bug ID: 1879106 Summary: In add input source "SEARCH" for input not working properly. Product: Fedora Version: 33 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: prigupta(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1714925 --> https://bugzilla.redhat.com/attachment.cgi?id=1714925&action=edit screen cast for adding input source from search Description of problem: The search option in "add input source" is not working properly. Version-Release number of selected component (if applicable): Fedora-33 How reproducible: Steps to Reproduce: 1.Go to the settings --> region and language -- > input sources 2.Go to add input source(+) 3.try to search(:) some language specific input source. For example hangul(Korean), Intelligent pinyin(Chinese) , typing booster, Cangjie(chinese hong kong) Actual results: 1. Search will work for some input sources like typing booster( it will give "other") but it does not work for some input like hangul. intelligent pinyin, cangjie etc Expected results:The search should give proper results for all. Additional info:Attaching Screencast for more description. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1711646] New: Scriptlet error when updating through SSH
by bugzilla＠redhat.com 09 May '21

09 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1711646 Bug ID: 1711646 Summary: Scriptlet error when updating through SSH Product: Fedora Version: 30 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: dreua(a)posteo.de 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: When I update or reinstall ibus-1.5.20-4.fc30 over SSH, dnf outputs the error "X11 connection rejected because of wrong authentication.". This is caused by https://src.fedoraproject.org/rpms/ibus/blob/master/f/ibus.spec#_338 running `sudo ibus write-cache --system` results in the same error when called over SSH. Version-Release number of selected component (if applicable): ibus-1.5.20-4.fc30 How reproducible: Always over SSH, never when using the terminal directly on the machine. Steps to Reproduce: 1. Reinstall or update to ibus-1.5.20-4.fc30 Actual results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Verifying : ibus-1.5.20-4.fc30.x86_64 Expected results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 Verifying : ibus-1.5.20-4.fc30.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Fedora-i18n-bugs] [Bug 1899847] New: update to v2.7-NotoSlimVF
by bugzilla＠redhat.com 19 Apr '21

19 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1899847 Bug ID: 1899847 Summary: update to v2.7-NotoSlimVF Product: Fedora Version: rawhide Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: petersen(a)redhat.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: Version 2.6 and 2.7 with Slim VF fonts were released in 2019: https://github.com/googlefonts/noto-fonts/releases It would be good to update Fedora to them. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1922533] New: Many international google-noto-*-fonts have invalid Appstream data
by bugzilla＠redhat.com 05 Apr '21

05 Apr '21

https://bugzilla.redhat.com/show_bug.cgi?id=1922533 Bug ID: 1922533 Summary: Many international google-noto-*-fonts have invalid Appstream data Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: google-noto-fonts Assignee: tagoh(a)redhat.com Reporter: hank.johnson3002(a)gmail.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 Created attachment 1752196 --> https://bugzilla.redhat.com/attachment.cgi?id=1752196&action=edit List of google-noto-*-fonts packages with Appstream data issues Description of problem: Many international google-noto-*-fonts have invalid Appstream data. This causes warnings in applications using Appstream, like KDE Discover. It also makes many appstreamcli commands not work. Version-Release number of selected component (if applicable): Most of them are version 20181223-8.fc33 How reproducible: Should be easy Steps to Reproduce: 1. sudo dnf install google-noto-sans-arabic fonts (I will attach a txt file with the full list of google-noto fonts with this issue) Actual results: Running `appstreamcli status` warns "Error while loading the metadata pool: Many components have been recognized as invalid. See debug output for details." Verbose output with `appstreamcli status --verbose` is attached in txt file. Opening KDE Discover creates a warning that "Please make sure that Appstream is properly set up on your system". Expected results: Running `appstreamcli status` reports no errors. Opening KDE Discover shows no warning. Additional info: Removing the specified fonts fixes the issues. I tried force refreshing appstream cache, rebooting, reinstalling appstream data, etc. TXT file with list of the violating fonts is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1749943] New: pango contain header with wrong hb.h include
by bugzilla＠redhat.com 08 Mar '21

08 Mar '21

https://bugzilla.redhat.com/show_bug.cgi?id=1749943 Bug ID: 1749943 Summary: pango contain header with wrong hb.h include Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: vascom2(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: I am try to build eiskaltdcpp and it fsilrd with error: BUILDSTDERR: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory BUILDSTDERR: 28 | #include <hb.h> BUILDSTDERR: | ^~~~~~ Full build log https://kojipkgs.fedoraproject.org/work/tasks/5226/37235226/build.log Version-Release number of selected component (if applicable): pango-1.44.6-1.fc32 How reproducible: Always. As I see this line was added in pango 1.44. But harfbuzz's hb.h in Fedora placed at /usr/include/harfbuzz/ Need to solve it for build other packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1922481] New: translate-toolkit-3.3.1 is available
by bugzilla＠redhat.com 20 Feb '21

20 Feb '21

https://bugzilla.redhat.com/show_bug.cgi?id=1922481 Bug ID: 1922481 Summary: translate-toolkit-3.3.1 is available Product: Fedora Version: rawhide Status: NEW Component: translate-toolkit Keywords: FutureFeature, Triaged Assignee: suanand(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dwayne(a)translate.org.za, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, mmraka(a)redhat.com, petersen(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 3.3.1 Current version/release in rawhide: 3.3.0-1.fc34 URL: http://toolkit.translatehouse.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3685/ -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1922484] New: fcitx-libpinyin-0.5.4 is available
by bugzilla＠redhat.com 29 Jan '21

29 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1922484 Bug ID: 1922484 Summary: fcitx-libpinyin-0.5.4 is available Product: Fedora Version: rawhide Status: NEW Component: fcitx-libpinyin Keywords: FutureFeature, Triaged Assignee: liangsuilong(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, liangsuilong(a)gmail.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.5.4 Current version/release in rawhide: 0.5.3-11.fc33 URL: https://fcitx-im.org/wiki/Libpinyin Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/8011/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1918606] gkbd-keyboard-display crash when Show Keyboard Layout with some input methods
by bugzilla＠redhat.com 27 Jan '21

27 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1918606 fujiwara <tfujiwar(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i18n-bugs(a)lists.fedoraproje | |ct.org, tfujiwar(a)redhat.com --- Comment #1 from fujiwara <tfujiwar(a)redhat.com> --- I think it's good to move the report to upstream and my suggestion is to file a patch to save the previous keymap in gnome-shell. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1853937] Auto-hinter ignores non-unicode ligatures (e.g. Lato ti, tt)
by bugzilla＠redhat.com 26 Jan '21

26 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1853937 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|32 |rawhide --- Comment #29 from Akira TAGOH <tagoh(a)redhat.com> --- Moving this to rawhide. we are planning to fix this there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1554701] can't paste the flags emoji
by bugzilla＠redhat.com 26 Jan '21

26 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1554701 --- Comment #13 from Peng Wu <pwu(a)redhat.com> --- For gnome-terminal, vte may not support Unicode Emoji sequence. URL: https://gitlab.gnome.org/GNOME/vte/-/blob/master/src/vteunistr.h#L30 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1554701] can't paste the flags emoji
by bugzilla＠redhat.com 25 Jan '21

25 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1554701 --- Comment #12 from Matthias Clasen <mclasen(a)redhat.com> --- I believe this is https://gitlab.gnome.org/GNOME/pango/-/issues/293 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1761885] Drop unused .uuid files
by bugzilla＠redhat.com 25 Jan '21

25 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1761885 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ajax(a)redhat.com, | |caillon+fedoraproject@gmail | |.com, | |gnome-sig(a)lists.fedoraproje | |ct.org, | |i18n-bugs(a)lists.fedoraproje | |ct.org, mclasen(a)redhat.com, | |pnemade(a)redhat.com, | |rhughes(a)redhat.com, | |rstrode(a)redhat.com, | |sandmann(a)redhat.com Component|fontpackages |fontconfig Summary|rpm -V complains about mode |Drop unused .uuid files |for ghost .uuid files | --- Comment #7 from Akira TAGOH <tagoh(a)redhat.com> --- Moving this to fontconfig to drop the unused .uuid files from filesystem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs January 2021