i18n-bugs November 2019

i18n-bugs@lists.fedoraproject.org

1 participants
124 discussions

[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 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 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 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 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 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 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 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs November 2019