[Bug 2123722] New: Noto Khmer to default for Khmer
by bugzilla@redhat.com
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
4 months, 4 weeks
[Bug 2093859] New: [abrt] ibus-anthy-python: _Py_INCREF():
python3.10 killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2093859
Bug ID: 2093859
Summary: [abrt] ibus-anthy-python: _Py_INCREF(): python3.10
killed by SIGSEGV
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:cf7f44bcb9c2c2815bdb65cb37a42f3598ad0a67;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
Description of problem:
Version-Release number of selected component:
ibus-anthy-python-1.5.14-4.fc36
Additional info:
reporter: libreport-2.17.1
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: python3 /usr/share/ibus-anthy/engine/main.py --ibus
crash_function: _Py_INCREF
executable: /usr/bin/python3.10
journald_cursor:
s=0325f794070a4f0cbc4530c1f3e0ce87;i=251fb;b=a1249be8f9ec419eb97f1227a35e5fc0;m=87fad6a;t=5e062559eddf7;x=20a00219da6db34b
kernel: 5.17.11-300.fc36.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 _Py_INCREF at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Include/object.h:472
#1 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Python/ceval.c:2806
#2 _PyEval_EvalFrame at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Include/internal/pycore_ceval.h:46
#3 _PyEval_Vector at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Python/ceval.c:5065
#4 _PyObject_VectorcallTstate at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Include/cpython/abstract.h:114
#5 PyObject_Vectorcall at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Include/cpython/abstract.h:123
#6 call_function at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Python/ceval.c:5867
#7 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Python/ceval.c:4213
#8 _PyEval_EvalFrame at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Include/internal/pycore_ceval.h:46
#9 _PyEval_Vector at
/usr/src/debug/python3.10-3.10.4-1.fc36.x86_64/Python/ceval.c:5065
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2093859
5 months
[Bug 2074360] New: Xorg gtk4: candidate windows are placed
off-screen
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2074360
Bug ID: 2074360
Summary: Xorg gtk4: candidate windows are placed off-screen
Product: Fedora
Version: 36
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:
With Gnome on Xorg using gtk4 apps, the candidate is often placed
partially or completely off-screen, which is not useful of course.
Version-Release number of selected component (if applicable):
ibus-1.5.26-3.fc36.x86_64
gtk4-4.6.2-2.fc36.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start GNOME on Xorg
2. Open gnome-text-editor or gtk4-demo-application
3. Try to input Japanese or Chinese
Actual results:
Candidate window is place off-window or off-screen
Expected results:
Candidate window to be visible like with gtk3 apps
Additional info:
Is there some way to enforce that candidate windows should always appear
on-screen?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2074360
5 months
[Bug 2013323] New: Cursor position and conversion regioni of
ibus-anthy are invisible in Google Documents (both in firefox and
google-chrome)
by bugzilla@redhat.com
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
5 months
[Fedora-i18n-bugs] [Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
Bug ID: 1779123
Summary: Pango no longer supports type1 fonts
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: mjg(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In pango 1.44, pango dropped support for type1 fonts. Therefore, no application
which uses pango for font loading can use type1 fonts any more.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64 (and later)
How reproducible:
always
Steps to Reproduce:
1. Upgrade F31 or rawhide
2. Open any pango-using application
3. Try to use type1 font
Actual results:
No type1 font is usable
Expected results:
Type1 font is usable
Additional info:
bug 1753295 is the same bug for dropped bitmap font support. Over there,
workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are
discussed. An attempt to discuss type1 there failed.
This bug here is specifically about type1 fonts to discuss ways (or their
absence) to deal with pangos dropped type 1 support.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 months
[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.
5 months
[Bug 1993618] New: [abrt] ibus-libpinyin:
PY::PunctEditor::moveCursorToBegin(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1993618
Bug ID: 1993618
Summary: [abrt] ibus-libpinyin:
PY::PunctEditor::moveCursorToBegin():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:e41f218ee5601bc1377bb63d92ea7cfafa49f6df;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: tcfxfzoi(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-libpinyin-1.12.0-3.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
crash_function: PY::PunctEditor::moveCursorToBegin
executable: /usr/libexec/ibus-engine-libpinyin
journald_cursor:
s=b843de467070413eac4da2bc5d966ff5;i=701f;b=c1ce31806f0448d2826bedd20c47fa6b;m=99564a78;t=5c986a4580fd5;x=bf2d4d76d0a056b9
kernel: 5.13.9-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (9 frames)
#4 PY::PunctEditor::moveCursorToBegin at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:317
#5 PY::PunctEditor::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:190
#6 PY::BopomofoEngine::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPBopomofoEngine.cc:198
#8 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at
/usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusmarshalers.c:280
#13 ibus_engine_service_method_call at
/usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusengine.c:1107
#14 call_in_idle_cb at ../gio/gdbusconnection.c:4913
#18 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131
#20 ibus_main at /usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusshare.c:322
#21 start_component at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYMain.cc:141
--
You are receiving this mail because:
You are on the CC list for the bug.
5 months
[Fedora-i18n-bugs] [Bug 1897782] New: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1897782
Bug ID: 1897782
Summary: ibus pinyin input with special characters like '/'
will repeat itself non-stop and cause strange
behaviours with background applications
Product: Fedora
Version: 33
Status: NEW
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: yemoran-2020(a)outlook.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In Fedora 33 Workstation, with a Chinese system language, when I try to input
with the ibus input (intelligent pinyin), and I pressed the slash key'/', then
the slash character '/' will automatically keep repeating itself, even if I
only pressed the slash key '/' once.
Not only this caused unwanted '/' to spam, but:
1. Also prevents me from pressing alphabetical characters to use pinyin input
normally, unless I delete all my remaining characters to exit pinyin prompt and
start over;
2. Can possibly delete my already-saved text, in combination with
<Ctrl-Backspace>.
It seems that I have completely lost control within the pinyin prompt. I have
met with other surprising conditions, though cannot be immediately reproduced
now, but I believe more combinations of inputs triggering different bugs will
be confirmed later.
Version-Release number of selected component (if applicable):
Any kind of version. I also tested with Fedora 32 Workstation, still have this
bug.
How reproducible:
Always
Steps to Reproduce:
1. Fetch any Fedora Workstation version, be it 32 or 33 or any updates applied.
2. Add Chinese input method 'Intelligent Pinyin' and switch to it
3. In GNOME(Wayland), open any GTK-based application, be it Firefox, GNOME
Terminal, gedit, Libreoffice, ... (take gedit as an example)
4. Input 你好,今天天气 (keypress: nihao<1>,jintian<1>) as a start up example, confirm
input use number key '1'. or keys like <Enter> or <Space>.
5. Input 怎么样/ (keypress: zenmy/). Do not confirm immediately after 'zenmy', but
press '/' exactly once.
6. The '/' character is repeating itself within several hundred milliseconds.
7. Press <Ctrl-Backspace>. gedit will highlight "你好,今天天气" (with a lot of
trailing '/').
8. Press <Backspace> to delete these Chinese characters.
Actual results:
Not only '/' is repeating itself, but also I lost control to gedit and gedit
thinks you want to press '/' forever or even wants to delete my
already-confirmed characters before this input.
Expected results:
1. '/' Should not trigger anything, unless I have pressed this key and did not
release this key press (but I always release keys)
2. '/' Should not make me lost control over pinyin prompt to gedit
3. <Backspace> Should only delete pinyin alphabets in pinyin prompt panel, and
should not do anything to the background gedit texts, unless I have exited the
pinyin prompt panel (because I confirmed my input or have deleted every pinyin
alphabet in it)
Additional info:
1. I did not found this bug on Debian buster or Arch with latest updates.
Additionally, '/' did not even input a single character '/' in these
distributions, but I cannot confirm if this is the expected behaviour. In
Fedora 33 KDE, '/' did input a single character '/', but immediately stopped.
2. I didn't find this behaviour in qt-based applications (like Fedora Image
Writer or Octave) in GNOME, or any application in other desktop environments
(including KDE, or even GTK-based Cinnamon Desktop). This bug seems to only
occur on GTK-based applications on GNOME.
3. I can be very sure that this is not caused by something wrong with my
specific keyboard, because (a) Other distributions worked very well (b) Other
Fedora spins worked very well (c) Qt-based applications in GNOME worked very
well (d) GNOME X11 session worked very well (e) I replicated this bug on a
fresh install of Fedora 32 Workstation in another laptop of mine.
4. I guess other special characters (or keys) like '[', ']', '\', '<Esc>',
'<Backspace>', etc. may trigger similar bugs, but I cannot confirm. '/' will
surely trigger this. ',' and '.' are used in pinyin input method to flip
candidate characters pages, so they doesn't trigger this bug. ' does not
trigger this bug (used in xi'an for 西安)
--
You are receiving this mail because:
You are on the CC list for the bug.
5 months
[Bug 2164233] New: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
Bug ID: 2164233
Summary: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
Product: Fedora
Version: 37
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: byoungchan.lee(a)gmx.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.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, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I try to run openttd, fontconfig crashes due to an assertion.
https://github.com/freedesktop/fontconfig/blob/2.14.1/src/fccache.c#L808
Version-Release number of selected component (if applicable):
$ rpm -qa | grep fontconfig
fontconfig-2.14.1-2.fc37.x86_64
fontconfig-2.14.1-2.fc37.i686
fontconfig-devel-2.14.1-2.fc37.x86_64
fontconfig-debugsource-2.14.1-2.fc37.x86_64
$ rpm -qa | grep openttd
openttd-opengfx-7.1-3.fc37.noarch
openttd-12.2-4.fc37.x86_64
How reproducible:
Run openttd
Steps to Reproduce:
1.
2.
3.
Actual results:
Crash
Expected results:
Game runs.
Additional info:
I'm not sure why assertions are enabled in fontconfig.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
5 months, 1 week
[Bug 2062619] New: IBus stop working after locking screen
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2062619
Bug ID: 2062619
Summary: IBus stop working after locking screen
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: tagoh(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:
When I keep preediting on apps and the screen is locked by idle, IBus stop
working after unlocking.
Version-Release number of selected component (if applicable):
ibus-1.5.25-13.fc36.x86_64
How reproducible:
always
Steps to Reproduce:
1.Install Workstation from Live
2.Setup with ja
3.Open LibreOffice Writer
4.Type something on preedit and wait for locking the screen
5.Unlock the screen
Actual results:
Unable to input through IBus on apps
Expected results:
Able to input through IBus
Additional info:
IBus get back after changing the focus for example.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2062619
5 months, 2 weeks