December 2019 - i18n-bugs - Fedora mailing-lists

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

[Fedora-i18n-bugs] [Bug 1707001] New: Ibus-pinyin ERROR
by bugzilla＠redhat.com 12 Jan '21

12 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1707001 Bug ID: 1707001 Summary: Ibus-pinyin ERROR Product: Fedora Version: 30 Hardware: All OS: Linux Status: NEW Component: ibus-pinyin Severity: urgent Assignee: pwu(a)redhat.com Reporter: 1990konger(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: The input method is incorrect and cannot be recognized correctly. The text to be entered is required. For example, 'nihao' should be right, '你好'. Now enter 'nihao' to show 'niha o'.Unrecognized what you need 'ni' is a word. 'hao' is a word. 'ha' is a word but the display is wrong at this time and cannot be selected. Unable to recognize 'hao'. Affect all input suggestions to withdraw to the old version Version-Release number of selected component (if applicable): Name : ibus-pinyin Version : 1.5.0 Release : 16.fc30 How reproducible: 'nihao' is meaning is 'Hello' 'niha o', it is an error Steps to Reproduce: 1.All Chinese input is wrong Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1703849] New: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick
by bugzilla＠redhat.com 20 Oct '20

20 Oct '20

https://bugzilla.redhat.com/show_bug.cgi?id=1703849 Bug ID: 1703849 Summary: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jfrieben(a)hotmail.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: Using pango-view with backend ft2 in a current Fedora 29 Workstation installation fails because pango-view tries to launch the display utility from ImageMagick which has not been pulled in as a dependency. Version-Release number of selected component (if applicable): pango-1.42.4-2.fc29 How reproducible: Always Steps to Reproduce: 1. Launch GNOME session of a current Fedora 29 Workstation installation. 2. Run 'pango-view --backend=ft2 -t PANGO'. Actual results: Utility pango-view aborts with the error message: "pango-view: When running ImageMagick 'display' command: Failed to execute child process “display” (No such file or directory)" Expected results: Utility pango-view displays the sample text. Additional info: - Installing package ImageMagick prior to running pango-view ensures correct execution. Therefore, adding ImageMagick as a requirement of package pango solves this issue. - It is probably preferable to patch pango-view such that it calls "gm display" from package GraphicsMagick and to pull in the latter instead of ImageMagick. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1747731] New: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com 29 Sep '20

29 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1747731 Bug ID: 1747731 Summary: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:ebfdf9e0e88e902f1a9d6c72641712e29b0aca46; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: dcdrake42(a)gmail.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: Seemed to occur while typing immediately after changing from English to Chinese input while using the browser version of Facebook Messenger (Chromium). Version-Release number of selected component: ibus-libpinyin-1.11.1-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin::MemoryChunk::ensure_has_more_space(unsigned long) executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=9c254645106a4209b447b2a1893383ad;i=189698;b=c5ac01a80c3a439eb3832a0a5ed88e02;m=202900d17;t=59173a5b8af7b;x=99dc5a43153fc974 kernel: 5.2.9-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #7 pinyin::MemoryChunk::ensure_has_more_space(unsigned long) at ../../src/include/memory_chunk.h:122 #8 pinyin::MemoryChunk::ensure_has_space(unsigned long) at ../../src/include/memory_chunk.h:92 #9 pinyin::MemoryChunk::set_content(unsigned long, void const*, unsigned long) at ../../src/include/memory_chunk.h:286 #10 pinyin::MemoryChunk::append_content(void const*, unsigned long) at ../../src/include/memory_chunk.h:302 #11 pinyin::merge_single_gram(pinyin::SingleGram*, pinyin::SingleGram const*, pinyin::SingleGram const*) at ngram.cpp:322 #12 pinyin::PhoneticLookup<2, 3>::search_bigram2(_GPtrArray*, int, int, _GArray**) at ../src/include/memory_chunk.h:86 #13 pinyin::PhoneticLookup<2, 3>::get_nbest_match(_GArray*, pinyin::PhoneticKeyMatrix const*, pinyin::ForwardPhoneticConstraints const*, pinyin::NBestMatchResults*) at ../src/storage/phrase_index.h:731 #14 PY::FullPinyinEditor::insert(int) at PYPFullPinyinEditor.cc:56 #15 PY::PinyinEngine::processKeyEvent(unsigned int, unsigned int, unsigned int) at /usr/include/c++/9/bits/shared_ptr_base.h:1020 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1766971] New: Default monospace font Amharic is weird, makes gnome-terminal look weird
by bugzilla＠redhat.com 23 Sep '20

23 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1766971 Bug ID: 1766971 Summary: Default monospace font Amharic is weird, makes gnome-terminal look weird Product: Fedora Version: 31 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: mfabian(a)redhat.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 Created attachment 1630570 --> https://bugzilla.redhat.com/attachment.cgi?id=1630570&action=edit Screenshot.png [mfabian@localhost ~]$ fc-match monospace:lang=de DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" [mfabian@localhost ~]$ fc-match monospace:lang=ja NotoSansCJK-Regular.ttc: "Noto Sans Mono CJK JP" "Regular" [mfabian@localhost ~]$ fc-match monospace:lang=en DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" [mfabian@localhost ~]$ fc-match monospace:lang=am FreeSerif.ttf: "FreeSerif" "Regular" [mfabian@localhost ~]$ cat /etc/fedora-release Fedora release 31 (Thirty One) [mfabian@localhost ~]$ Maybe there is no monospace font for Amharic ☹ This makes gnome-terminal look weird in am_ET.UTF-8 locale, see screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1781372] New: [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1781372 Bug ID: 1781372 Summary: [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:75f531706153dfdd85ddf0be1692b26d7940fb0d;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: daniel(a)demus.dk 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-4.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: ibus-daemon --panel disable -r --xim crash_function: invoke_set_property_in_idle_cb executable: /usr/bin/ibus-daemon journald_cursor: s=c4148406e0464aa6b028a69dbd858103;i=2332cb;b=9b80660c325a4e97b03f82a722e4c4df;m=49832e189;t=59943b5e4b38d;x=d732a9d65ff2477 kernel: 5.3.14-300.fc31.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 13

[Fedora-i18n-bugs] [Bug 1752858] New: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1752858 Bug ID: 1752858 Summary: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit Product: Fedora Version: 31 Status: NEW Component: lohit-devanagari-fonts Assignee: petersen(a)redhat.com Reporter: psatpute(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, sshedmak(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1615839 --> https://bugzilla.redhat.com/attachment.cgi?id=1615839&action=edit Image showing rendering issue Description of problem: Combination र्श्व is not rendering correctly in gedit/harfbuzz. But it works properly in Firefox Version-Release number of selected component (if applicable): lohit-devanagari-fonts 2.95.4-9 harfbuzz-2.6.0-1 How reproducible: Evertime Steps to Reproduce: 1. Open Terminal 2. Type commng: hb-view /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf र्श्व 3. Observe result Actual results: Reph not getting form. Expected results: Expected Reph should get formed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1730242] New: unable to see ibus-sayura in Region panel
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1730242 Bug ID: 1730242 Summary: unable to see ibus-sayura in Region panel Product: Fedora Version: rawhide Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: pnemade(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: On Fedora 30 updated Silverblue system, I layered ibus-sayura package. Then tried to add it via Region panel. I cannot see it listed there. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Layer ibus-sayura package 2. reboot or you can ibus restart 3. try to add Sayura input using Region panel Actual results: There is no entry for Sayura in Region panel Expected results: It should allow to select Sayura Additional info: As I did not see Sayura, I executed "ibus write-cache" Then, I executed [parag@f30sb ~]$ ibus read-cache|grep -i sayura <description>Sayura Component</description> <exec>/usr/libexec/ibus-engine-sayura --ibus</exec> <textdomain>ibus-sayura</textdomain> <path mtime="0" >/usr/share/ibus/component/sayura.xml</path> <name>sayura</name> <longname>Sayura</longname> <description>Sayura Input Method</description> <icon>/usr/share/ibus-sayura/icons/ibus-sayura.png</icon> Then, [parag@f30sb ~]$ ibus list-engine|grep -i sayura no output for above command -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1689745] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1689745 Bug ID: 1689745 Summary: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: robinlee.sysu(a)gmail.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: Crash when updating system Version-Release number of selected component: ibus-libpinyin-1.11.0-2.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=cc3b4d7aa103497a99d675649b9ae013;i=94c7;b=13573ad620e541ff8cacc1ad1ceca0c3;m=eea6a32;t=584549ca4b236;x=245f7212fc098115 kernel: 5.0.0-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #8 g_settings_real_change_event at ../gio/gsettings.c:391 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1614 #12 _g_closure_invoke_va at ../gobject/gclosure.c:873 #15 settings_backend_path_changed at ../gio/gsettings.c:466 Potential duplicate: bug 1649100 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1758852] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1758852 Bug ID: 1758852 Summary: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599;VAR IANT_ID=workstation; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: neoh.ys(a)gmail.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 Version-Release number of selected component: ibus-libpinyin-1.11.1-2.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=d0bfbd77a305433ab20ca800db00de73;i=1c977;b=a298c5cc72eb401d9e2263a3bc469e87;m=163503887a;t=59436eaaf2c10;x=ab8ddda419eaa95f kernel: 5.3.2-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2300 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #4 g_cclosure_marshal_VOID__STRINGv at ../gobject/gmarshal.c:1462 #5 _g_closure_invoke_va at ../gobject/gclosure.c:873 #8 g_settings_real_change_event at ../gio/gsettings.c:392 #9 _g_cclosure_marshal_BOOLEAN__POINTER_INTv at ../gio/gmarshal-internal.c:426 #10 _g_closure_invoke_va at ../gobject/gclosure.c:873 #13 settings_backend_path_changed at ../gio/gsettings.c:467 Potential duplicate: bug 1689745 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1738159] New: tomoe depends on Python 2
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1738159 Bug ID: 1738159 Summary: tomoe depends on Python 2 Product: Fedora Version: rawhide Status: NEW Component: tomoe Assignee: pwu(a)redhat.com Reporter: lbalhar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Blocks: 1698500 (F31_PY2REMOVAL) Target Milestone: --- Classification: Fedora Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#In… Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for tomoe's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to tomoe. If you need anything from us, or something is unclear, please mention it here. Thank you. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1698500 [Bug 1698500] F31 Mass Python 2 Package Removal -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1779586] New: [abrt] ibus-table: g_settings_schema_get_value(): python3.7 killed by SIGTRAP
by bugzilla＠redhat.com 15 Sep '20

15 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1779586 Bug ID: 1779586 Summary: [abrt] ibus-table: g_settings_schema_get_value(): python3.7 killed by SIGTRAP Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:004184fdd6fa1b8e4e49df86a1c57ac5847dd204;VAR IANT_ID=workstation; Component: ibus-table Assignee: mfabian(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.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 Version-Release number of selected component: ibus-table-1.9.21-5.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-10030.slice/session-2.scope cmdline: /usr/bin/python3 /usr/share/ibus-table/engine/main.py --profile --ibus crash_function: g_settings_schema_get_value executable: /usr/bin/python3.7 journald_cursor: s=c0d79f79862b4941981f04495d4f8245;i=8bf219;b=16aabd8bda544929bc6ad65c9e902988;m=37114158;t=5985239b337cb;x=955981e5440c8c5d kernel: 5.3.12-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 10030 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #4 g_settings_schema_get_value at ../gio/gsettingsschema.c:973 #6 g_settings_schema_key_init at ../gio/gsettingsschema.c:1253 #7 g_settings_set_value at ../gio/gsettings.c:1578 #8 ffi_call_unix64 at ../src/x86/unix64.S:76 #9 ffi_call at ../src/x86/ffi64.c:525 #10 pygi_invoke_c_callable at ../gi/pygi-invoke.c:690 #11 pygi_function_cache_invoke at ../gi/pygi-cache.c:863 #12 pygi_callable_info_invoke at ../gi/pygi-invoke.c:770 #13 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:770 #14 _Py_CheckRecursionLimit -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1672442] New: Bug that will not accept input from keyboard
by bugzilla＠redhat.com 02 Sep '20

02 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1672442 Bug ID: 1672442 Summary: Bug that will not accept input from keyboard Product: Fedora Version: 29 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: qqke6wd9k(a)apricot.ocn.ne.jp 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 input characters, sometimes this bug occurs, the PC will not accept input from the keyboard morever. Since it accepts mouse operation, logout and shutdown are possible. When I log out and re-login, PC is able to accept only direct input (English). Also, the IME icon on the task bar is lost. It will also be impossible to switch input modes. I am a Japanese user, but when after login, I cannot enter Japanese characters. After this bug occurrence, only English characters can be entered. Version-Release number of selected component (if applicable): How reproducible: everyday Steps to Reproduce: 1.Open an application that can enter letters (eg gedit or Firefox) 2.keep typing characters until this bug occurs. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1750891] New: font cache not getting update on Silverblue 31?
by bugzilla＠redhat.com 01 Aug '20

01 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1750891 Bug ID: 1750891 Summary: font cache not getting update on Silverblue 31? Product: Fedora Version: 31 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: pnemade(a)redhat.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: I have this system state [parag@localhost ~]$ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi langpacks-hi libreoffice-core ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi libreoffice-core [parag@localhost ~]$ rpm-ostree db diff ostree diff commit from: rollback deployment (0ad271d38c5aa4e1ce194ea625f83862d2c317774d96ba9b94d53c5324133265) ostree diff commit to: booted deployment (61f7aea98b458e53e42e85131e62ad7c84f80592676f28949cc5aa411e34ff55) Added: glibc-langpack-hi-2.30-1.fc31.x86_64 google-noto-sans-devanagari-ui-vf-fonts-20181223-6.fc31.noarch google-noto-sans-devanagari-vf-fonts-20181223-6.fc31.noarch hyphen-hi-1:0.7.0-14.fc31.noarch langpacks-core-hi-2.0-6.fc31.noarch langpacks-hi-2.0-6.fc31.noarch libreoffice-help-hi-1:6.3.1.2-1.fc31.x86_64 libreoffice-langpack-hi-1:6.3.1.2-1.fc31.x86_64 samyak-devanagari-fonts-1.2.2-22.fc31.noarch samyak-fonts-common-1.2.2-22.fc31.noarch [parag@localhost ~]$ fc-list :lang=hi /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf: Lohit Devanagari:style=Regular /usr/share/fonts/google-droid/DroidSansDevanagari-Regular.ttf: Droid Sans:style=Regular [parag@localhost ~]$ Version-Release number of selected component (if applicable): fontconfig-2.13.92-2.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. on F31, install any langpacks which will install additional fonts packages like langpacks-hi 2. execute fc-list :lang=hi 3. Actual results: "fc-list :lang=hi" output remained same Expected results: "fc-list :lang=hi" should included rencently installed font packages as well Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Fedora-i18n-bugs] [Bug 1770450] New: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
by bugzilla＠redhat.com 23 Jun '20

23 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1770450 Bug ID: 1770450 Summary: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample .conf", line 6: unknown element "reset-dirs" Product: Fedora Version: 30 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: lhaastdaiz(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 When upgrading to fontconfig-2.13.1-9.fc30.x86_64, dnf emits this warning: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs" $ cat -n /usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf 1 <?xml version="1.0"?> 2 <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> 3 <fontconfig> 4 <description>Re-define fonts dirs sample</description> 5 6 <reset-dirs /> 7 <dir prefix="xdg">fonts</dir> 8 9 </fontconfig> -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1767499] New: Very bad kerning for Tahoma in Fedora 31
by bugzilla＠redhat.com 09 May '20

09 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1767499 Bug ID: 1767499 Summary: Very bad kerning for Tahoma in Fedora 31 Product: Fedora Version: 31 Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: aros(a)gmx.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 Created attachment 1631087 --> https://bugzilla.redhat.com/attachment.cgi?id=1631087&action=edit Tahoma as rendered by Pango 1.44 in Fedora 31 This is how Tahoma font is rendered in Fedora 31. After downgrading to pango-1.43.0-4.fc30.x86_64.rpm the issue disappears. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Fedora-i18n-bugs] [Bug 1737785] New: CVE-2019-1010238 pango: heap based buffer overflow can be used to get code execution
by bugzilla＠redhat.com 30 Apr '20

30 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1737785 Bug ID: 1737785 Summary: CVE-2019-1010238 pango: heap based buffer overflow can be used to get code execution Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: high Priority: high Assignee: security-response-team(a)redhat.com Reporter: mrehak(a)redhat.com CC: caillon+fedoraproject(a)gmail.com, eng-i18n-bugs(a)redhat.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: Other Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass invalid utf-8 strings to functions like pango_itemize. External References: https://packetstormsecurity.com/files/153838/USN-4081-1.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Fedora-i18n-bugs] [Bug 1766554] New: [abrt] stardict: g_type_check_instance_cast(): stardict killed by SIGSEGV
by bugzilla＠redhat.com 29 Apr '20

29 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1766554 Bug ID: 1766554 Summary: [abrt] stardict: g_type_check_instance_cast(): stardict killed by SIGSEGV Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:5cf2cd39fc416e272716f2eb0f77e4d5284fe46b;VAR IANT_ID=workstation; Component: stardict Assignee: psatpute(a)redhat.com Reporter: viktar_siarheichyk(a)epam.com 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 Version-Release number of selected component: stardict-3.0.6-12.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: stardict crash_function: g_type_check_instance_cast executable: /usr/bin/stardict journald_cursor: s=f0aac7fcdfad43228e20c09dae141664;i=5f22c;b=1e80a38b7b604a3192855143705cdc2d;m=2335667c1;t=5960abe948f7d;x=9e8c5aa0ed83d3fe kernel: 5.3.7-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at ../gobject/gtype.c:4057 #1 DictManageDlg::Show at dictmanagedlg.cpp:2803 #2 AppCore::PopupDictManageDlg() at stardict.cpp:1967 #7 gtk_real_button_released at gtkbutton.c:1712 #12 gtk_button_button_release at gtkbutton.c:1604 #14 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:84 #19 gtk_widget_event_internal at gtkwidget.c:5017 #20 gtk_widget_event at gtkwidget.c:4814 #21 gtk_propagate_event at gtkmain.c:2503 #22 gtk_main_do_event at gtkmain.c:1698 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1784430] New: Please package python3-polib for EPEL 8
by bugzilla＠redhat.com 15 Apr '20

15 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1784430 Bug ID: 1784430 Summary: Please package python3-polib for EPEL 8 Product: Fedora EPEL Version: epel8 Status: NEW Component: python-polib Assignee: suanand(a)redhat.com Reporter: vtrefny(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: diegobz(a)gmail.com, dingyichen(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, ivazqueznet(a)gmail.com, moez.roy(a)gmail.com, reallylongword(a)gmail.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora It's available for EPEL 7 and it would be nice to have it for CentOS/RHEL 8 too. I'm packager and I can help as a co-maintainer if needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1735152] New: eclipse-nls: FTBFS in Fedora rawhide/f31
by bugzilla＠redhat.com 10 Apr '20

10 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1735152 Bug ID: 1735152 Summary: eclipse-nls: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-nls Assignee: sean+rh(a)flanigan.org Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, sean+rh(a)flanigan.org Blocks: 1732841 Target Milestone: --- Classification: Fedora eclipse-nls failed to build from source in Fedora rawhide/f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=36633177 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-nls at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, eclipse-nls will be orphaned. Before branching of Fedora 32, eclipse-nls will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1732841 [Bug 1732841] (F31FTBFS) - Fedora 31 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Fedora-i18n-bugs] [Bug 1739051] New: tomoe-gtk depends on Python 2
by bugzilla＠redhat.com 10 Apr '20

10 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1739051 Bug ID: 1739051 Summary: tomoe-gtk depends on Python 2 Product: Fedora Version: rawhide Status: NEW Component: tomoe-gtk Assignee: extras-orphan(a)fedoraproject.org Reporter: lbalhar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, extras-orphan(a)fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 1698500 (F31_PY2REMOVAL) Target Milestone: --- Classification: Fedora Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#In… Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for tomoe-gtk's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to tomoe-gtk. If you need anything from us, or something is unclear, please mention it here. Thank you. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1698500 [Bug 1698500] F31 Mass Python 2 Package Removal -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1711631] New: [abrt] ibus-libpinyin: pinyin_save(pinyin_context_t*)(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 10 Apr '20

10 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1711631 Bug ID: 1711631 Summary: [abrt] ibus-libpinyin: pinyin_save(pinyin_context_t*)(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:2907b6d4b730ec4a10a6bea50fea98c87d3a4241;VAR IANT_ID=workstation; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: leftmostcat(a)gmail.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 Version-Release number of selected component: ibus-libpinyin-1.11.0-2.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save(pinyin_context_t*) executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=f9047c3871b9426fb1457b843e4962ba;i=2be43;b=a2c85faaa45f4919a598643806057a19;m=10704f78ad;t=58937579e8528;x=34c91ce58520a188 kernel: 5.0.16-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 pinyin_save(pinyin_context_t*) at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData(char const*) at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, _GVariant*) at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback(_GSettings*, char const*, PY::LibPinyinConfig*) at /usr/include/c++/9/bits/char_traits.h:300 Potential duplicate: bug 1579078 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1748187] New: cannot install the best update candidate for package liberation-fonts-1:2.00.5-3.fc30.noarch
by bugzilla＠redhat.com 07 Apr '20

07 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748187 Bug ID: 1748187 Summary: cannot install the best update candidate for package liberation-fonts-1:2.00.5-3.fc30.noarch Product: Fedora Version: 30 Hardware: x86_64 OS: Linux Status: NEW Component: liberation-narrow-fonts Severity: high Assignee: vishalvijayraghavan(a)gmail.com Reporter: sascha(a)peilicke.de QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: $ sudo dnf upgrade --best --allowerasing --skip-broken Last metadata expiration check: 0:01:01 ago on Di 03 Sep 2019 08:17:06 CEST. Error: Problem: cannot install the best update candidate for package liberation-fonts-1:2.00.5-3.fc30.noarch - cannot install both liberation-fonts-1:2.00.5-1.fc30.noarch and liberation-fonts-1:2.00.5-3.fc30.noarch - problem with installed package liberation-narrow-fonts-1.07.6-1.fc30.noarch - cannot install the best update candidate for package liberation-narrow-fonts-1.07.6-1.fc30.noarch $ dnf list installed | grep liberation liberation-fonts.noarch 1:2.00.5-3.fc30 @updates liberation-fonts-common.noarch 1:2.00.5-3.fc30 @updates liberation-mono-fonts.noarch 1:2.00.5-3.fc30 @updates liberation-narrow-fonts.noarch 1.07.6-1.fc30 @fedora liberation-sans-fonts.noarch 1:2.00.5-3.fc30 @updates liberation-serif-fonts.noarch 1:2.00.5-3.fc30 @updates -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1761089] New: Request to package fcitx and other fcitx libraries on EPEL 8
by bugzilla＠redhat.com 06 Apr '20

06 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1761089 Bug ID: 1761089 Summary: Request to package fcitx and other fcitx libraries on EPEL 8 Product: Fedora EPEL Version: epel8 Status: NEW Component: fcitx Assignee: liangsuilong(a)gmail.com Reporter: jatin1812(a)protonmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, i(a)cicku.me, liangsuilong(a)gmail.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora We do have fcitx in EPEL 7 repos, RHEL 8/ CentOS 8 need fcitx in EPEL 8 repositories :) -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Fedora-i18n-bugs] [Bug 1770072] New: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/glassy/.local/share/ibus-typing-booster/data'
by bugzilla＠redhat.com 01 Apr '20

01 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1770072 Bug ID: 1770072 Summary: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/glassy/.local/share/ibus-typing-booster/data' Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:2670921efebf7bcad72573b1e26a7af7ab099357;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: ropermantena(a)protonmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-typing-booster-2.7.0-1.fc31 Additional info: reporter: libreport-2.10.1 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml crash_function: makedirs exception_type: FileExistsError executable: /usr/share/ibus-typing-booster/engine/main.py interpreter: python3-3.7.5-1.fc31.x86_64 kernel: 5.3.8-300.fc31.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/glassy/.local/share/ibus-typing-booster/data' Traceback (most recent call last): File "/usr/share/ibus-typing-booster/engine/main.py", line 34, in <module> import factory File "/usr/share/ibus-typing-booster/engine/factory.py", line 32, in <module> import hunspell_table File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 45, in <module> import itb_emoji File "/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 78, in <module> USER_DATADIR = itb_util.xdg_save_data_path('ibus-typing-booster/data') File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 3487, in xdg_save_data_path return xdg.BaseDirectory.save_data_path(*resource) File "/usr/lib/python3.7/site-packages/xdg/BaseDirectory.py", line 70, in save_data_path os.makedirs(path) File "/usr/lib64/python3.7/os.py", line 221, in makedirs mkdir(name, mode) FileExistsError: [Errno 17] File exists: '/home/glassy/.local/share/ibus-typing-booster/data' Local variables in innermost frame: name: '/home/glassy/.local/share/ibus-typing-booster/data' mode: 511 exist_ok: False head: '/home/glassy/.local/share/ibus-typing-booster' tail: 'data' cdir: '.' -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Fedora-i18n-bugs] [Bug 1762523] New: Please build scim in normal EPEL8
by bugzilla＠redhat.com 06 Mar '20

06 Mar '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762523 Bug ID: 1762523 Summary: Please build scim in normal EPEL8 Product: Fedora EPEL Version: epel7 Status: NEW Component: scim Assignee: pwu(a)redhat.com Reporter: tdawson(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Please build scim in EPEL8 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1767691] New: [abrt] ibus: _sighandler(): ibus-x11 killed by SIGABRT
by bugzilla＠redhat.com 18 Feb '20

18 Feb '20

https://bugzilla.redhat.com/show_bug.cgi?id=1767691 Bug ID: 1767691 Summary: [abrt] ibus: _sighandler(): ibus-x11 killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:44f14558d1ec49dea0179699b613cdb85862261f;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: luya(a)fedoraproject.org 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: Normal browsing Version-Release number of selected component: ibus-1.5.21-3.fc31 Additional info: reporter: libreport-2.11.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/libexec/ibus-x11 --kill-daemon crash_function: _sighandler executable: /usr/libexec/ibus-x11 journald_cursor: s=b5fa959f9f9b43c79b7363914655333d;i=228c;b=b0f7b0646ee64534be10cf35e79392ae;m=16bd6b623;t=59640f126938a;x=557f40dc940b3985 kernel: 5.3.7-301.fc31.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 5

[Fedora-i18n-bugs] [Bug 1697211] New: [abrt] imsettings: g_hash_table_lookup_node(): imsettings-daemon killed by SIGABRT
by bugzilla＠redhat.com 28 Jan '20

28 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1697211 Bug ID: 1697211 Summary: [abrt] imsettings: g_hash_table_lookup_node(): imsettings-daemon killed by SIGABRT Product: Fedora Version: 29 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:c4df6f808c8e833fc02448adc172b67850913d2b; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: milan.kerslager(a)pslib.cz QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: imsettings-1.7.3-6.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-daemon crash_function: g_hash_table_lookup_node executable: /usr/libexec/imsettings-daemon journald_cursor: s=25e9e854390e4073b28b24d7c7aa8774;i=5a91;b=036096806eb64446a528e45c95a91bef;m=25b8918;t=5858478b4ec7d;x=4599a78d8c33b842 kernel: 5.0.5-200.fc29.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 33

[Fedora-i18n-bugs] [Bug 1786199] New: build of google-roboto-fonts for EPEL 8
by bugzilla＠redhat.com 19 Jan '20

19 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1786199 Bug ID: 1786199 Summary: build of google-roboto-fonts for EPEL 8 Product: Fedora EPEL Version: epel8 Status: NEW Component: google-roboto-fonts Assignee: dtardon(a)redhat.com Reporter: breno(a)tembosocial.com QA Contact: extras-qa(a)fedoraproject.org CC: dtardon(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Hi, I would like to ask a build of google-roboto-fonts for EPEL 8. Would you mind requesting the branches and build them? I've built them myself for testing, no issues at all. Please, let me know if I can be of any help. Thank you very much. - Breno -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1767995] New: Request to package im-chooser for EPEL 8
by bugzilla＠redhat.com 18 Jan '20

18 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1767995 Bug ID: 1767995 Summary: Request to package im-chooser for EPEL 8 Product: Fedora Version: 31 Status: NEW Component: im-chooser Assignee: tagoh(a)redhat.com Reporter: jatin1812(a)protonmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Please provide im-chooser for EPEL 8 for use on CentOS 8 and RHEL 8. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1774899] New: gettext-devel missing dependency on diffutils package
by bugzilla＠redhat.com 13 Jan '20

13 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1774899 Bug ID: 1774899 Summary: gettext-devel missing dependency on diffutils package Product: Fedora Version: rawhide Status: NEW Component: gettext Assignee: petersen(a)redhat.com Reporter: bnocera(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, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora gettext-devel-0.20.1-2.fc31.x86_64 When trying to use autopoint without the diffutils package installed: ./autogen.sh --prefix=/usr --libdir=/usr/lib64 && make && sudo make install autoreconf: Entering directory `.' autoreconf: running: autopoint --force /usr/bin/autopoint: line 677: cmp: command not found Copying file ABOUT-NLS /usr/bin/autopoint: line 677: cmp: command not found Copying file config.rpath /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found Copying file m4/extern-inline.m4 /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found /usr/bin/autopoint: line 677: cmp: command not found Copying file po/Makefile.in.in /usr/bin/autopoint: line 677: cmp: command not found Copying file po/Makevars.template /usr/bin/autopoint: line 677: cmp: command not found Copying file po/Rules-quot /usr/bin/autopoint: line 677: cmp: command not found Copying file po/boldquot.sed /usr/bin/autopoint: line 677: cmp: command not found Copying file po/en(a)boldquot.header /usr/bin/autopoint: line 677: cmp: command not found Copying file po/en(a)quot.header /usr/bin/autopoint: line 677: cmp: command not found Copying file po/insert-header.sin /usr/bin/autopoint: line 677: cmp: command not found Copying file po/quot.sed /usr/bin/autopoint: line 677: cmp: command not found Copying file po/remove-potcdate.sin autoreconf: running: aclocal --force --install -I m4 ${ACLOCAL_FLAGS} ^Cautoreconf: aclocal terminated by signal: 2 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1786527] New: update to 1.5.3 release
by bugzilla＠redhat.com 11 Jan '20

11 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1786527 Bug ID: 1786527 Summary: update to 1.5.3 release Product: Fedora Version: rawhide Status: NEW Component: ibus-hangul Assignee: pwu(a)redhat.com Reporter: petersen(a)redhat.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: ibus-hangul-1.5.3 was released last month. It would be good to get it into Fedora. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1771526] New: fcitx input method is not working with default shell zsh
by bugzilla＠redhat.com 11 Jan '20

11 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1771526 Bug ID: 1771526 Summary: fcitx input method is not working with default shell zsh Product: Fedora Version: 31 Status: NEW Component: imsettings Assignee: tagoh(a)redhat.com Reporter: djraymond1(a)naver.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Happening after changing default shell from bash to zsh. fcitx always shows up no input window. So that, I can't change my input language. Setting default shell as zsh made fcitx not working. This seems like happening like this : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905129 I searched for of it, and found that zsh does not allow "for", so there was a same problem on ubuntu im-config, before version 0.36 This problem looks very similar to it. After few minutes using my computer, I got a message: Giving up to bring the process up because main Input Method process for FCITX rapidly died many times. See $XDG_CACHE_HOME/imsettings/log for more details. (...and I couldn't find the log file) I've checked and tried to add export ~~~ on .zshrc, and it's same. This was same as ubuntu im-config what I've mentioned before. Version-Release number of selected component (if applicable): imsettings x86_64 1.8.1-2.fc31 fcitx x86_64 4.2.9.6-6.fc31 (fcitx-hangul x86_64 0.3.1-7.fc31) zsh x86_64 5.7.1-4.fc31 How reproducible:All Steps to Reproduce: 1.Install fcitx + your language of fcitx, set it up 2.change shell from bash to zsh 3.restart computer, it happens. Actual results: Cannot change language, No input Window, seems export not working. Expected results:Just works well Additional info: Using KDE Plasma workspace. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1768311] New: [abrt] imsettings: g_mutex_lock(): imsettings-daemon killed by SIGSEGV
by bugzilla＠redhat.com 07 Jan '20

07 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1768311 Bug ID: 1768311 Summary: [abrt] imsettings: g_mutex_lock(): imsettings-daemon killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:306ca4522cde8dfac2023cfb1322a1924c487273; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: lists(a)nerdbynature.de QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: imsettings-1.8.1-2.fc31 Additional info: reporter: libreport-2.10.1 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/imsettings-daemon crash_function: g_mutex_lock executable: /usr/libexec/imsettings-daemon journald_cursor: s=5969806ae8934c8b974f2e25b5e368d0;i=905;b=513a13d4d0244018aaf34bc69abce311;m=59751182;t=5967acddabf56;x=2a2f38baf92c96a9 kernel: 5.3.7-301.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 g_mutex_lock at ../glib/gthread-posix.c:1363 #1 xfconf_cache_set_property_reply_handler at xfconf-cache.c:611 #2 g_task_return_now at ../gio/gtask.c:1212 #3 complete_in_idle_cb at ../gio/gtask.c:1226 Potential duplicate: bug 1665761 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1782436] New: [abrt] imsettings: imsettings-daemon killed by SIGSEGV
by bugzilla＠redhat.com 24 Dec '19

24 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1782436 Bug ID: 1782436 Summary: [abrt] imsettings: imsettings-daemon killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d2b4b359b6da4682fab000fbd7c50eeb610e11ca;VAR IANT_ID=workstation; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: thetejenkins(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: imsettings-1.8.1-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.1\x2dcom.redhat.imsettings.slice/dbus-:1.1-com.redhat.imsettings@0.service cmdline: /usr/libexec/imsettings-daemon executable: /usr/libexec/imsettings-daemon journald_cursor: s=6e3a44f56807477cba75c45efc2cbb6c;i=ccd53;b=996e7b8a796549c39609541129b00b82;m=24acca7aa0;t=5996e6548fa18;x=2e3017a204cfaf6c kernel: 5.3.14-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 ?? #1 g_tree_find_node at ../glib/gtree.c:1106 #2 g_tree_lookup at ../glib/gtree.c:847 #3 xfconf_cache_set_property_reply_handler at xfconf-cache.c:624 #4 g_task_return_now at ../gio/gtask.c:1212 #5 complete_in_idle_cb at ../gio/gtask.c:1226 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Fedora-i18n-bugs] [Bug 1779077] New: [abrt] imsettings: g_system_thread_wait(): imsettings-daemon killed by SIGSEGV
by bugzilla＠redhat.com 24 Dec '19

24 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1779077 Bug ID: 1779077 Summary: [abrt] imsettings: g_system_thread_wait(): imsettings-daemon killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:16ff0b976a24c14408d0e3659745f3b76fb4ae86; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: vladimirtest(a)ya.ru QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: imsettings-1.8.1-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 3 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/imsettings-daemon crash_function: g_system_thread_wait executable: /usr/libexec/imsettings-daemon journald_cursor: s=d6ad36e8c5234ca28a1e049fb29bdada;i=6d3;b=15ee52afaf804abab1933586716f51fe;m=1936b4a;t=598c81b220f24;x=62184227ff8a3d68 kernel: 5.3.7-301.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 g_system_thread_wait at ../glib/gthread-posix.c:1235 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1722851] New: imsettings-daemon crashed in g_mutex_lock with X2Go and MATE
by bugzilla＠redhat.com 24 Dec '19

24 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1722851 Bug ID: 1722851 Summary: imsettings-daemon crashed in g_mutex_lock with X2Go and MATE Product: Fedora Version: 30 Hardware: x86_64 OS: Linux Status: NEW Component: imsettings Severity: medium Assignee: tagoh(a)redhat.com Reporter: rkudyba(a)fordham.edu QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora rpm -q x2goserver x2goserver-4.1.0.4-0.0x2go1.0.git20190621.1766.heuler.fc30.x86_64 rpm -q imsettings imsettings-1.8.1-1.fc30.x86_64 5.0.17-300.fc30.x86_64 We also use NIS authetication. Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:26 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:26 ourworkstation journal[15099]: atk-bridge: GetRegisteredEvents returned message with unknown signature Jun 21 09:33:26 ourworkstation journal[15099]: atk-bridge: get_device_events_reply: unknown signature Jun 21 09:33:26 ourworkstation journal[15099]: atk-bridge: get_device_events_reply: unknown signature Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.gnome.evolution.dataserver.Sources5' Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:26 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:26 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.gnome.evolution.dataserver.Calendar7' requested by ':1.33' (uid=6105 pid=14844 comm="/usr/libexec/evolution-data-server/evolution-alarm") Jun 21 09:33:27 ourworkstation systemd[1]: Started dbus-:1.9-org.mate.SettingsDaemon.DateTimeMechanism@4.service. Jun 21 09:33:27 ourworkstation journal[15099]: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node button, owner GtkToggleButton) Jun 21 09:33:27 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.gnome.GConf' requested by ':1.53' (uid=6105 pid=15208 comm="/usr/libexec/pulse/gconf-helper ") Jun 21 09:33:27 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.gnome.GConf' Jun 21 09:33:27 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.gnome.evolution.dataserver.Calendar7' Jun 21 09:33:27 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.gnome.evolution.dataserver.AddressBook9' requested by ':1.52' (uid=6105 pid=15172 comm="/usr/libexec/evolution-calendar-factory ") Jun 21 09:33:28 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9' Jun 21 09:33:30 ourworkstation xdg-desktop-portal-kde[15100]: qt.qpa.xcb: X server does not support XInput 2 Jun 21 09:33:31 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:31 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:31 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:31 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.freedesktop.impl.portal.desktop.kde' Jun 21 09:33:32 ourworkstation xdg-desktop-portal-kde[15100]: qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 167, resource id: 143, major code: 130 (Unknown), minor code: 47 Jun 21 09:33:32 ourworkstation journal[15100]: AT-SPI: Could not obtain desktop path or name Jun 21 09:33:32 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:32 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:32 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:32 ourworkstation journal[15100]: atk-bridge: GetRegisteredEvents returned message with unknown signature Jun 21 09:33:32 ourworkstation journal[15100]: atk-bridge: get_device_events_reply: unknown signature Jun 21 09:33:32 ourworkstation journal[15100]: atk-bridge: get_device_events_reply: unknown signature Jun 21 09:33:32 ourworkstation journal[14859]: Failed connect to PipeWire: Couldn't connect PipeWire remote Jun 21 09:33:32 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.freedesktop.portal.Desktop' Jun 21 09:33:32 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:32 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:32 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:33 ourworkstation caja[14768]: [N-A] Caja-Actions Menu Extender 1.8.3 initializing... Jun 21 09:33:33 ourworkstation systemd[1]: Starting Package management dnf daemon... Jun 21 09:33:33 ourworkstation caja[14768]: [N-A] Caja-Actions Tracker 1.8.3 initializing... Jun 21 09:33:33 ourworkstation systemd[1]: Started Package management dnf daemon. Jun 21 09:33:33 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:33 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:33 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:34 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:34 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:34 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:35 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.gtk.vfs.Metadata' requested by ':1.22' (uid=6105 pid=14768 comm="caja ") Jun 21 09:33:35 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.gtk.vfs.Metadata' Jun 21 09:33:38 ourworkstation systemd[1]: dnfdaemon.service: Succeeded. Jun 21 09:33:39 ourworkstation com.redhat.imsettings[14681]: [ 1561124019.814453]: IMSettings-Daemon[14868]: INFO: Attempting to switch IM to IBus [lang=en_US.UTF-8, desktop=MATE, update=false] Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.093470]: GLib[14868]: DEBUG: posix_spawn avoided (fd close requested) Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.109461]: IMSettings-Daemon[14868]: WARNING **: Child process exited with code 1 Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.110309]: IMSettings-Daemon[14868]: INFO: no need to invoke any auxiliary process for IBus Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.111218]: IMSettings-Daemon[14868]: INFO: Starting the main process for IBus [lang:en_US.UTF-8] Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.112049]: GLib[14868]: DEBUG: posix_spawn avoided (workdir specified) (fd close requested) (child_setup specified) Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.117844]: IMSettings-Daemon[14868]: INFO: Started IBus: [process: /usr/bin/ibus-daemon -r --xim, lang: en_US.UTF-8, pid: 15549, id: 12, time: 2019-06-21T13:33:40.117800Z Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.119844]: IMSettings-MATE-GSettings backend[14868]: INFO: Setting up ibus:xim as gtk+ immodule Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.120816]: IMSettings-GSettings backend[14868]: INFO: Setting up ibus:xim as gtk+ immodule Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.319065]: IMSettings-Qt backend[14868]: INFO: Setting up ibus as Qt immodule Jun 21 09:33:40 ourworkstation com.redhat.imsettings[14681]: [ 1561124020.324493]: IMSettings-XFCE backend[14868]: INFO: Setting up ibus:xim as gtk+ immodule Jun 21 09:33:40 ourworkstation kernel: imsettings-daem[14868]: segfault at 40 ip 00007f876295cce9 sp 00007fff0c0379a8 error 6 in libglib-2.0.so.0.6000.4[7f87628dc000+82000] Jun 21 09:33:40 ourworkstation kernel: Code: 00 5d e9 7a 29 fd ff 66 2e 0f 1f 84 00 00 00 00 00 48 8b 7f 30 e8 77 01 f8 ff eb d4 0f 1f 44 00 00 f3 0f 1e fa b8 01 00 00 00 <f0> 0f c1 07 85 c0 74 0f e9 da f6 ff ff 66 2e 0f 1f 84 00 00 00 00 Jun 21 09:33:40 ourworkstation systemd[1]: Started Process Core Dump (PID 15554/UID 0). Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.portal.IBus' requested by ':1.63' (uid=6105 pid=15549 comm="/usr/bin/ibus-daemon -r --xim ") Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:40 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:40 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Successfully activated service 'org.freedesktop.portal.IBus' Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:40 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:40 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=6105 pid=14692 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha") Jun 21 09:33:40 ourworkstation dbus-daemon[14681]: [session uid=6105 pid=14679] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jun 21 09:33:40 ourworkstation dbus-broker-launch[14692]: Activation request for 'org.a11y.atspi.Registry' failed. Jun 21 09:33:41 ourworkstation systemd-coredump[15556]: Process 14868 (imsettings-daem) of user 6105 dumped core. Stack trace of thread 14868: #0 0x00007f876295cce9 g_mutex_lock (libglib-2.0.so.0) #1 0x00007f8761210ba5 n/a (libxfconf-0.so.3) #2 0x00007f8762af4c0a n/a (libgio-2.0.so.0) #3 0x00007f8762af4c4d n/a (libgio-2.0.so.0) #4 0x00007f876290d7db n/a (libglib-2.0.so.0) #5 0x00007f8762910edd g_main_context_dispatch (libglib-2.0.so.0) #6 0x00007f8762911270 n/a (libglib-2.0.so.0) #7 0x00007f87629115a3 g_main_loop_run (libglib-2.0.so.0) #8 0x00005639b5009cc7 main (imsettings-daemon) #9 0x00007f87626fbf33 __libc_start_main (libc.so.6) #10 0x00005639b5009d4e _start (imsettings-daemon) Stack trace of thread 14889: #0 0x00007f87627c85c7 __poll (libc.so.6) #1 0x00007f87629111de n/a (libglib-2.0.so.0) #2 0x00007f8762911313 g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8761252a9d n/a (libdconfsettings.so) #4 0x00007f876293a4e2 n/a (libglib-2.0.so.0) #5 0x00007f87628a65a2 start_thread (libpthread.so.0) #6 0x00007f87627d3303 __clone (libc.so.6) Stack trace of thread 14869: #0 0x00007f87627c85c7 __poll (libc.so.6) #1 0x00007f87629111de n/a (libglib-2.0.so.0) #2 0x00007f8762911313 g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f8762911361 n/a (libglib-2.0.so.0) #4 0x00007f876293a4e2 n/a (libglib-2.0.so.0) #5 0x00007f87628a65a2 start_thread (libpthread.so.0) #6 0x00007f87627d3303 __clone (libc.so.6) Stack trace of thread 14870: #0 0x00007f87627c85c7 __poll (libc.so.6) #1 0x00007f87629111de n/a (libglib-2.0.so.0) #2 0x00007f87629115a3 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f8762b5dd5a n/a (libgio-2.0.so.0) #4 0x00007f876293a4e2 n/a (libglib-2.0.so.0) #5 0x00007f87628a65a2 start_thread (libpthread.so.0) #6 0x00007f87627d3303 __clone (libc.so.6) Stack trace of thread 15552: #0 0x00007f87627cdfad syscall (libc.so.6) #1 0x00007f876295cf4e g_cond_wait_until (libglib-2.0.so.0) #2 0x00007f87628e2031 n/a (libglib-2.0.so.0) #3 0x00007f876293b06a n/a (libglib-2.0.so.0) #4 0x00007f876293a4e2 n/a (libglib-2.0.so.0) #5 0x00007f87628a65a2 start_thread (libpthread.so.0) #6 0x00007f87627d3303 __clone (libc.so.6) Jun 21 09:33:41 ourworkstation systemd[1]: systemd-coredump(a)6-15554-0.service: Succeeded. Jun 21 09:33:43 ourworkstation abrt-server[15615]: Lock file '.lock' is locked by process 8649 Jun 21 09:33:44 ourworkstation abrt-notification[15659]: Process 14868 (imsettings-daemon) crashed in g_mutex_lock() Jun 21 09:33:52 ourworkstation pulseaudio[14881]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Jun 21 09:33:52 ourworkstation systemd[1]: systemd-hostnamed.service: Succeeded. Jun 21 09:33:53 ourworkstation org.freedesktop.Tracker1[14681]: OK Jun 21 09:33:57 ourworkstation systemd[1]: dbus-:1.9-org.mate.SettingsDaemon.DateTimeMechanism@4.service: Succeeded. Jun 21 09:34:29 ourworkstation dbus-daemon[9812]: [session uid=1201 pid=9810] Activating service name='org.freedesktop.Tracker1' requested by ':1.33' (uid=1201 pid=9946 comm="/usr/libexec/tracker-miner-fs ") Jun 21 09:34:29 ourworkstation dbus-daemon[9812]: [session uid=1201 pid=9810] Successfully activated service 'org.freedesktop.Tracker1' Jun 21 09:34:29 ourworkstation dbus-daemon[9812]: [session uid=1201 pid=9810] Activating service name='org.freedesktop.thumbnails.Cache1' requested by ':1.33' (uid=1201 pid=9946 comm="/usr/libexec/tracker-miner-fs ") Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer /usr/bin/gnome-epub-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer evince-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer /usr/bin/gnome-mobi-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer mate-thumbnail-font --size %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer gsf-office-thumbnailer -i %i -o %o -s %s Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer /usr/bin/totem-video-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer atril-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer gnome-thumbnail-font --size %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o Jun 21 09:34:30 ourworkstation org.freedesktop.thumbnails.Cache1[9812]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o gdb backtrace: Core was generated by `/usr/libexec/imsettings-daemon'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f876295cce9 in g_mutex_lock (mutex=mutex@entry=0x40) at ../glib/gthread-posix.c:1354 1354 ../glib/gthread-posix.c: No such file or directory. [Current thread is 1 (Thread 0x7f87622e7880 (LWP 14868))] (gdb) bt full #0 0x00007f876295cce9 in g_mutex_lock (mutex=mutex@entry=0x40) at ../glib/gthread-posix.c:1354 _g_boolean_var_ = <optimized out> #1 0x00007f8761210ba5 in xfconf_cache_set_property_reply_handler (proxy=0x5639b6ad6bb0 [GDBusProxy], res=0x5639b6aa68f0, user_data=user_data@entry=0x7f8754017c10) at xfconf-cache.c:608 cache = 0x0 old_item = 0x7f8754017c10 item = <optimized out> error = 0x0 result = <optimized out> #2 0x00007f8762af4c0a in g_task_return_now (task=0x5639b6aa68f0 [GTask]) at ../gio/gtask.c:1209 #3 0x00007f8762af4c4d in complete_in_idle_cb (task=task@entry=0x5639b6aa68f0) at ../gio/gtask.c:1223 #4 0x00007f876290d7db in g_idle_dispatch (source=source@entry=0x5639b6aaa470, callback=0x7f8762af4c40 <complete_in_idle_cb>, user_data=0x5639b6aa68f0) at ../glib/gmain.c:5627 again = <optimized out> #5 0x00007f8762910edd in g_main_dispatch (context=0x5639b6a9ab00) at ../glib/gmain.c:3189 dispatch = <optimized out> prev_source = 0x0 was_in_call = <optimized out> user_data = 0x5639b6aa68f0 callback = 0x7f8762af4c40 <complete_in_idle_cb> cb_funcs = 0x7f87629e3280 <g_source_callback_funcs> cb_data = 0x7f8754015880 need_destroy = <optimized out> source = 0x5639b6aaa470 current = 0x5639b6aa4680 i = 0 __FUNCTION__ = "g_main_dispatch" #6 0x00007f8762910edd in g_main_context_dispatch (context=context@entry=0x5639b6a9ab00) at ../glib/gmain.c:3854 #7 0x00007f8762911270 in g_main_context_iterate (context=0x5639b6a9ab00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:3927 max_priority = 0 timeout = 0 some_ready = 1 nfds = <optimized out> allocated_nfds = <optimized out> fds = 0x5639b6ae4750 #8 0x00007f87629115a3 in g_main_loop_run (loop=0x5639b6aa92c0) at ../glib/gmain.c:4123 __FUNCTION__ = "g_main_loop_run" #9 0x00005639b5009cc7 in main (argc=<optimized out>, argv=<optimized out>) at main.c:180 err = 0x0 arg_replace = 0 arg_no_logfile = 0 arg_xinputrcdir = 0x0 arg_xinputdir = 0x0 arg_homedir = 0x0 arg_moduledir = 0x0 loop = 0x5639b6aa92c0 ctx = <optimized out> entries = {{long_name = 0x5639b50113b8 "replace", short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x7fff0c037ba0, description = 0x5639b5011240 "Replace the instance of the imsettings daemon.", arg_description = 0x0}, {long_name = 0x5639b5010993 "xinputrcdir", short_name = 0 '\000', flags = 1, arg = G_OPTION_ARG_STRING, arg_data = 0x7fff0c037bb0, description = 0x5639b5011270 "Set the system-wide xinputrc directory (for debugging purpose)", arg_description = 0x5639b50113c0 "DIR"}, {long_name = 0x5639b50109b0 "xinputdir", short_name = 0 '\000', flags = 1, arg = G_OPTION_ARG_STRING, arg_data = 0x7fff0c037bb8, description = 0x5639b50112b0 "Set the IM configuration directory (for debugging purpose)", arg_description = 0x5639b50113c0 "DIR"}, {long_name = 0x5639b5010978 "homedir", short_name = 0 '\000', flags = 1, arg = G_OPTION_ARG_STRING, arg_data = 0x7fff0c037bc0, description = 0x5639b50112f0 "Set a home directory (for debugging purpose)", arg_description = 0x5639b50113c0 "DIR"}, {long_name = 0x5639b50109d6 "moduledir", short_name = 0 '\000', flags = 1, arg = G_OPTION_ARG_STRING, arg_data = 0x7fff0c037bc8, description = 0x5639b5011320 "Set the imsettings module directory (for debugging purpose)", arg_description = 0x5639b50113c0 "DIR"}, {long_name = 0x5639b50113c4 "no-logfile", short_name = 0 '\000', flags = 1, arg = G_OPTION_ARG_NONE, arg_data = 0x7fff0c037ba4, description = 0x5639b50113cf "Do not create a log file.", arg_description = 0x0}, {long_name = 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0, arg_description = 0x0}} connection = 0x5639b6a9b060 [GDBusConnection] -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1785548] New: Fedora 31 cannot use Courier 10 Pitch
by bugzilla＠redhat.com 24 Dec '19

24 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1785548 Bug ID: 1785548 Summary: Fedora 31 cannot use Courier 10 Pitch Product: Fedora Version: 31 Hardware: All OS: Linux Status: NEW Component: fontconfig Severity: high Assignee: tagoh(a)redhat.com Reporter: ercli(a)ucdavis.edu 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: After updating from Fedora 30 to Fedora 31, the Courier 10 Pitch font is no longer available, even if the package xorg-x11-fonts-Type1 is installed and fc-list command shows the font Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Make sure Fedora 31 is available (e.g. use Fedora Live CD) 2. sudo dnf install xorg-x11-fonts-Type1 3. fc-list | grep "Courier 10 Pitch" # make sure the font is available in fc-list 4. Open gedit, go to Preferences -> Fonts&Colors -> Edior font 5. Search for "Courier 10 Pitch". Actual results: Cannot find font "Courier 10 Pitch" Expected results: Can find font "Courier 10 Pitch" Additional info: * The font is also not fond on gnome-terminal, LibreOffice Writer, etc. * Works on Fedora 30 and lower. * If update from Fedora 30 to 31, then gnome-terminal and gedit will not be able to find the font, and all characters become a square with some hexadecimal numbers in it, like: +--+ +--+ |00| |00| |31| |32| +--+ +--+ -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1116676] filter keyboard layouts by geometry
by bugzilla＠redhat.com 17 Dec '19

17 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1116676 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1450591] po2l20n doesn't work
by bugzilla＠redhat.com 16 Dec '19

16 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1450591 Jens Petersen <petersen(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |FutureFeature Version|30 |rawhide -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1779129] New: [abrt] ibus-anthy-python: on_btn_dict_view_clicked(): main.py:1457:on_btn_dict_view_clicked:TypeError: can only concatenate str (not "list") to str
by bugzilla＠redhat.com 12 Dec '19

12 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1779129 Bug ID: 1779129 Summary: [abrt] ibus-anthy-python: on_btn_dict_view_clicked(): main.py:1457:on_btn_dict_view_clicked:TypeError: can only concatenate str (not "list") to str Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:7fd9487994a22353543467a8f4860de6905c7deb;VAR IANT_ID=workstation; Component: ibus-anthy Assignee: tfujiwar(a)redhat.com Reporter: julroy67(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: When trying to view the "Postal code conversion" dictionnary in the Dictionnary tab of ibus-anthy settings, this error pops up. Version-Release number of selected component: ibus-anthy-python-1.5.11-3.fc31 Additional info: reporter: libreport-2.11.3 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: python3 /usr/share/ibus-anthy/setup/main.py crash_function: on_btn_dict_view_clicked exception_type: TypeError executable: /usr/share/ibus-anthy/setup/main.py interpreter: python3-3.7.5-1.fc31.x86_64 kernel: 5.3.13-300.fc31.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: main.py:1457:on_btn_dict_view_clicked:TypeError: can only concatenate str (not "list") to str Traceback (most recent call last): File "/usr/share/ibus-anthy/setup/main.py", line 1457, in on_btn_dict_view_clicked self.__run_message_dialog(_("Your file does not exist: ") + dict_file, TypeError: can only concatenate str (not "list") to str Local variables in innermost frame: self: <__main__.AnthySetup object at 0x7fa20301e910> widget: <Gtk.Button object at 0x7fa2020c7910 (GtkButton at 0x55948849d340)> dict_file: ['/usr/share/ibus-anthy/dicts/zipcode.t'] selected_id: 'zipcode' -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1376060] [RFE] Transliterate Full name into correct User name in Users Spoke
by bugzilla＠redhat.com 12 Dec '19

12 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1376060 Vendula Poncova <vponcova(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vponcova(a)redhat.com Flags|needinfo?(anaconda-maint-li |needinfo?(Frodox(a)zoho.com) |st(a)redhat.com) | --- Comment #4 from Vendula Poncova <vponcova(a)redhat.com> --- Hello, I couldn't find a Python library that would provide this functionality and we are not going to implement it. However, the installer could skip the non-ASCII characters or generate an empty string instead of the invalid user name. What do you think? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1376060] [RFE] Transliterate Full name into correct User name in Users Spoke
by bugzilla＠redhat.com 11 Dec '19

11 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1376060 Adam Williamson <awilliam(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |awilliam(a)redhat.com Flags| |needinfo?(anaconda-maint-li | |st(a)redhat.com) --- Comment #3 from Adam Williamson <awilliam(a)redhat.com> --- So this is a feature request that makes sense, but I kinda doubt it's the sort of work anaconda team wants or has the resources to maintain. anaconda devs, maybe someone can take a quick look here and if this is not something you think it's feasible to do and maintain, close this as WONTFIX? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1778439] New: fcitx-cloudpinyin-0.3.7 is available
by bugzilla＠redhat.com 09 Dec '19

09 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1778439 Bug ID: 1778439 Summary: fcitx-cloudpinyin-0.3.7 is available Product: Fedora Version: rawhide Status: NEW Component: fcitx-cloudpinyin 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, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.3.7 Current version/release in rawhide: 0.3.5-6.fc31 URL: https://fcitx-im.org/wiki/Cloudpinyin 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/8007/ -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1778473] New: fcitx-4.2.9.7 is available
by bugzilla＠redhat.com 09 Dec '19

09 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1778473 Bug ID: 1778473 Summary: fcitx-4.2.9.7 is available Product: Fedora Version: rawhide Status: NEW Component: fcitx 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, i(a)cicku.me, liangsuilong(a)gmail.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 4.2.9.7 Current version/release in rawhide: 4.2.9.6-6.fc31 URL: https://fcitx-im.org/wiki/Fcitx 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/8004/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1778452] New: fcitx-qt5-1.2.4 is available
by bugzilla＠redhat.com 09 Dec '19

09 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1778452 Bug ID: 1778452 Summary: fcitx-qt5-1.2.4 is available Product: Fedora Version: rawhide Status: NEW Component: fcitx-qt5 Keywords: FutureFeature, Triaged Assignee: robinlee.sysu(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.2.4 Current version/release in rawhide: 1.2.3-10.fc32 URL: https://github.com/fcitx/fcitx-qt5 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/6513/ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1780080] New: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] Tiedosto on olemassa: '/var/lib/gdm/.local/share/ibus-typing-booster/data'
by bugzilla＠redhat.com 06 Dec '19

06 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1780080 Bug ID: 1780080 Summary: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] Tiedosto on olemassa: '/var/lib/gdm/.local/share/ibus-typing-booster/data' Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:ab5c53a974d0954de2e47e68851a9197a76e44db;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: ricky.tigg(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-typing-booster-2.7.2-1.fc31 Additional info: reporter: libreport-2.11.3 cgroup: 0::/user.slice/user-42.slice/user@42.service/gnome-shell-wayland.service cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml crash_function: makedirs exception_type: FileExistsError executable: /usr/share/ibus-typing-booster/engine/main.py interpreter: python3-3.7.5-1.fc31.x86_64 kernel: 5.3.11-300.fc31.x86_64 runlevel: N 5 type: Python3 uid: 42 Truncated backtrace: os.py:221:makedirs:FileExistsError: [Errno 17] Tiedosto on olemassa: '/var/lib/gdm/.local/share/ibus-typing-booster/data' Traceback (most recent call last): File "/usr/share/ibus-typing-booster/engine/main.py", line 34, in <module> import factory File "/usr/share/ibus-typing-booster/engine/factory.py", line 32, in <module> import hunspell_table File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 45, in <module> import itb_emoji File "/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 78, in <module> USER_DATADIR = itb_util.xdg_save_data_path('ibus-typing-booster/data') File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 3504, in xdg_save_data_path return xdg.BaseDirectory.save_data_path(*resource) File "/usr/lib/python3.7/site-packages/xdg/BaseDirectory.py", line 70, in save_data_path os.makedirs(path) File "/usr/lib64/python3.7/os.py", line 221, in makedirs mkdir(name, mode) FileExistsError: [Errno 17] Tiedosto on olemassa: '/var/lib/gdm/.local/share/ibus-typing-booster/data' Local variables in innermost frame: name: '/var/lib/gdm/.local/share/ibus-typing-booster/data' mode: 511 exist_ok: False head: '/var/lib/gdm/.local/share/ibus-typing-booster' tail: 'data' cdir: '.' -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1764520] New: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/liting/.local/share/ibus-typing-booster/data'
by bugzilla＠redhat.com 04 Dec '19

04 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1764520 Bug ID: 1764520 Summary: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/liting/.local/share/ibus-typing-booster/data' Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b46ec76f84c8b3b39dc8714416fdf9384c0a26db;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: 1419004855(a)qq.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I deleted my /home/user/.config directory and I could not use my Chinese input source after that Version-Release number of selected component: ibus-typing-booster-2.6.0-1.fc30 Additional info: reporter: libreport-2.10.0 cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml crash_function: makedirs exception_type: FileExistsError executable: /usr/share/ibus-typing-booster/engine/main.py interpreter: python3-3.7.3-1.fc30.x86_64 kernel: 5.0.9-301.fc30.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/liting/.local/share/ibus-typing-booster/data' Traceback (most recent call last): File "/usr/share/ibus-typing-booster/engine/main.py", line 33, in <module> import factory File "/usr/share/ibus-typing-booster/engine/factory.py", line 32, in <module> import hunspell_table File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 45, in <module> import itb_emoji File "/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 73, in <module> USER_DATADIR = itb_util.xdg_save_data_path('ibus-typing-booster/data') File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 3188, in xdg_save_data_path return xdg.BaseDirectory.save_data_path(*resource) File "/usr/lib/python3.7/site-packages/xdg/BaseDirectory.py", line 70, in save_data_path os.makedirs(path) File "/usr/lib64/python3.7/os.py", line 221, in makedirs mkdir(name, mode) FileExistsError: [Errno 17] File exists: '/home/liting/.local/share/ibus-typing-booster/data' Local variables in innermost frame: name: '/home/liting/.local/share/ibus-typing-booster/data' mode: 511 exist_ok: False head: '/home/liting/.local/share/ibus-typing-booster' tail: 'data' cdir: '.' -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Fedora-i18n-bugs] [Bug 1713963] New: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/uncle/.local/share/ibus-typing-booster/data'
by bugzilla＠redhat.com 04 Dec '19

04 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1713963 Bug ID: 1713963 Summary: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/uncle/.local/share/ibus-typing-booster/data' Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a57581355f40a89196828c901bccde0c5db8a7c4;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: satyendrax(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-typing-booster-2.6.1-1.fc30 Additional info: reporter: libreport-2.10.0 cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml crash_function: makedirs exception_type: FileExistsError executable: /usr/share/ibus-typing-booster/engine/main.py interpreter: python3-3.7.3-3.fc30.x86_64 kernel: 5.0.17-300.fc30.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/uncle/.local/share/ibus-typing-booster/data' Traceback (most recent call last): File "/usr/share/ibus-typing-booster/engine/main.py", line 33, in <module> import factory File "/usr/share/ibus-typing-booster/engine/factory.py", line 32, in <module> import hunspell_table File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 45, in <module> import itb_emoji File "/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 73, in <module> USER_DATADIR = itb_util.xdg_save_data_path('ibus-typing-booster/data') File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 3188, in xdg_save_data_path return xdg.BaseDirectory.save_data_path(*resource) File "/usr/lib/python3.7/site-packages/xdg/BaseDirectory.py", line 70, in save_data_path os.makedirs(path) File "/usr/lib64/python3.7/os.py", line 221, in makedirs mkdir(name, mode) FileExistsError: [Errno 17] File exists: '/home/uncle/.local/share/ibus-typing-booster/data' Local variables in innermost frame: name: '/home/uncle/.local/share/ibus-typing-booster/data' mode: 511 exist_ok: False head: '/home/uncle/.local/share/ibus-typing-booster' tail: 'data' cdir: '.' -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Fedora-i18n-bugs] [Bug 1779424] New: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/jsmestad/.local/share/ibus-typing-booster/data'
by bugzilla＠redhat.com 04 Dec '19

04 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1779424 Bug ID: 1779424 Summary: [abrt] ibus-typing-booster: makedirs(): os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/jsmestad/.local/share/ibus-typing-booster/data' Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:7b7d40d22cbb8615e54210a50242bd993561456f;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: justin.smestad(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I booted up and logged into Gnome. This message greeted me. Version-Release number of selected component: ibus-typing-booster-2.7.2-1.fc31 Additional info: reporter: libreport-2.11.3 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml crash_function: makedirs exception_type: FileExistsError executable: /usr/share/ibus-typing-booster/engine/main.py interpreter: python3-3.7.5-1.fc31.x86_64 kernel: 5.3.13-300.fc31.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: os.py:221:makedirs:FileExistsError: [Errno 17] File exists: '/home/jsmestad/.local/share/ibus-typing-booster/data' Traceback (most recent call last): File "/usr/share/ibus-typing-booster/engine/main.py", line 34, in <module> import factory File "/usr/share/ibus-typing-booster/engine/factory.py", line 32, in <module> import hunspell_table File "/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 45, in <module> import itb_emoji File "/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 78, in <module> USER_DATADIR = itb_util.xdg_save_data_path('ibus-typing-booster/data') File "/usr/share/ibus-typing-booster/engine/itb_util.py", line 3504, in xdg_save_data_path return xdg.BaseDirectory.save_data_path(*resource) File "/usr/lib/python3.7/site-packages/xdg/BaseDirectory.py", line 70, in save_data_path os.makedirs(path) File "/usr/lib64/python3.7/os.py", line 221, in makedirs mkdir(name, mode) FileExistsError: [Errno 17] File exists: '/home/jsmestad/.local/share/ibus-typing-booster/data' Local variables in innermost frame: name: '/home/jsmestad/.local/share/ibus-typing-booster/data' mode: 511 exist_ok: False head: '/home/jsmestad/.local/share/ibus-typing-booster' tail: 'data' cdir: '.' -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1637647] [ibus-typing-booster] In gnome Wayland, while deleting with backspace, previously entered keywords appear repetitively in gedit.
by bugzilla＠redhat.com 03 Dec '19

03 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1637647 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 --- Comment #5 from Mike FABIAN <mfabian(a)redhat.com> --- The bug still exists in Fedora 31. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1777400] New: ibus-libpinyin's "Fuzzy input" is not working for pinyin
by bugzilla＠redhat.com 03 Dec '19

03 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1777400 Bug ID: 1777400 Summary: ibus-libpinyin's "Fuzzy input" is not working for pinyin Product: Fedora Version: 31 Status: NEW Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: yanqiyu01(a)gmail.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 ibus-libpinin's settings, "fuzzy input"(may be other words in English, here it is "模糊音") only shows options for bopomofo but not showing options for pinyin. Version-Release number of selected component (if applicable): 1.11.1 How reproducible: Always. Steps to Reproduce: 1. Set input method to ibus-libpinyin, and go to its settings, enable all options(which are showing bopomofo) . 2. Type "指挥"（zhihui）by "zihui" 3. Actual results: Found "指挥" don't show as candidate Expected results: Fuzzy pinyin should work for pinyin: It should provide fuzzy pinyin settings and be able to handle typos such as zhihui/zihui. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1526467] Searching for emoji and selecting an emoji should jump to category
by bugzilla＠redhat.com 02 Dec '19

02 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1526467 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1526464] Make it possible to use cursors to select emojis
by bugzilla＠redhat.com 02 Dec '19

02 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1526464 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1526463] Make emoji selectable
by bugzilla＠redhat.com 02 Dec '19

02 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1526463 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1133127] The hotkey for switching to direct input mode should be configurable
by bugzilla＠redhat.com 02 Dec '19

02 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=1133127 Mike FABIAN <mfabian(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|30 |31 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 683325] pidgin freezes for some specific messages and window size
by bugzilla＠redhat.com 02 Dec '19

02 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=683325 --- Comment #15 from Peng Wu <pwu(a)redhat.com> --- Could someone provide one simple pango test case with C code to reproduce this bug? I think that test case can help debugging the pango code. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 683325] pidgin freezes for some specific messages and window size
by bugzilla＠redhat.com 01 Dec '19

01 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=683325 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tagoh(a)redhat.com |pwu(a)redhat.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 683325] pidgin freezes for some specific messages and window size
by bugzilla＠redhat.com 01 Dec '19

01 Dec '19

https://bugzilla.redhat.com/show_bug.cgi?id=683325 Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Version|17 |31 Resolution|CURRENTRELEASE |--- --- Comment #14 from Cristian Ciupitu <cristian.ciupitu(a)yahoo.com> --- Still happening with pidgin-2.13.0-15.fc31.x86_64 & pango-1.44.7-1.fc31.x86_64 but I don't know an easy way to reproduce it. It seems to be happen when I write longer messages which require at least two lines. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1773282] New: [abrt] ibus-rime: std::__shared_ptr_access<YAML::detail::node_data, (__gnu_cxx::_Lock_policy)2, false, false>::_M_get(): ibus-engine-rime killed by SIGSEGV
by bugzilla＠redhat.com 30 Nov '19

30 Nov '19

https://bugzilla.redhat.com/show_bug.cgi?id=1773282 Bug ID: 1773282 Summary: [abrt] ibus-rime: std::__shared_ptr_access<YAML::detail::node_data, (__gnu_cxx::_Lock_policy)2, false, false>::_M_get(): ibus-engine-rime killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:96e54405e111c846fc50f4505de090a9ffb6e7d3;VAR IANT_ID=kde; Component: ibus-rime Assignee: pwu(a)redhat.com Reporter: wiovitkb(a)abcd.zeroe.ml 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 Version-Release number of selected component: ibus-rime-1.3.0-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/libexec/ibus-engine-rime --ibus crash_function: std::__shared_ptr_access<YAML::detail::node_data, (__gnu_cxx::_Lock_policy)2, false, false>::_M_get executable: /usr/libexec/ibus-engine-rime journald_cursor: s=bb560ab30cac49968060f82b688be374;i=10e7d;b=76f23fdb2eca4ba68b1e9b7f802ffe8e;m=210858b;t=59783f3c93769;x=5a8b36a2170b9345 kernel: 5.3.11-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 std::__shared_ptr_access<YAML::detail::node_data, (__gnu_cxx::_Lock_policy)2, false, false>::_M_get at /usr/include/c++/9/bits/shared_ptr_base.h:1020 #1 std::__shared_ptr_access<YAML::detail::node_data, (__gnu_cxx::_Lock_policy)2, false, false>::operator-> at /usr/include/c++/9/bits/shared_ptr_base.h:1015 #2 YAML::detail::node_ref::type at /usr/include/yaml-cpp/node/detail/node_ref.h:25 #3 YAML::detail::node::type at /usr/include/yaml-cpp/node/detail/node.h:30 #4 YAML::Node::Type at /usr/include/yaml-cpp/node/impl.h:79 #5 rime::ConfigData::ConvertFromYaml at /usr/src/debug/librime-1.3.2-4.fc31.x86_64/src/rime/config/config_data.cc:252 #6 rime::ConfigData::LoadFromFile at /usr/src/debug/librime-1.3.2-4.fc31.x86_64/src/rime/config/config_data.cc:68 #7 rime::Config::LoadFromFile at /usr/include/c++/9/bits/shared_ptr_base.h:1020 #8 rime::InstallationUpdate::Run at /usr/include/boost/filesystem/path.hpp:435 #9 rime::Deployer::RunTask at /usr/src/debug/librime-1.3.2-4.fc31.x86_64/src/rime/deployer.cc:42 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1773818] New: ibus-engine-rime crash after start
by bugzilla＠redhat.com 30 Nov '19

30 Nov '19

https://bugzilla.redhat.com/show_bug.cgi?id=1773818 Bug ID: 1773818 Summary: ibus-engine-rime crash after start Product: Fedora Version: 31 Status: NEW Component: ibus-rime Severity: high Assignee: pwu(a)redhat.com Reporter: vtgoal(a)gmail.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: ibus-engine-rime after login gnome Version-Release number of selected component (if applicable): ibus-rime-1.3.0-3.fc31.x86_64 How reproducible: 100% Steps to Reproduce: 1. Login gnome 2. Switch to Rime input Actual results: Rime input doesn't work, crash message in dmesg Expected results: Additional info: dmesg: [Tue Nov 19 10:18:34 2019] traps: ibus-engine-rim[6850] general protection fault ip:7f8623a0c603 sp:7ffe4769a880 error:0 in librime.so.1.3.2[7f862396b000+157000] crash_function: rime::ConfigData::ConvertFromYaml(YAML::Node const&, rime::ConfigCompiler*) OS and kernel version: Fedora 31 Workstation, kernel-5.3.11-300.fc31.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs December 2019