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=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=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=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=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=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=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=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=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=1715713
Bug ID: 1715713
Summary: [abrt] ibus: __poll(): ibus-daemon killed by SIGABRT
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:3762bf7397dfcdc0d227eab9d3c9f8588275c712;VAR
IANT_ID=workstation;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: noobusinghacks(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
happened at the same time as this
https://bugzilla.redhat.com/show_bug.cgi?id=1567645
Version-Release number of selected component:
ibus-1.5.19-16.fc29
Additional info:
reporter: libreport-2.10.0
backtrace_rating: 4
cmdline: ibus-daemon --xim --panel disable
crash_function: __poll
executable: /usr/bin/ibus-daemon
journald_cursor:
s=f82b3db13754497e9310ee2fd027e3bb;i=2b63;b=50f26a9fd7d644b2abe679f36a10238a;m=48602e00;t=58a24e988af8a;x=128fed0d5928463a
kernel: 5.0.17-200.fc29.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (3 frames)
#0 __poll at ../sysdeps/unix/sysv/linux/poll.c:29
#1 g_main_context_poll at gmain.c:4221
#4 bus_server_run at server.c:195
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1660522
Bug ID: 1660522
Summary: [abrt] ibus-anthy-python:
__update_anthy_convert_chars():
engine.py:1269:__update_anthy_convert_chars:TypeError:
can only concatenate str (not "NoneType") to str
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:68516d1ac979ea4a4ef53d1d33c98a5060591dde;VAR
IANT_ID=workstation;
Component: ibus-anthy
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, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-anthy-python-1.5.10-5.fc29
Additional info:
reporter: libreport-2.9.7
cmdline: python3 /usr/share/ibus-anthy/engine/main.py --ibus
crash_function: __update_anthy_convert_chars
exception_type: TypeError
executable: /usr/share/ibus-anthy/engine/main.py
interpreter: python3-3.7.1-4.fc29.x86_64
kernel: 4.19.5-300.fc29.x86_64
runlevel: N 5
type: Python3
uid: 10030
Truncated backtrace:
engine.py:1269:__update_anthy_convert_chars:TypeError: can only concatenate str
(not "NoneType") to str
Traceback (most recent call last):
File "/usr/share/ibus-anthy/engine/engine.py", line 1290, in __update
self.__update_convert_chars()
File "/usr/share/ibus-anthy/engine/engine.py", line 1213, in
__update_convert_chars
self.__update_anthy_convert_chars()
File "/usr/share/ibus-anthy/engine/engine.py", line 1269, in
__update_anthy_convert_chars
self.__convert_chars += text
TypeError: can only concatenate str (not "NoneType") to str
Local variables in innermost frame:
self: <engine.Engine object at 0x7f74fce16630 (engine+Engine at
0x558e39add170)>
pos: 0
i: 0
seg_index: -1
text: None
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1708013
Bug ID: 1708013
Summary: gettext-0.20 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Keywords: FutureFeature, Triaged
Assignee: panovotn(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jjanco(a)redhat.com, nphilipp(a)redhat.com,
panovotn(a)redhat.com, petersen(a)redhat.com,
praiskup(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.20
Current version/release in rawhide: 0.19.8.1-18.fc30
URL: http://www.gnu.org/software/gettext/
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/898/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1756997
Bug ID: 1756997
Summary: Request package for EPEL8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: zinnia
Assignee: pwu(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com, petersen(a)redhat.com,
pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
zinnia is required to build mozc on EPEL8. so please consider to import and
build the package on EPEL8. thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1737186
Bug ID: 1737186
Summary: enable introspection
Product: Fedora
Version: rawhide
Status: NEW
Component: harfbuzz
Assignee: pnemade(a)redhat.com
Reporter: mclasen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Pango now has api that provides access to harfbuzz objects. It would be nice to
make that available via introspection, but we can only do that if harfbuzz
introspection data is available.
So, please build harfbuzz with --with-gobject --enable-introspection
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1753042
Bug ID: 1753042
Summary: [abrt] imsettings: g_hash_table_lookup_node():
imsettings-daemon killed by SIGABRT
Product: Fedora
Version: 30
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:c4df6f808c8e833fc02448adc172b67850913d2b;VAR
IANT_ID=workstation;
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: yetoohappy(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
Description of problem:
I had system settings open to the keyboard shortcut editor for several hours, I
turned off both my monitors, I remoted in with nomachine, left that session
idle overnight, I closed the nomachine session, turned on both of my monitors
and found that my machine had froze and I needed to do a hard shutdown then
restart.
Version-Release number of selected component:
imsettings-1.8.1-1.fc30
Additional info:
reporter: libreport-2.10.1
backtrace_rating: 4
cmdline: /usr/libexec/imsettings-daemon
crash_function: g_hash_table_lookup_node
executable: /usr/libexec/imsettings-daemon
journald_cursor:
s=2da537a4bb2b406fb6ca1a849db112c7;i=92b;b=c3573035fa344b19b730895bef1a164d;m=3a6034c;t=592b679da5d38;x=9900af4f0b35af3d
kernel: 5.2.11-200.fc30.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Potential duplicate: bug 1697211
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1756197
Bug ID: 1756197
Summary: [RFE] Please build a package to install Mozc via EPEL8
Product: Fedora EPEL
Version: el6
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: ykatabam(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
Please build a package to install Mozc input system via EPEL8.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1757207
Bug ID: 1757207
Summary: harfbuzz-2.6.2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: harfbuzz
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.6.2
Current version/release in rawhide: 2.6.1-2.fc32
URL: https://www.freedesktop.org/wiki/HarfBuzz
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/1299/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1751940
Bug ID: 1751940
Summary: CVE-2019-14822 ibus: missing authorization allows
local attacker to access the input bus of another user
[fedora-all]
Product: Fedora
Version: 30
Status: NEW
Component: ibus
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: tfujiwar(a)redhat.com
Reporter: rschiron(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
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #26 from Fedora Update System <updates(a)fedoraproject.org> ---
liberation-narrow-fonts-1.07.6-2.fc31 has been pushed to the Fedora 31 stable
repository. If problems still persist, please make note of it in this bug
report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1551073
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1444357
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1417814
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1345824
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1345808
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1330162
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfabian(a)redhat.co |
|m) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1665761
Bug ID: 1665761
Summary: [abrt] imsettings: g_mutex_lock(): imsettings-daemon
killed by SIGSEGV
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:306ca4522cde8dfac2023cfb1322a1924c487273;
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: joaomfloriano(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
Description of problem:
I logged into Fedora and its error sequence was reported. I did not run or open
any application
Version-Release number of selected component:
imsettings-1.7.3-6.fc29
Additional info:
reporter: libreport-2.9.7
backtrace_rating: 4
cmdline: /usr/libexec/imsettings-daemon
crash_function: g_mutex_lock
executable: /usr/libexec/imsettings-daemon
journald_cursor:
s=79f49ceccf4744e99f013bda7b2b469e;i=6e1;b=35544eed6b7b4c5591e1c02456652103;m=1185506c;t=57f5ce41b707e;x=50618820333031c0
kernel: 4.19.13-300.fc29.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 g_mutex_lock at gthread-posix.c:1343
#1 xfconf_cache_set_property_reply_handler at xfconf-cache.c:608
#2 g_task_return_now at gtask.c:1148
#3 g_task_return at gtask.c:1206
#4 reply_cb at gdbusproxy.c:2586
#5 g_task_return_now at gtask.c:1148
#6 g_task_return at gtask.c:1206
#7 g_dbus_connection_call_done at gdbusconnection.c:5713
#8 g_task_return_now at gtask.c:1148
#9 complete_in_idle_cb at gtask.c:1162
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1717190
Bug ID: 1717190
Summary: [abrt] imsettings: g_atomic_ref_count_compare():
imsettings-daemon killed by SIGSEGV
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:873b1f950e6e0270d1224c57f39e50fa91912dcc;
Component: imsettings
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
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_atomic_ref_count_compare
executable: /usr/libexec/imsettings-daemon
global_pid: 3412
kernel: 5.0.17-200.fc29.x86_64
runlevel: N 5
type: CCpp
uid: 0
Truncated backtrace:
Thread no. 1 (10 frames)
#0 g_atomic_ref_count_compare at grefcount.c:284
#1 g_hash_table_lookup_node at ghash.c:1371
#2 g_hash_table_remove_internal at ghash.c:1371
#3 xfconf_cache_set_property_reply_handler at xfconf-cache.c:620
#4 g_task_return_now at gtask.c:1148
#5 g_task_return at gtask.c:1206
#6 reply_cb at gdbusproxy.c:2586
#7 g_task_return_now at gtask.c:1148
#8 g_task_return at gtask.c:1206
#9 g_dbus_connection_call_done at gdbusconnection.c:5713
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
--- Comment #14 from Akira TAGOH <tagoh(a)redhat.com> ---
We have a fontconfig config file per packages. nothing we can do for this in
fontconfig. and gnu-free-fonts has lower priority enough (they are assigned to
69) and google-noto-sans-gurmukhi-fonts (new default font for Punjabi, changed
in f31. see Bug#1554988) has a higher priority than gnu-free-fonts (they are
assigned to 65-0).
In fact, on Fedora-Workstation-Live-x86_64-31-20190909.n.0.iso:
$ fc-match :lang=pa
NotoSansGurmukhi-Regular.ttf: "Noto Sans Gurmukhi" "Regular"
The font selection itself works as expected. please retest and provide more
information.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1736952
Bug ID: 1736952
Summary: vt323-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: vt323-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
vt323-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36638009
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix vt323-fonts 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,
vt323-fonts will be orphaned. Before branching of Fedora 32,
vt323-fonts 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=1735978
Bug ID: 1735978
Summary: labelleaurore-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: labelleaurore-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
labelleaurore-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36634790
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix labelleaurore-fonts 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,
labelleaurore-fonts will be orphaned. Before branching of Fedora 32,
labelleaurore-fonts 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=1735437
Bug ID: 1735437
Summary: WritRecogn: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: WritRecogn
Assignee: extras-orphan(a)fedoraproject.org
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dingyichen(a)gmail.com, extras-orphan(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
WritRecogn failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36631879
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix WritRecogn 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,
WritRecogn will be orphaned. Before branching of Fedora 32,
WritRecogn 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=1736956
Bug ID: 1736956
Summary: wallpoet-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: wallpoet-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
wallpoet-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36638031
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix wallpoet-fonts 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,
wallpoet-fonts will be orphaned. Before branching of Fedora 32,
wallpoet-fonts 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=1736653
Bug ID: 1736653
Summary: shadowsintolight-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: shadowsintolight-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
shadowsintolight-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36637611
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix shadowsintolight-fonts 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,
shadowsintolight-fonts will be orphaned. Before branching of Fedora 32,
shadowsintolight-fonts 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=1736580
Bug ID: 1736580
Summary: reeniebeanie-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: reeniebeanie-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
reeniebeanie-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36637407
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix reeniebeanie-fonts 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,
reeniebeanie-fonts will be orphaned. Before branching of Fedora 32,
reeniebeanie-fonts 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=1736138
Bug ID: 1736138
Summary: monofett-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: monofett-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
monofett-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36635592
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix monofett-fonts 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,
monofett-fonts will be orphaned. Before branching of Fedora 32,
monofett-fonts 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=1735062
Bug ID: 1735062
Summary: cyreal-wireone-fonts: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: cyreal-wireone-fonts
Assignee: jujens(a)jujens.eu
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, jujens(a)jujens.eu
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
cyreal-wireone-fonts failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36632718
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix cyreal-wireone-fonts 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,
cyreal-wireone-fonts will be orphaned. Before branching of Fedora 32,
cyreal-wireone-fonts 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=1734917
Bug ID: 1734917
Summary: WritRecogn: FTBFS in Fedora rawhide/f31
Product: Fedora
Version: rawhide
Status: NEW
Component: WritRecogn
Assignee: extras-orphan(a)fedoraproject.org
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dingyichen(a)gmail.com, extras-orphan(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com
Blocks: 1732841
Target Milestone: ---
Classification: Fedora
WritRecogn failed to build from source in Fedora rawhide/f31
https://koji.fedoraproject.org/koji/taskinfo?taskID=36631879
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix WritRecogn 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,
WritRecogn will be orphaned. Before branching of Fedora 32,
WritRecogn 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=1667951
Bug ID: 1667951
Summary: google-roboto-mono-fonts is needed in rawhide (f30)
Product: Fedora
Version: rawhide
Status: NEW
Component: google-roboto-mono-fonts
Assignee: extras-orphan(a)fedoraproject.org
Reporter: mgansser(a)online.de
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-orphan(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
need the package for a review in rawhide (f30).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1707734
Bug ID: 1707734
Summary: fc-validate should return non-zero value when missing
glyph for language coverage
Product: Fedora
Version: rawhide
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: pwu(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:
When use fc-validate to check missing glyph for language coverage,
if some glyphs are missing, fc-validate still returns zero value.
Version-Release number of selected component (if applicable):
fontconfig-2.13.1-3.fc29.x86_64
How reproducible:
Run fc-validate -l zh_cn
/usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc
and fc-validate -l th /usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc
Steps to Reproduce:
1. run fc-validate against some fonts which missing glyph coverage
Actual results:
fc-validate returns zero value.
Expected results:
fc-validate returns non-zero value if any font face missing glyph coverage.
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=1750732
Bug ID: 1750732
Summary: config can't be turned on if no
$HOME/.config/fontconfig/conf.d is available
Product: Fedora
Version: 31
Status: NEW
Component: fonts-tweak-tool
Assignee: tagoh(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com,
petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
On the Fontconfig recipes tab, the config can't be turned on if no
$HOME/.config/fontconfig/conf.d is available. once it is created, it works
fine.
Version-Release number of selected component (if applicable):
fonts-tewak-tool-0.4.5-5.fc31.x86_64
libeasyfc-0.14.0-5.fc31.x86_64
libeasyfc-gobject-0.14.0-5.fc31.x86_64
How reproducible:
always
Steps to Reproduce:
1.run fonts-tweak-tool
2.go to the fontconfig recipes tab
3.turn on some config
Actual results:
switch is turned off immediately
Expected results:
switch should keeps turned on.
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=1592335
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version| |Canna-3.7p3-56.fc29
Resolution|--- |ERRATA
Last Closed| |2019-09-19 01:52:44
--- Comment #6 from Fedora Update System <updates(a)fedoraproject.org> ---
Canna-3.7p3-56.fc29 has been pushed to the Fedora 29 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1752862
Martin Pitt <mpitt(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |POST
CC| |mpitt(a)redhat.com
--- Comment #3 from Martin Pitt <mpitt(a)redhat.com> ---
Fixed in https://github.com/cockpit-project/cockpit/pull/12841
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1717958
Bug 1717958 depends on bug 1751940, which changed state.
Bug 1751940 Summary: CVE-2019-14822 ibus: missing authorization allows local attacker to access the input bus of another user [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=1751940
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Resolution|--- |ERRATA
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1748803
Bug ID: 1748803
Summary: liberation-fonts.noarch should pull in
liberation-*-fonts or be dropped
Product: Fedora
Version: rawhide
Status: NEW
Component: liberation-fonts
Assignee: petersen(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
liberation-fonts.noarch is an empty package which does nothing.
It should pull in its subpackages (or otherwise be dropped).
How reproducible:
100%
Steps to Reproduce:
1. dnf install liberation-fonts
Actual results:
no files installed
Expected results:
liberation-sans, liberation-serif-fonts, liberation-mono-fonts to be pulled in.
(Maybe even liberation-narrow-fonts??)
Additional info:
I think this is already the case in RHEL: we should the same in Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1752862
Matej Marušák <mmarusak(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmarusak(a)redhat.com
Assignee|mpitt(a)redhat.com |mmarusak(a)redhat.com
--- Comment #2 from Matej Marušák <mmarusak(a)redhat.com> ---
Thanks for the report.
I noticed a while ago that we do not translate all strings due to not ideal
settings in our scripts that generate strings for translations. When I tried to
fix it, I hit bug in one of utilities we use.
I only kept it in my head but now I documented it and opened issue about it in
upstream: https://github.com/cockpit-project/cockpit/issues/12835
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1752862
Pravin Satpute <psatpute(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=1619530
--- Comment #9 from Mike FABIAN <mfabian(a)redhat.com> ---
So anaconda should make an exception for Georgian not to automatically
capitalize the first letter.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1651736
Mike FABIAN <mfabian(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|29 |31
--- Comment #2 from Mike FABIAN <mfabian(a)redhat.com> ---
The problem still exists in Fedora 31.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1689037
--- Comment #39 from Adam Williamson <awilliam(a)redhat.com> ---
Hmm, here it is apparently happening on x86_64 even:
https://openqa.fedoraproject.org/tests/451841
but it seems we didn't store the coredump on that occasion :(
sigh, I love these bugs. I did check if harfbuzz regressed, but it doesn't look
like it (the revert still looks to be applied).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744377
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version| |fontconfig-2.13.92-3.fc31
Resolution|--- |ERRATA
Last Closed| |2019-09-15 00:25:45
--- Comment #6 from Fedora Update System <updates(a)fedoraproject.org> ---
fontconfig-2.13.92-3.fc31 has been pushed to the Fedora 31 stable repository.
If problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744970
--- Comment #5 from Fedora Update System <updates(a)fedoraproject.org> ---
weston-6.0.0-3.fc31 has been pushed to the Fedora 31 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744970
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version| |weston-6.0.0-3.fc31
Resolution|--- |ERRATA
Last Closed| |2019-09-14 00:09:48
--- Comment #4 from Fedora Update System <updates(a)fedoraproject.org> ---
weston-6.0.0-3.fc31 has been pushed to the Fedora 31 stable repository. If
problems still persist, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1689037
--- Comment #38 from Michael Catanzaro <mcatanzaro(a)gnome.org> ---
(In reply to Adam Williamson from comment #37)
> etc. etc. Is this still useless and indicative of memory corruption we're
> not finding?
Yes indeed, sadly:
(In reply to Michael Catanzaro from comment #4)
> I've seen this many times before. It's never a problem in
> gtk_css_static_style_compute_value. Always turns out to be memory corruption
> in some unrelated code. Could be Anaconda, could be GTK, but the backtrace
> is almost certainly useless. You need to catch this under asan or valgrind
> to have any chance.
Memory corruption is the absolute worst. Very hard to track down. :/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1689037
--- Comment #37 from Adam Williamson <awilliam(a)redhat.com> ---
So, something like this is happening again :/
But this time even with PYTHONMALLOC=debug set, the backtrace is in gtk_css:
#0 0x0000ffff81bd34c4 in __GI___waitpid (pid=<optimized out>,
stat_loc=stat_loc@entry=0xffffef7a8d6c,
options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1 0x0000ffff7184f154 in sync_signal_handler (signum=<optimized out>) at
isys.c:143
#2 <signal handler called>
#3 0x0000000000000000 in ?? ()
#4 0x0000ffff60221f30 in gtk_css_static_style_compute_value
(style=0xaaaaf1fc6660, provider=0xaaaaf4d71260,
parent_style=0xaaaaf2a00be0, id=52, specified=0xffff64030a40, section=0x0)
at gtkcssstaticstyle.c:237
#5 0x0000ffff6020dadc in _gtk_css_lookup_resolve
(lookup=lookup@entry=0xaaaaf5431d90,
provider=provider@entry=0xaaaaf4d71260, style=style@entry=0xaaaaf1fc6660,
parent_style=parent_style@entry=0xaaaaf2a00be0) at gtkcsslookup.c:122
#6 0x0000ffff60221e30 in gtk_css_static_style_new_compute
(provider=0xaaaaf4d71260,
matcher=matcher@entry=0xffffef7aa278, parent=parent@entry=0xaaaaf2a00be0)
at gtkcssstaticstyle.c:195
#7 0x0000ffff6020fff0 in gtk_css_node_create_style (cssnode=0xaaaaf4e22740) at
gtkcssnode.c:371
#8 gtk_css_node_real_update_style (cssnode=0xaaaaf4e22740, change=8598372560,
timestamp=107356270,
style=0xaaaaf52fa890) at gtkcssnode.c:425
#9 0x0000ffff6020eeb4 in gtk_css_node_ensure_style (cssnode=0xaaaaf4e22740,
current_time=current_time@entry=107356270) at gtkcssnode.c:1007
etc. etc. Is this still useless and indicative of memory corruption we're not
finding?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #13 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Mike FABIAN from comment #12)
> So I wonder what additional benefit ibus-bogo really offers. Should
> we bother fixing ibus-bogo at all?
I had a look at the ibus-bogo source code and I think I can fix it with some
effort...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #12 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Truong Anh Tuan from comment #9)
> > The Fedora test case for ibus-bogo, https://fedoraproject.org/wiki/QA:Bogo,
> > has:
> >
> > type "Khoong cos gif quis hown ddoocj laapj tuwj do".
> > ...
> > you will get: "Không có gì quí hơn độc lập tự do".
>
> This is the main/core function so this test is mandatory.
>
> > That looks like a transliteration which could be done easily with a m17n
> > input method as well.
And this test works already when using the vi-telex.mim input method
via ibus-typing-booster.
And it also works when using vi-telex.mim via ibus-m17n.
So I wonder what additional benefit ibus-bogo really offers. Should
we bother fixing ibus-bogo at all?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #11 from Truong Anh Tuan <tuanta(a)iwayvietnam.com> ---
(In reply to Mike FABIAN from comment #10)
> I am still confused, are you using ibus-bogo, or are you using vi-telex.mim
> through ibus-m17n or ibus-typing-booster?
I am currently using ibus-bogo and ibus-unikey, not ibus-m17n or
ibus-typing-booster.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #10 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Truong Anh Tuan from comment #9)
> (In reply to Mike FABIAN from comment #8)
> >
> > How are you using vi-telex? If I understand correctly, you are not using
> > /usr/share/m17n/vi-telex.mim
> > because you are using neither ibus-m17n nor ibus-typing-booster. So the
> > "vi-telex" you are using
> > must be some Vietnamese keyboard layout from xkb, I guess. But I can find
> > no “telex” in
> > /usr/share/X11/xkb/symbols/vn so I am wondering what exactly you are using.
>
> Sorry for getting you confused.
> I meant I use "Telex" method to type Vietnamese.
I am still confused, are you using ibus-bogo, or are you using vi-telex.mim
through
ibus-m17n or ibus-typing-booster?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #9 from Truong Anh Tuan <tuanta(a)iwayvietnam.com> ---
(In reply to Mike FABIAN from comment #8)
>
> How are you using vi-telex? If I understand correctly, you are not using
> /usr/share/m17n/vi-telex.mim
> because you are using neither ibus-m17n nor ibus-typing-booster. So the
> "vi-telex" you are using
> must be some Vietnamese keyboard layout from xkb, I guess. But I can find
> no “telex” in
> /usr/share/X11/xkb/symbols/vn so I am wondering what exactly you are using.
Sorry for getting you confused.
I meant I use "Telex" method to type Vietnamese.
> > ibus-bogo and ibus-unikey are a bit different as they are software for
> > Vietnamese language processing with additional features:
> > + Spelling checks.
> > + Text processing.
> > + Different Vietnamese charsets.
> > ...
>
> Is there a specification what exactly ibus-bogo and ibus-unikey are supposed
> to do?
>
> The Fedora test case for ibus-bogo, https://fedoraproject.org/wiki/QA:Bogo,
> has:
>
> type "Khoong cos gif quis hown ddoocj laapj tuwj do".
> ...
> you will get: "Không có gì quí hơn độc lập tự do".
This is the main/core function so this test is mandatory.
> That looks like a transliteration which could be done easily with a m17n
> input method as well.
> But for creating a m17n input method it would be nice to have some
> specification, that would be easier than just reverse engineering ibus-bogo.
Not sure. I will give a try.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1717958
Riccardo Schirone <rschiron(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rschiron(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=1717958
Riccardo Schirone <rschiron(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends On| |1751940
--- Comment #18 from Riccardo Schirone <rschiron(a)redhat.com> ---
Created ibus tracking bugs for this issue:
Affects: fedora-all [bug 1751940]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1751940
[Bug 1751940] CVE-2019-14822 ibus: missing authorization allows local attacker
to access the input bus of another user [fedora-all]
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1717958
Riccardo Schirone <rschiron(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|security, qe_staff |
CC| |eng-i18n-bugs(a)redhat.com,
| |i18n-bugs(a)lists.fedoraproje
| |ct.org,
| |shawn.p.huang(a)gmail.com
Summary|EMBARGOED CVE-2019-14822 |CVE-2019-14822 ibus:
|ibus: missing authorization |missing authorization
|allows local attacker to |allows local attacker to
|access the input bus of |access the input bus of
|another user |another user
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1707712
Bug ID: 1707712
Summary: liberation-fonts.noarch should not Provides or
Obsoletes liberation-narrow fonts
Product: Fedora
Version: 30
Status: NEW
Component: liberation-fonts
Assignee: petersen(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
This may be due to unclear wording in the Packaging Guidelines
but liberation-fonts should not Provides or Obsoletes liberation-narrow-fonts.
In fact is basically to install liberation-narrow-fonts in Fedora because of
this. ;-)
The Obsoletes made sense before liberation-narrow-fonts was reintroduced to
Fedora (except the upperbound is far to high).
How reproducible:
100%
Steps to Reproduce:
1. Try to install liberation-narrow-fonts
# dnf install liberation-narrow-fonts
Actual results:
liberation-fonts gets installed
Expected results:
liberation-narrow-fonts
Additional info:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repl…
"If a package supersedes/replaces an existing package without being a
sufficiently compatible replacement as defined above, use only the Obsoletes:
line from the above example."
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1195216
--- Comment #18 from Fedora Update System <updates(a)fedoraproject.org> ---
liberation-narrow-fonts-1.07.6-2.fc29 has been pushed to the Fedora 29 stable
repository. If problems still persist, please make note of it in this bug
report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #25 from Fedora Update System <updates(a)fedoraproject.org> ---
liberation-narrow-fonts-1.07.6-2.fc29 has been pushed to the Fedora 29 stable
repository. If problems still persist, please make note of it in this bug
report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #24 from Michal Jaegermann <michal.jnn(a)gmail.com> ---
(In reply to Albert Szostkiewicz from comment #23)
> Different version, same issue ?
>
> Dependencies resolved.
>
> Problem: cannot install both liberation-fonts-1:2.00.3-1.fc29.noarch and
> liberation-fonts-1:2.00.5-2.fc29.noarch
> - cannot install the best update candidate for package
> liberation-narrow-fonts-1.07.5-1.fc29.noarch
According to comment #20 from 2019-09-05 this trouble is resolved by version
1.07.6-2 while "regular" repositories for fc29 are still offering only
1.07.5-1. While 1.07.6-2 does fix this the update is apparently still stuck up
in "channels".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #8 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Truong Anh Tuan from comment #7)
> (In reply to Mike FABIAN from comment #4)
> > What is the difference between ibus-bogo, ibus-unikey, and the Vietnamese
> > input methods available in m17n-db (which are also available in
> > ibus-typing-booster)?
>
> Actually, I am not familiar with this. I am just a packager, not a software
> developer.
>
> > $ ls /usr/share/m17n/vi-*.mim
> > /usr/share/m17n/vi-base.mim /usr/share/m17n/vi-nom.mim
> > /usr/share/m17n/vi-viqr.mim
> > /usr/share/m17n/vi-han.mim /usr/share/m17n/vi-tcvn.mim
> > /usr/share/m17n/vi-vni.mim
> > /usr/share/m17n/vi-nom-vni.mim /usr/share/m17n/vi-telex.mim
>
> But I think these are Vietnamese keyboards, the way to type Vietnamese (I am
> using "vi-telex").
How are you using vi-telex? If I understand correctly, you are not using
/usr/share/m17n/vi-telex.mim
because you are using neither ibus-m17n nor ibus-typing-booster. So the
"vi-telex" you are using
must be some Vietnamese keyboard layout from xkb, I guess. But I can find no
“telex” in
/usr/share/X11/xkb/symbols/vn so I am wondering what exactly you are using.
> ibus-bogo and ibus-unikey are a bit different as they are software for
> Vietnamese language processing with additional features:
> + Spelling checks.
> + Text processing.
> + Different Vietnamese charsets.
> ...
Is there a specification what exactly ibus-bogo and ibus-unikey are supposed to
do?
The Fedora test case for ibus-bogo, https://fedoraproject.org/wiki/QA:Bogo,
has:
type "Khoong cos gif quis hown ddoocj laapj tuwj do".
...
you will get: "Không có gì quí hơn độc lập tự do".
That looks like a transliteration which could be done easily with a m17n input
method as well.
But for creating a m17n input method it would be nice to have some
specification, that would be easier than just reverse engineering ibus-bogo.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #23 from Albert Szostkiewicz <tmdag(a)tmdag.com> ---
Different version, same issue ?
Dependencies resolved.
Problem: cannot install both liberation-fonts-1:2.00.3-1.fc29.noarch and
liberation-fonts-1:2.00.5-2.fc29.noarch
- cannot install the best update candidate for package
liberation-narrow-fonts-1.07.5-1.fc29.noarch
- cannot install the best update candidate for package
liberation-fonts-1:2.00.5-2.fc29.noarch
=============================================================================================================================================================================================================================================
Package Architecture
Version
Repository Size
=============================================================================================================================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
liberation-fonts noarch
1:2.00.3-1.fc29
fedora 7.8 k
Transaction Summary
=============================================================================================================================================================================================================================================
Skip 1 Package
Nothing to do.
Complete!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #7 from Truong Anh Tuan <tuanta(a)iwayvietnam.com> ---
(In reply to Mike FABIAN from comment #4)
> What is the difference between ibus-bogo, ibus-unikey, and the Vietnamese
> input methods available in m17n-db (which are also available in
> ibus-typing-booster)?
Actually, I am not familiar with this. I am just a packager, not a software
developer.
> $ ls /usr/share/m17n/vi-*.mim
> /usr/share/m17n/vi-base.mim /usr/share/m17n/vi-nom.mim
> /usr/share/m17n/vi-viqr.mim
> /usr/share/m17n/vi-han.mim /usr/share/m17n/vi-tcvn.mim
> /usr/share/m17n/vi-vni.mim
> /usr/share/m17n/vi-nom-vni.mim /usr/share/m17n/vi-telex.mim
But I think these are Vietnamese keyboards, the way to type Vietnamese (I am
using "vi-telex").
ibus-bogo and ibus-unikey are a bit different as they are software for
Vietnamese language processing with additional features:
+ Spelling checks.
+ Text processing.
+ Different Vietnamese charsets.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #6 from Truong Anh Tuan <tuanta(a)iwayvietnam.com> ---
(In reply to Mike FABIAN from comment #5)
> (In reply to Truong Anh Tuan from comment #3)
> > I am still using both fine on my F30 Workstation.
> > Let me check this more details later.
>
> It works on Xorg, so maybe it works for you because you use Gnome on Xorg,
> not on Wayland.
I am currently using Wayland. Just checked:
[tuanta@tuanta ~]$ loginctl show-session 2 -p Type
Type=wayland
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #5 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Truong Anh Tuan from comment #3)
> I am still using both fine on my F30 Workstation.
> Let me check this more details later.
It works on Xorg, so maybe it works for you because you use Gnome on Xorg, not
on Wayland.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
Mike FABIAN <mfabian(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mfabian(a)redhat.com
--- Comment #4 from Mike FABIAN <mfabian(a)redhat.com> ---
What is the difference between ibus-bogo, ibus-unikey, and the Vietnamese input
methods available in m17n-db (which are also available in ibus-typing-booster)?
$ ls /usr/share/m17n/vi-*.mim
/usr/share/m17n/vi-base.mim /usr/share/m17n/vi-nom.mim
/usr/share/m17n/vi-viqr.mim
/usr/share/m17n/vi-han.mim /usr/share/m17n/vi-tcvn.mim
/usr/share/m17n/vi-vni.mim
/usr/share/m17n/vi-nom-vni.mim /usr/share/m17n/vi-telex.mim
If they are all different, then maybe it would be useful to add vi-bogo.mim and
vi-unikey.mim which
mimic the behaviour of ibus-bogo and ibus-unikey to be able to use these
Vietnamese input methods
with ibus-typing-booster (to get word completions).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1368757
--- Comment #10 from Peng Wu <pwu(a)redhat.com> ---
Hi Mike FABIAN,
I just tested with kwrite on Fedora 30 for this bug, it seems work.
Could we close this bug?
Thanks,
Peng
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1592335
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |ON_QA
--- Comment #5 from Fedora Update System <updates(a)fedoraproject.org> ---
Canna-3.7p3-56.fc29 has been pushed to the Fedora 29 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-2019-ea62c748f4
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #3 from Truong Anh Tuan <tuanta(a)iwayvietnam.com> ---
I am still using both fine on my F30 Workstation.
Let me check this more details later.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #2 from sandeep shedmake <sshedmak(a)redhat.com> ---
(In reply to fujiwara from comment #1)
> ibus-bogo has a problem in Wayland to send the wrong keycodes.
> I'd suggest to use preedit instead of forwarding key events or ibus-unikey
> instead.
Reported problem persists with f31 (ibus-bogo-0.4-20.fc31).
Yep, 'ibus-unikey' works as an alternative Vietnamese IME for ibus.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
--- Comment #8 from David Sommerseth <dazo(a)eurephia.org> ---
(In reply to Mike FABIAN from comment #6)
> /usr/share/X11/xkb/rules/base.xml contains for Norway:
>
>
> <layout>
> <configItem>
> <name>no</name>
>
> <shortDescription>no</shortDescription>
> <description>Norwegian</description>
> <languageList>
> <iso639Id>nor</iso639Id>
> <iso639Id>nob</iso639Id>
> <iso639Id>nno</iso639Id>
> </languageList>
> </configItem>
[...snip...]
> So it looks to me that "nno" is used to lookup that name in case
> of Norway and "dan" is used for Denmark. And the name is looked up
> in And /usr/share/xml/iso-codes/iso_639.xml.
You seem to be unto something here. As the Norwegian layout is defined with
both "Norwegian" (nor), "Norwegian, Bokmål" (nob) and "Norwegian, Nynorsk"
(nno) - where only the 'nno' is the one being picked up. Only the 'nor'
alternative should be used.
But Danish is "simpler", that it only has a single <iso639Id/> entry, while
Norwegian currently have 3 entries listed. Does all these three really need to
be listed here? As I said in comment #0, the Norwegian Bokmål and Norwegian
Nynorsk are 100% identical in regards to keyboard layout; the main difference
is how (quite) some words are spelled and/or pronounced - otherwise the rest of
the language characteristics are basically identical - and both are considered
a "Norwegian" language. Unless I've misunderstood something,
/usr/share/X11/xkb/rules/base.xml is used for keyboard configuration - so
removing the 'nob' and 'nno' entries shouldn't cause any harm.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1658169
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|unspecified |medium
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1658187
--- Comment #1 from Jens Petersen <petersen(a)redhat.com> ---
Better to move upstream perhaps?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1592335
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |MODIFIED
--- Comment #4 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2019-ea62c748f4 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea62c748f4
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1134299
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|29 |30
--- Comment #21 from Jens Petersen <petersen(a)redhat.com> ---
Still happening in F30+?
If someone could confirm for F31 even that would be good
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1569943
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FutureFeature
Link ID| |Mozilla Foundation 1580099
Version|29 |rawhide
--- Comment #7 from Jens Petersen <petersen(a)redhat.com> ---
I reported this upstream in
https://bugzilla.mozilla.org/show_bug.cgi?id=1580099
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1592335
Akira TAGOH <tagoh(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|extras-orphan@fedoraproject |tagoh(a)redhat.com
|.org |
Flags|needinfo?(tagoh(a)redhat.com) |
--- Comment #3 from Akira TAGOH <tagoh(a)redhat.com> ---
R: initscripts line was added according to the template of tmpfiles.d packaging
guidelines. and it isn't needed anymore. so dropping and built it in f29...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1449506
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FutureFeature
Priority|unspecified |medium
Version|29 |rawhide
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|29 |rawhide
--- Comment #7 from Jens Petersen <petersen(a)redhat.com> ---
Do the keyboard strings come from xkeyboard-config?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1446940
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |CURRENTRELEASE
Assignee|psatpute(a)redhat.com |pnemade(a)redhat.com
Last Closed| |2019-09-10 06:23:45
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1368757
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|than(a)redhat.com |pwu(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=1592335
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagoh(a)redhat.com
Flags| |needinfo?(tagoh(a)redhat.com)
--- Comment #2 from Jens Petersen <petersen(a)redhat.com> ---
Can we close this?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1603416
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2019-09-10 06:03:20
--- Comment #5 from Jens Petersen <petersen(a)redhat.com> ---
Fixed in F30+.
(Not sure what uses aspell-hi these days?)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1625596
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |FutureFeature
Version|29 |rawhide
Summary|emoji input does not work |emoji input does not work
|in f29 live |in Live
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1625596
--- Comment #4 from Jens Petersen <petersen(a)redhat.com> ---
Can you provide details of the memory usage? How heavy is it?
I feel consistency is also important.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744377
--- Comment #5 from Steven Usdansky <usdanskys(a)gmail.com> ---
New fontconfig fixes the problem for me
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #22 from Alexandre Ducastaing <alexducast(a)gmail.com> ---
It is fixed for me too. Thanks to Fedora Team!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ajax(a)redhat.com,
| |caillon+fedoraproject@gmail
| |.com,
| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |gnome-sig(a)lists.fedoraproje
| |ct.org,
| |john.j5live(a)gmail.com,
| |mclasen(a)redhat.com,
| |rhughes(a)redhat.com,
| |rstrode(a)redhat.com,
| |sandmann(a)redhat.com
Component|LiveCD - KDE |fontconfig
Assignee|fedora(a)deadbabylon.de |tagoh(a)redhat.com
QA Contact| |extras-qa(a)fedoraproject.org
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pnemade(a)redhat.com,
| |vvijayra(a)redhat.com
Flags| |needinfo?(aalam@fedoraproje
| |ct.org)
--- Comment #13 from Jens Petersen <petersen(a)redhat.com> ---
Is this a KDE Spin specific issue...?
Does the same issue exist on Fedora Workstation?
I would suggest moving to fontconfig say for lack of a better component.
I think it should either be solved in @fonts or fontconfig fedora .conf
priorities.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #21 from Donald O'Dona <thomas.paulsen(a)firemail.de> ---
it seems to be fixed so far. Thanks RH people!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
Kevin Fenzi <kevin(a)scrye.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|spin-kickstarts |LiveCD - KDE
Assignee|vpavlin(a)redhat.com |fedora(a)deadbabylon.de
QA Contact|extras-qa(a)fedoraproject.org |
--- Comment #12 from Kevin Fenzi <kevin(a)scrye.com> ---
Moving to livecd/kde
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Resolution|--- |ERRATA
Last Closed| |2019-09-05 11:48:17
--- Comment #19 from Fedora Update System <updates(a)fedoraproject.org> ---
liberation-narrow-fonts-1.07.6-2.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |ON_QA
--- Comment #18 from Fedora Update System <updates(a)fedoraproject.org> ---
liberation-narrow-fonts-1.07.6-2.fc31 has been pushed to the Fedora 31 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-2019-c3d484d6c4
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Gergely Gombos <gombosg(a)disroot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gombosg(a)disroot.org
--- Comment #17 from Gergely Gombos <gombosg(a)disroot.org> ---
Thanks for the fix, it's working! Let's test and give it some karma in Bodhi so
that it can quickly be pushed to stable.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |MODIFIED
--- Comment #15 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2019-2b29cee6f9 has been submitted as an update to Fedora 29.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-2b29cee6f9
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
love58900(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |love58900(a)gmail.com
--- Comment #14 from love58900(a)gmail.com ---
You can try:
rpm -e --nodeps liberation-narrow-fonts-1.07.6-1.fc30.noarch
It should remove the package and not the dependencies. The issue looks like
it's because the package names are different but the install location is the
same.
SOURCE: https://www.reddit.com/r/Fedora/comments/cxzcwy/cant_upgrade_a_package/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744970
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|MODIFIED |ON_QA
--- Comment #3 from Fedora Update System <updates(a)fedoraproject.org> ---
weston-6.0.0-3.fc31 has been pushed to the Fedora 31 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-2019-7a51c7bd9c
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loganjerry(a)gmail.com
--- Comment #13 from Parag Nemade <pnemade(a)redhat.com> ---
*** Bug 1747785 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747785
Bug ID: 1747785
Summary: Uninstallable liberation-fonts update
Product: Fedora
Version: 30
Hardware: All
OS: Linux
Status: NEW
Component: liberation-fonts
Severity: medium
Assignee: petersen(a)redhat.com
Reporter: loganjerry(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,
petersen(a)redhat.com, psatpute(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Trying to update my Fedora 30 machine this morning:
# dnf upgrade
Dependencies resolved.
Problem: cannot install both liberation-fonts-1:2.00.5-1.fc30.noarch and
liberation-fonts-1:2.00.5-3.fc30.noarch
- cannot install the best update candidate for package
liberation-narrow-fonts-1.07.6-1.fc30.noarch
- cannot install the best update candidate for package
liberation-fonts-1:2.00.5-3.fc30.noarch
================================================================================
Package Architecture Version Repository Size
================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
liberation-fonts noarch 1:2.00.5-1.fc30 fedora 8.0 k
Transaction Summary
================================================================================
Skip 1 Package
# dnf --best --allowerasing upgrade
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
(try to add '--skip-broken' to skip uninstallable packages)
Version-Release number of selected component (if applicable):
liberation-fonts-1:2.00.5-1.fc30
liberation-fonts-1:2.00.5-3.fc30
How reproducible:
N/A
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brian(a)interlinx.bc.ca
--- Comment #12 from Parag Nemade <pnemade(a)redhat.com> ---
*** Bug 1748302 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1748302
Bug ID: 1748302
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-fonts
Severity: high
Assignee: petersen(a)redhat.com
Reporter: brian(a)interlinx.bc.ca
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,
petersen(a)redhat.com, psatpute(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Error:
Problem: problem with installed package
liberation-fonts-1:2.00.5-3.fc30.noarch
- cannot install the best update candidate for package
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
- cannot install both liberation-fonts-1:2.00.5-1.fc30.noarch and
liberation-fonts-1:2.00.5-3.fc30.noarch
(try to add '--skip-broken' to skip uninstallable packages)
Version-Release number of selected component (if applicable):
liberation-fonts-2.00.5-3.fc30.noarch
liberation-narrow-fonts-1.07.6-1.fc30.noarch
How reproducible:
100%
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744970
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |MODIFIED
--- Comment #2 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2019-7a51c7bd9c has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2019-7a51c7bd9c
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Albert Szostkiewicz <tmdag(a)tmdag.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tmdag(a)tmdag.com
--- Comment #11 from Albert Szostkiewicz <tmdag(a)tmdag.com> ---
got same issue here
Problem: cannot install both liberation-fonts-1:2.00.5-1.fc30.noarch and
liberation-fonts-1:2.00.5-3.fc30.noarch
> env LANGUAGE=en dnf --version
4.2.7
Installed: dnf-0:4.2.7-2.fc30.noarch at Wed 04 Sep 2019 06:34:29 AM GMT
Built : Fedora Project at Tue 23 Jul 2019 07:10:30 AM GMT
Installed: rpm-0:4.14.2.1-5.fc30.x86_64 at Wed 04 Sep 2019 06:31:19 AM GMT
Built : Fedora Project at Thu 29 Aug 2019 10:46:16 AM GMT
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
Vendula Poncova <vponcova(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |admiller(a)redhat.com,
| |bruno(a)wolff.to,
| |dustymabe(a)redhat.com,
| |kevin(a)scrye.com,
| |vpavlin(a)redhat.com
Component|anaconda |spin-kickstarts
Assignee|tagoh(a)redhat.com |vpavlin(a)redhat.com
--- Comment #11 from Vendula Poncova <vponcova(a)redhat.com> ---
The fonts for Live ISO are defined by Fedora kickstart files. Reassigning to
spin-kickstarts.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #10 from Jens Petersen <petersen(a)redhat.com> ---
(In reply to Kalev Lember from comment #9)
> I think a simple solution to this would be to bump liberation-narrow-fonts
> epoch to 2, to make sure that the liberation-narrow-fonts EVR compares
> higher to 1:2.00.5-1.fc30 that's provided by liberation-fonts.
Yes +1
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1726215
Bug ID: 1726215
Summary: ibus does not work for applications run from Toolbox
container
Product: Fedora
Version: 30
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Current IMEs do not work for apps run from a Toolbox container.
How reproducible:
100%
Steps to Reproduce:
1.
$ sudo dnf install toolbox
$ toolbox create
$ toolbox enter
⬢$ sudo dnf install gedit
⬢$ gedit
2. try to use ibus in gedit running from container
Actual results:
IME can't be used (though Gnome Shell Input Source shows selected IME)
Expected results:
ibus should work
Additional info:
Maybe needs some dbus help.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Kalev Lember <klember(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |klember(a)redhat.com
--- Comment #9 from Kalev Lember <klember(a)redhat.com> ---
I think a simple solution to this would be to bump liberation-narrow-fonts
epoch to 2, to make sure that the liberation-narrow-fonts EVR compares higher
to 1:2.00.5-1.fc30 that's provided by liberation-fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|unspecified |high
Assignee|petersen(a)redhat.com |vvijayra(a)redhat.com
Severity|unspecified |high
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Michal Jaegermann <michal.jnn(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.jnn(a)gmail.com
--- Comment #8 from Michal Jaegermann <michal.jnn(a)gmail.com> ---
Not that surprisingly the same problem hits liberation-fonts-2.00.3-1.fc29 as
well. This cannot be installed even with '--allowerasing' present.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1744970
Kalev Lember <klember(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |klember(a)redhat.com
--- Comment #1 from Kalev Lember <klember(a)redhat.com> ---
Please do a PR and CC me there. Would be awesome if you could also help with
updating it to 7.0.0 that just got released.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #7 from Edouard Bourguignon <madko(a)linuxed.net> ---
same here if wine is installed can't upgrade without error:
LANG=C dnf --version
4.2.7
Installed: dnf-0:4.2.7-2.fc30.noarch at Sat Aug 24 12:35:09 2019
Built : Fedora Project at Tue Jul 23 07:10:30 2019
Installed: rpm-0:4.14.2.1-5.fc30.x86_64 at Sun Sep 1 09:32:22 2019
Built : Fedora Project at Thu Aug 29 10:46:16 2019
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1530086
A S Alam <aalam(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|30 |31
--- Comment #10 from A S Alam <aalam(a)fedoraproject.org> ---
Fedora 31 still have same issue
Tested with: Fedora-Workstation-Live-x86_64-31-20190902.n.0.iso
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #6 from Donald O'Dona <thomas.paulsen(a)firemail.de> ---
env LANGUAGE=en dnf --version
4.2.7
Installed: dnf-0:4.2.7-2.fc30.noarch at Tue 30 Jul 2019 10:59:54 AM GMT
Built : Fedora Project at Tue 23 Jul 2019 07:10:30 AM GMT
Installed: rpm-0:4.14.2.1-5.fc30.x86_64 at Mon 02 Sep 2019 05:26:38 AM GMT
Built : Fedora Project at Thu 29 Aug 2019 10:46:16 AM GMT
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #5 from Yaroslav Sidlovsky <zawertun(a)gmail.com> ---
$ env LANGUAGE=en dnf --version
0.3s (0) 11:19:58
4.2.7
Installed: dnf-0:4.2.7-2.fc30.noarch at Вт 30 июл 2019 09:40:08
Built : Fedora Project at Вт 23 июл 2019 07:10:30
Installed: rpm-0:4.14.2.1-5.fc30.x86_64 at Пн 02 сен 2019 05:58:34
Built : Fedora Project at Чт 29 авг 2019 10:46:16
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #4 from Marek Blaha <mblaha(a)redhat.com> ---
May I ask you what version of dnf are you using?
My first thought was, that the provide/obsolete are missing in newer version by
a mistake. But in liberation-fonts changelog I found:
* Mon Jun 24 2019 Vishal Vijayraghavan <vvijayra AT redhat DOT com> -
1:2.00.5-3
- Resolves: rhbz#1643920: Removed Obsoletes: %{fontname}-narrow-fonts and
Provides: %{fontname}-narrow-fonts macro
- Splitted the font family(mono, sans and serif) into diferrent root font
directories
Now the situation is confusing for the dependency solver:
- given the obsolete/provide in the version
liberation-fonts-1:2.00.5-1.fc30.noarch, this is the best version of
liberation-narrow-fonts package
- at the same time liberation-fonts-1:2.00.5-3.fc30.noarch is the best version
of liberation-fonts
this end in solution where two versions of liberation-fonts are about to be
installed, which is not viable.
I'm not sure how to solve this situation, but better workaround at the moment
is not to use versionlock (as I recommended in comment#1), but exclude
liberation-fonts-1:2.00.5-1.fc30.noarch package. E.g. adding
excludepkgs=liberation-fonts-1:2.00.5-1.fc30.noarch
line into [main] section of /etc/dnf/dnf.conf
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #3 from Donald O'Dona <thomas.paulsen(a)firemail.de> ---
# dnf update
skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
liberation-fonts noarch 1:2.00.5-1.fc30 fedora 8.0 k
# dnf update --best --allowerasing liberation-fonts
Last metadata expiration check: 0:59:12 ago on Mon 02 Sep 2019 08:01:11 AM
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
(try to add '--skip-broken' to skip uninstallable packages)
# dnf update --best --allowerasing liberation-fonts --skip-broken
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
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
--- Comment #2 from Yaroslav Sidlovsky <zawertun(a)gmail.com> ---
Same bug: #1747785.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1747737
Marek Blaha <mblaha(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caillon+fedoraproject@gmail
| |.com,
| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |gnome-sig(a)lists.fedoraproje
| |ct.org,
| |i18n-bugs(a)lists.fedoraproje
| |ct.org,
| |john.j5live(a)gmail.com,
| |mclasen(a)redhat.com,
| |petersen(a)redhat.com,
| |psatpute(a)redhat.com,
| |rhughes(a)redhat.com,
| |rstrode(a)redhat.com,
| |sandmann(a)redhat.com,
| |vishalvijayraghavan(a)gmail.c
| |om
Component|dnf |liberation-fonts
Assignee|rpm-software-management@lis |petersen(a)redhat.com
|ts.fedoraproject.org |
--- Comment #1 from Marek Blaha <mblaha(a)redhat.com> ---
It looks like liberation-fonts-1:2.00.5-1.fc30.noarch obsoletes and provides
liberation-narrow-fonts but the updated liberation-fonts-1:2.00.5-3.fc30.noarch
version does not:
$ dnf repoquery --obsoletes liberation-fonts-1:2.00.5-1.fc30.noarch
liberation-narrow-fonts < 1:2.0.0
$ dnf repoquery --provides liberation-fonts-1:2.00.5-1.fc30.noarch
liberation-fonts = 1:2.00.5-1.fc30
liberation-narrow-fonts = 1:2.00.5-1.fc30
$ dnf repoquery --obsoletes liberation-fonts-1:2.00.5-3.fc30.noarch
$ dnf repoquery --provides liberation-fonts-1:2.00.5-3.fc30.noarch
liberation-fonts = 1:2.00.5-3.fc30
Reassigning to liberation-fonts component to resolve the packaging problem.
You can workaround it by locking liberation-fonts package on older version: #
dnf versionlock liberation-fonts
--
You are receiving this mail because:
You are on the CC list for the bug.