[Bug 2183905] New: replace gettext hostname helper with
/usr/bin/hostname
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2183905
Bug ID: 2183905
Summary: replace gettext hostname helper with /usr/bin/hostname
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Assignee: suanand(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
nphilipp(a)redhat.com, petersen(a)redhat.com,
praiskup(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
gettext includes its own hostname helper program
(presumably for systems that do not provide the hostname tool)
which uses deprecated gethostbyname() function...
If /usr/bin/hostname is a drop in replacement then it seems
better just to use that in place of it - this would avoid
the rpminspect warnings/errors about gethostbyname() usage.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2183905
2 months, 1 week
[Bug 1974983] New: After upgrade xkeyboard-config to version
2.33-1.fc35 layout indicator stop react to layout switch by Ctrl-Shift key
combination.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1974983
Bug ID: 1974983
Summary: After upgrade xkeyboard-config to version 2.33-1.fc35
layout indicator stop react to layout switch by
Ctrl-Shift key combination.
Product: Fedora
Version: rawhide
Status: NEW
Component: xkeyboard-config
Assignee: peter.hutterer(a)redhat.com
Reporter: mikhail.v.gavrilov(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
After upgrade xkeyboard-config to version 2.33-1.fc35 layout indicator stop
react to layout switch by Ctrl-Shift key combination.
The bug is affected only Wayland session and only non standard layout switch
key combination.
Last good version is 2.32-3.fc35
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 2 weeks
[Bug 2088665] New: Noto Sans is chosen to display symbol characters
it doesn't contain
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
Bug ID: 2088665
Summary: Noto Sans is chosen to display symbol characters it
doesn't contain
Product: Fedora
Version: 36
Status: NEW
Component: google-noto-fonts
Assignee: tagoh(a)redhat.com
Reporter: talk(a)danielflaum.net
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1881507
--> https://bugzilla.redhat.com/attachment.cgi?id=1881507&action=edit
A zipped sample PDF and image of relevant portion of PDF when affected by the
issue
Description of problem:
Given a PDF lacking embedded fonts which use certain characters (including →
and ≥), GNOME's Evince on Fedora 36 chooses to substitute the Noto Sans font,
which does not include these characters.
Version-Release number of selected component (if applicable):
How reproducible:
Successfully reproduced by two people independently.
Steps to Reproduce:
1. Boot a fresh copy of Fedora 36 (the Live version in a VM will do).
2. Open the attached sample PDF in GNOME Evince (aka Document Viewer).
3. Observe the missing characters in the second paragraph from the top of the
page.
Actual results:
See attached image.
Expected results:
The missing characters should be displayed properly as → (that is,
https://unicode-table.com/en/2192/).
Additional info:
The filer initially sought help at
https://ask.fedoraproject.org/t/missing-characters-in-pdfs-since-upgrade-...,
which may be informative in reproducing the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2088665
2 months, 2 weeks
[Bug 2093080] New: Default fonts for Arabic do not match the font
packages list
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2093080
Bug ID: 2093080
Summary: Default fonts for Arabic do not match the font
packages list
Product: Fedora
Version: 36
Hardware: All
OS: Linux
Status: NEW
Component: fontconfig
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: awilliam(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, 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
There's a test case:
https://fedoraproject.org/wiki/QA:Testcase_i18n_default_fonts
which requires checking the default fonts for various languages against a list,
http://tagoh.fedorapeople.org/fonts/fc-test.sh .
The current default fonts for Arabic installs do not match the list. The list
states sans should be DejaVu Sans, serif should be FreeSerif or MPH 2B Damase,
and mono should be DejaVu Sans Mono. These may have been changed recently, as
our openQA reference text file expects them to be Noto Naskh Arabic (for both
sans and serif?) and PakType Naskh Basic for mono.
In any case, what we actually see doesn't match either the list or the openQA
reference file. We see "Noto Sans Arabic" and "PakType Naqsh" in the output
from the test, I think for serif (yes really) and monospace respectively.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093080
2 months, 2 weeks
[Bug 1974076] New: Chinese input methods use previously enabled
layout
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1974076
Bug ID: 1974076
Summary: Chinese input methods use previously enabled layout
Product: Fedora
Version: 34
Hardware: All
OS: Linux
Status: NEW
Component: ibus-libpinyin
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: nickolay.ilyushin(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
ibus-libpinyin (and most probably several other input methods) uses `default`
keyboard layout instead of `us` or whatever fits best. This effectively means
that the last keyboard layout (non-IME) will be used for the pinyin input. For
users which use non-Latin keyboard layouts, such as Russian or Ukrainian, this
makes pinyin input unusable.
Version-Release number of selected component (if applicable): 1.12.0
How reproducible: easily.
Steps to Reproduce:
1. Enable pinyin input method in your settings.
2. Switch to e.g. Russian layout.
3. Switch to pinyin IME.
4. You will type Russian letters and pinyin IME will not trigger.
Actual results:
`4. You will type Russian letters and pinyin IME will not trigger.`
Expected results:
`4. You will type *Latin* letters and pinyin IME *will* trigger.`
Additional info:
There are two workarounds:
1. Manually patch `/usr/share/ibus/component/libpinyin.xml` and change `layout`
to `us` from `default`. I don't know how this will work with non-QWERTY
keyboards though.
2. Switch to a Latin layout before switching to pinyin.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 months, 2 weeks