https://bugzilla.redhat.com/show_bug.cgi?id=1790554
Bug ID: 1790554
Summary: Keyboard layout of Kana Kanji wont show up
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sumukher(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The keyboard layout for Kana Kanji Japanese doesnt show up
Version-Release number of selected component (if applicable):
Fedora-Rawhide-20200112.n.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install Fedora-Rawhide-20200112.n.0 WS from live boot
2. Open settings and navigate to Region and Language
3. Add Japanese Kana Kanji in the input source
4. Click the icon looking like an eye button which should open the keyboard
layout
Actual results:
Doesn't show up the keyboard layout
Expected results:
The keyboard layout should show up like it shows up for english
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1807534
Bug ID: 1807534
Summary: pyzy requires Python 2 to build
Product: Fedora
Version: rawhide
Status: NEW
Component: pyzy
Assignee: pwu(a)redhat.com
Reporter: pviktori(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
Blocks: 1803205 (BRPY27)
Target Milestone: ---
Classification: Fedora
Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's
now provided from the compat package `python27`.
Packages that only use Python 2 at build time, like pyzy, had a general
exception to keep using it in Fedora 31. Now, the dependency should be removed.
Let us know if you need any help investigating or removing the dependency.
(There are dozens of packages like this, so we didn't investigate this one
thoroughly. We assume you know the package best.)
If it's possible that the dependency won't be removed in Fedora 33. Please
request a FESCo exception. You can refer to the exception for mercurial as an
example: https://pagure.io/fesco/issue/2243
It's good to mention:
- What is the reason for the Python 2 build dependency?
- What are the upstream/community plans/timelines regarding Python 2?
- What is the guidance for porting the build 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?)
If you need anything from us, or something is unclear, please mention it here.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1803205
[Bug 1803205] Tracking: Packages BuildRequiring python27
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1787190
Bug ID: 1787190
Summary: Windows+ Space shortcut opened KRunner instead of
switch keyboard (ibus) in KDE plasma
Product: Fedora
Version: 31
Status: NEW
Component: kf5-plasma
Keywords: i18n
Assignee: me(a)dvratil.cz
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
jgrulich(a)redhat.com, kde-sig(a)lists.fedoraproject.org,
me(a)dvratil.cz, rdieter(a)gmail.com, than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
after updating KDE with Fedora 31, Windows+Space is opening 'Krunner', but not
switching keyboard (which is default shortcut for ibus keybaord switch).
Krunner is not running with Alt+F2
Krunner is running with Windows +F2
Version-Release number of selected component (if applicable):
plasma-desktop-5.17.4-1.fc31.x86_64
plasma-nm-openswan-5.17.4-1.fc31.x86_64
plasma-desktop-doc-5.17.4-1.fc31.noarch
plasma-browser-integration-5.17.4-1.fc31.x86_64
plasma-workspace-5.17.4-1.fc31.x86_64
plasma-nm-vpnc-5.17.4-1.fc31.x86_64
plasma-workspace-common-5.17.4-1.fc31.x86_64
plasma-nm-5.17.4-1.fc31.x86_64
plasma-workspace-geolocation-5.17.4-1.fc31.x86_64
plasma-milou-5.17.4-1.fc31.x86_64
plasma-integration-5.17.4-1.fc31.x86_64
plasma-discover-5.17.4-1.fc31.x86_64
plasma-nm-openvpn-5.17.4-1.fc31.x86_64
plasma-breeze-5.17.4-1.fc31.x86_64
plasma-drkonqi-5.17.4-1.fc31.x86_64
kdeplasma-addons-5.17.4-1.fc31.x86_64
plasma-user-manager-5.17.4-1.fc31.x86_64
plasma-pk-updates-0.3.2-4.fc31.x86_64
plasma-nm-l2tp-5.17.4-1.fc31.x86_64
plasma-nm-openconnect-5.17.4-1.fc31.x86_64
kf5-plasma-5.64.0-1.fc31.x86_64
plasma-workspace-geolocation-libs-5.17.4-1.fc31.x86_64
plasma-lookandfeel-fedora-5.17.4-1.fc31.noarch
plasma-nm-pptp-5.17.4-1.fc31.x86_64
plasma-workspace-libs-5.17.4-1.fc31.x86_64
plasma-systemsettings-5.17.4-1.fc31.x86_64
kde-settings-plasma-31.0-1.fc31.noarch
glibc-2.30-8.fc31.x86_64
glibc-langpack-pa-2.30-8.fc31.x86_64
glibc-langpack-en-2.30-8.fc31.x86_64
glibc-all-langpacks-2.30-8.fc31.x86_64
glibc-common-2.30-8.fc31.x86_6
ibus-setup-1.5.21-5.fc31.noarch
ibus-gtk3-1.5.21-5.fc31.x86_64
ibus-m17n-1.4.1-3.fc31.x86_64
ibus-gtk2-1.5.21-5.fc31.x86_64
ibus-qt-1.3.3-22.fc31.x86_64
ibus-libs-1.5.21-5.fc31.x86_64
ibus-1.5.21-5.fc31.x86_64
How reproducible:
Everytime after updating Fedora 31 KDE desktop with latest package
Steps to Reproduce:
1. Fresh install KDE Plasma with language (Punjabi, Hindi, any language using
iBus)
2. try to input by switching keyboard (ibus) pressing Windows+Space
3. sudo dnf update
4. Reboot
5. try to input by switching keyboard (ibus) pressing Windows+Space
Actual results:
Opened 'KRunner'
Expected results:
input keyboard layout should switch with 'Windows+space'.
Krunner should run with 'Alt+F2', which is not working
Additional info:
before updating, opened system setting -> Shortcut -> Global Shortcut - There
is NO krunner'
After update, system setting -> Shortcut -> Global Shortcut -> Krunner (this is
something new)
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1797926
Bug ID: 1797926
Summary: Korean Baekmuk fonts does not map missing glyphs to id
0
Product: Fedora
Version: 31
Hardware: All
OS: All
Status: NEW
Component: baekmuk-ttf-fonts
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: matt(a)nightrealms.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, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
From https://bugs.chromium.org/p/chromium/issues/detail?id=1042994
"So the font, does not map missing characters to a glyph id 0, missing glyph
id, but instead maps it to a glyph named '.null', glyph id 12505."
The result is that when Chrome tries to display the Korean characters listed at
http://www.alanwood.net/unicode/hangul-jamo-extended-b.html the characters come
out as blank.
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1805634
Bug ID: 1805634
Summary: Drop requirement for ibus-gtk2
Product: Fedora
Version: 32
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: akurtako(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
ibus package requires ibus-gtk2 which itself brings gtk2 which is not needed on
a numbef of machines. Can this Requires be dropped?
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1792714
Bug ID: 1792714
Summary: translate-toolkit-2.5.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Keywords: FutureFeature, Triaged
Assignee: petersen(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
mmraka(a)redhat.com, petersen(a)redhat.com,
suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.5.0
Current version/release in rawhide: 2.4.0-5.fc32
URL: http://toolkit.translatehouse.org/
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/3685/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1637647
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |ON_QA
--- Comment #9 from Fedora Update System <updates(a)fedoraproject.org> ---
ibus-typing-booster-2.8.1-1.fc32 has been pushed to the Fedora 32 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-049620fad5
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1637647
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |MODIFIED
--- Comment #6 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2020-049620fad5 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-049620fad5
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1637647
Mike FABIAN <mfabian(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1806696
--- Comment #9 from Greta Watson <greta_watson(a)stanfordalumni.org> ---
My system is up to date, with the exception of google-chrome-stable, which does
not have anything to do with cups. I updated yesterday. I uploaded several
files: the non-working file does not have the // characters at the start of
the file. the working file does have the // characters at the start of the
file, so the filter program apparently thinks it may be a C or C++ file, so it
prints.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1806696
--- Comment #8 from Zdenek Dohnal <zdohnal(a)redhat.com> ---
I'm not able to reproduce the issue on up-to-date F30 using your uploaded file
and ppd.
Wasn't a different file uploaded? Is your system up-to-date?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1806696
Zdenek Dohnal <zdohnal(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i18n-bugs(a)lists.fedoraproje
| |ct.org, tagoh(a)redhat.com
Component|cups |paps
Assignee|zdohnal(a)redhat.com |tagoh(a)redhat.com
--- Comment #7 from Zdenek Dohnal <zdohnal(a)redhat.com> ---
From the log:
Feb 25 06:46:19 sparky cupsd[7777]: Started filter
/usr/lib/cups/filter/texttopaps (PID 7795)
Feb 25 06:46:19 sparky cupsd[7777]: Started filter /usr/lib/cups/filter/gstopdf
(PID 7796)
Feb 25 06:46:19 sparky cupsd[7777]: Started filter
/usr/lib/cups/filter/pdftopdf (PID 7797)
Feb 25 06:46:19 sparky cupsd[7777]: Started filter
/usr/lib/cups/filter/gstoraster (PID 7798)
Feb 25 06:46:19 sparky cupsd[7777]: Started filter /usr/lib/cups/filter/hpcups
(PID 7799)
Feb 25 06:46:19 sparky cupsd[7777]: Started backend /usr/lib/cups/backend/hp
(PID 7800)
Feb 25 06:46:19 sparky cupsd[7777]: gstopdf argv[5] = 187 greta notworking.txt
1 finishings=3 number-up=1
job-uuid=urn:uuid:daea883b-765d-3cf1-6624-1306516eae74
job-originating-host-name=localhost date-time-at-creation=
date-time-at-processing= time-at-creation=1582641979
time-at-processing=1582641979 document-name-supplied=notworking.txt
Feb 25 06:46:19 sparky cupsd[7777]: PPD: /etc/cups/ppd/HP_Printer.ppd
Feb 25 06:46:19 sparky cupsd[7777]: OUTFORMAT=\"(null)\", so output format will
be CUPS/PWG Raster
Feb 25 06:46:19 sparky cupsd[7777]: STATE: -marker-supply-low-warning
Feb 25 06:46:19 sparky cupsd[7777]: pdftopdf: Last filter determined by the
PPD: hpcups; FINAL_CONTENT_TYPE: application/vnd.cups-raster => pdftopdf will
not log pages in page_log.
Feb 25 06:46:19 sparky cupsd[7777]: OUTFORMAT=\"PDF\", so output format will be
PDF
Feb 25 06:46:19 sparky cupsd[7777]: HP_Printer: Error while converting strings.
Feb 25 06:46:19 sparky cupsd[7777]: PID 7795 (/usr/lib/cups/filter/texttopaps)
stopped with status 1.
The error happens in texttopaps filter, which is part of paps package, I'll
reassign the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1450591
jibecfed <jean-baptiste(a)holcroft.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |ERRATA
Last Closed| |2020-02-25 12:49:03
--- Comment #3 from jibecfed <jean-baptiste(a)holcroft.fr> ---
as l20n was cancelled and replaced by fluent, do we still need to focus on
this? I don't think anybody use it.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1450591
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|petersen(a)redhat.com |suanand(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1803028
Bug ID: 1803028
Summary: ibus-table crashes when changing the punctuation width
or the letter width using the floating panel or the
menus
Product: Fedora
Version: 31
Status: NEW
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: ---
Link ID: Github mike-fabian/ibus-table/issues/26
Classification: Fedora
Always reproducible with ibus-table-1.9.24-1.fc31.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1799517
Bug ID: 1799517
Summary: ibus-chewing: FTBFS in Fedora rawhide/f32
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-chewing
Assignee: tfujiwar(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dingyichen(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Blocks: 1750908 (F32FTBFS)
Target Milestone: ---
Classification: Fedora
ibus-chewing failed to build from source in Fedora rawhide/f32
https://koji.fedoraproject.org/koji/taskinfo?taskID=41318234
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix ibus-chewing 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,
ibus-chewing will be orphaned. Before branching of Fedora 33,
ibus-chewing 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=1750908
[Bug 1750908] Fedora 32 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1804124
Gwyn Ciesla <gwync(a)protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2020-02-18 18:42:26
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1804124
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i18n-bugs(a)lists.fedoraproje
| |ct.org
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835376
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1647043
Bug 1647043 depends on bug 1647045, which changed state.
Bug 1647045 Summary: CVE-2018-18751 mingw-gettext: gettext: double free in default_add_message in read-catalog.c [epel-7]
https://bugzilla.redhat.com/show_bug.cgi?id=1647045
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |EOL
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1605054
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|VERIFIED |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2020-02-11 06:06:11
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1336042
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|VERIFIED |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2020-02-11 06:05:23
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1799518
Bug ID: 1799518
Summary: ibus-rime: FTBFS in Fedora rawhide/f32
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-rime
Assignee: pwu(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Blocks: 1750908 (F32FTBFS)
Target Milestone: ---
Classification: Fedora
ibus-rime failed to build from source in Fedora rawhide/f32
https://koji.fedoraproject.org/koji/taskinfo?taskID=41318235
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix ibus-rime 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,
ibus-rime will be orphaned. Before branching of Fedora 33,
ibus-rime 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=1750908
[Bug 1750908] Fedora 32 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1793460
Bug ID: 1793460
Summary: [abrt] ibus-typing-booster:
set_google_application_credentials():
main.py:3549:set_google_application_credentials:Attrib
uteError: 'SetupUI' object has no attribute
'_google_application_credentials_entry'
Product: Fedora
Version: 31
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:4a22d9d0f95a5aead38c33f5363b501996fee5eb;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: mfabian(a)redhat.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.5-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/setup/main.py
crash_function: set_google_application_credentials
exception_type: AttributeError
executable: /usr/share/ibus-typing-booster/setup/main.py
interpreter: python3-3.7.6-1.fc31.x86_64
kernel: 5.4.7-200.fc31.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
main.py:3549:set_google_application_credentials:AttributeError: 'SetupUI'
object has no attribute '_google_application_credentials_entry'
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/setup/main.py", line 1979, in
on_gsettings_value_changed
value, update_gsettings=False)
File "/usr/share/ibus-typing-booster/setup/main.py", line 3549, in
set_google_application_credentials
self._google_application_credentials_entry.set_text(
AttributeError: 'SetupUI' object has no attribute
'_google_application_credentials_entry'
Local variables in innermost frame:
self: <__main__.SetupUI object at 0x7f908566c370 (__main__+SetupUI at
0x5595a8282520)>
path: ''
update_gsettings: False
--
You are receiving this mail because:
You are on the CC list for the bug.