https://bugzilla.redhat.com/show_bug.cgi?id=2113538
Bug ID: 2113538
Summary: nafees-tehreer-naskh-fonts: FTBFS in Fedora
rawhide/f37
Product: Fedora
Version: rawhide
Status: NEW
Component: nafees-tehreer-naskh-fonts
Assignee: psatpute(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
nafees-tehreer-naskh-fonts failed to build from source in Fedora rawhide/f37
https://koji.fedoraproject.org/koji/taskinfo?taskID=89834809
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
Please fix nafees-tehreer-naskh-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,
nafees-tehreer-naskh-fonts will be orphaned. Before branching of Fedora 38,
nafees-tehreer-naskh-fonts will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2045102
[Bug 2045102] Fedora 37 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=2113538
https://bugzilla.redhat.com/show_bug.cgi?id=2113534
Bug ID: 2113534
Summary: nafees-nastaleeq-fonts: FTBFS in Fedora rawhide/f37
Product: Fedora
Version: rawhide
Status: NEW
Component: nafees-nastaleeq-fonts
Assignee: psatpute(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com
Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
nafees-nastaleeq-fonts failed to build from source in Fedora rawhide/f37
https://koji.fedoraproject.org/koji/taskinfo?taskID=89834788
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
Please fix nafees-nastaleeq-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,
nafees-nastaleeq-fonts will be orphaned. Before branching of Fedora 38,
nafees-nastaleeq-fonts will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2045102
[Bug 2045102] Fedora 37 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=2113534
https://bugzilla.redhat.com/show_bug.cgi?id=2061664
Bug ID: 2061664
Summary: IBus candidate panel show up at wrong positions for QT
apps
Product: Fedora
Version: 36
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: vtq-gnome(a)outlook.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: ---
Link ID: Red Hat Bugzilla 2060988
Classification: Fedora
Description of problem:
When I trying to input chinese text with ibus-libpinyin in QT apps (tested
texworks, okular, kwrite, konsole, fedora mediawriter, seemingly all QT apps),
the candidate character panel shows up not below the cursor but at a wrong
position, sometimes outside the window. This happens in both Wayland and Xorg
sessions, although the position is different for the two environments.
Version-Release number of selected component (if applicable):
Fedora-Workstation-Live-x86_64-36-20220307.n.0.iso image running on bare metal.
ibus-1.5.25-13.fc36
ibus-libpinyin-1.12.1-2.fc36
qt5-qtbase-5.15.2-33.fc36
How reproducible:
Always
Steps to Reproduce:
1. Boot from the live image
2. Add Intelligent Pinyin IME from Settings-Keyboard-Input Sources
3. Install some QT apps (e.g. kwrite)
4. Open kwrite, click the text field, use Super-Space to switch to Pinyin
input, and try to input some text
Actual results:
The candidate character panel shows up at a wrong position, sometimes outside
the window.
Expected results:
The candidate character panel should show up just below the text cursor.
Additional info:
Bug 2060988 for Wayland seems to be related. But this is happening in Xorg
session too.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2061664
https://bugzilla.redhat.com/show_bug.cgi?id=2123720
Bug ID: 2123720
Summary: Noto Sans Thai to default for Thai
Product: Fedora
Version: rawhide
Status: NEW
Component: google-noto-fonts
Keywords: FutureFeature
Assignee: tagoh(a)redhat.com
Reporter: tagoh(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,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
As we have changed most languages default to Noto, it may be good to consider
updating Thai to Noto as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2123720
https://bugzilla.redhat.com/show_bug.cgi?id=2123722
Bug ID: 2123722
Summary: Noto Khmer to default for Khmer
Product: Fedora
Version: rawhide
Status: NEW
Component: google-noto-fonts
Keywords: FutureFeature
Assignee: tagoh(a)redhat.com
Reporter: tagoh(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,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
As we have changed most languages default to Noto, it may be good to consider
updating Khmer to Noto as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2123722
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
Bug ID: 2013323
Summary: Cursor position and conversion regioni of ibus-anthy
are invisible in Google Documents (both in firefox and
google-chrome)
Product: Fedora
Version: 34
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
Created attachment 1832255
--> https://bugzilla.redhat.com/attachment.cgi?id=1832255&action=edit
Video showing the wrongly displayed cursor position using ibus-anthy in Google
Documents
I did choose component ibus, although this is likely not an ibus bug but a
problem in google docs, but I wanted to report it somehow, maybe something can
be done to improve this:
Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with
all current updates.
firefox-93.0-2.fc35.x86_64
google-chrome-unstable-96.0.4662.6-1.x86_64
ibus-1.5.25-4.fc35.x86_64
ibus-anthy-1.5.13-1.fc35.x86_64
See the attached video.
In the video I type わたしのなまえはやまだです first in gedit to show how it should work.
After typing that hiragana, I type space to start conversion. The current
conversion region is indicated by the cursor position and a purple background
color. When the conversion to kanji is startet, at first the cursor position is
at the left of the preedit and the conversion region is わたしの. I can then move
the conversion region right with arrow-right and see that it moves because the
blue background and the cursor position moves.
Then I do the same in Google Documents (both in firefox and google-chrome, that
makes no difference):
- The cursor position is *always* shown at the right end of the preedit
- The purple background color of the conversion region is not there
One can move the conversion region around using the arrow keys, one just cannot
see where the conversion region currently is the purple background is missing
*and* the cursor position is *always* at the right end of the preedit.
The same problem happens when trying to use ibus-typing-booster with the
"inline completion" option in Google Documents. The color of the inline
completion is missing *and* the cursor position is always at the end of the
preedit, so one cannot see where the inline completion is and whether it has
been accepted or not.
In gedit in wayland, the colors don't work either, but at least the cursor
position is shown correctly. When only the cursor position is shown but no
color, it is not great at least somewhat usable. By carefully watching the
cursor one can still see what is going on. But when the cursor positon is
always at the right of preedit *and* there is no colour, this is completely
unusable.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013323