[Bug 2178174] New: Status indicator doesn't show proper current
status on Flatpak app
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2178174
Bug ID: 2178174
Summary: Status indicator doesn't show proper current status on
Flatpak app
Product: Fedora
Version: 38
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 typing something through IBus on Flatpak on Silverblue and changing the
input mode by Zenkaku_Hankaku key, current input mode isn't reflected to the
status indicator at gnome-shell.
Version-Release number of selected component (if applicable):
Fedora-Silverblue-ostree-x86_64-38-20230314.n.0.iso
How reproducible:
always
Steps to Reproduce:
1.Install SB and setup as usual
2.Install LibreOffice from 'Fedora Linux' on gnome-software
3.Run LibreOffice and type something and Zenkaku_Hankaku key
Actual results:
The status indicator keeps 'あ' and no changes after pressing Zenkaku_Hankaku
key. also no ibus-related menu isn't available during flatpak app is active.
Expected results:
should works as usual
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=2178174
2 weeks, 6 days
[Bug 2093313] New: Too many ibus warnings, "no capability of
surrounding-text feature"
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2093313
Bug ID: 2093313
Summary: Too many ibus warnings, "no capability of
surrounding-text feature"
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:
I know this is an application bug, flooding same warnings looks not good to me.
this affects UX. applications and desktop is often freezing.
$ journalctl -S 2022-06-03 | grep IBUS-WARNING | wc -l
15974
That is quite bad.
Too many warnings should be omitted.
Version-Release number of selected component (if applicable):
ibus-1.5.26-4.fc36.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=2093313
3 weeks, 4 days
[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1790554
Bug ID: 1790554
Summary: Keyboard layout of Kana Kanji wont show up
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sumukher(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The keyboard layout for Kana Kanji Japanese doesnt show up
Version-Release number of selected component (if applicable):
Fedora-Rawhide-20200112.n.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install Fedora-Rawhide-20200112.n.0 WS from live boot
2. Open settings and navigate to Region and Language
3. Add Japanese Kana Kanji in the input source
4. Click the icon looking like an eye button which should open the keyboard
layout
Actual results:
Doesn't show up the keyboard layout
Expected results:
The keyboard layout should show up like it shows up for english
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 5 days
[Bug 2219580] New: [abrt] ibus-m17n: pop_im(): ibus-engine-m17n
killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2219580
Bug ID: 2219580
Summary: [abrt] ibus-m17n: pop_im(): ibus-engine-m17n killed by
SIGSEGV
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:2deacdc1a5691e3d276b97fbd7b38d765f2fe8e7;VAR
IANT_ID=workstation;
Component: ibus-m17n
Assignee: pnemade(a)redhat.com
Reporter: claudio(a)c3systems.com.br
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
pnemade(a)redhat.com, shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I can't tell......at one time i was able to accent letters and at others not
anymore.
Version-Release number of selected component:
ibus-m17n-1.4.19-1.fc38
Additional info:
reporter: libreport-2.17.11
kernel: 6.3.8-200.fc38.x86_64
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
reason: ibus-engine-m17n killed by SIGSEGV
journald_cursor:
s=6ffe44c376354fa4b647575156562e3e;i=2c8708;b=a03ce670cbc945ae972fcc641d6c89e7;m=b7c2c1ef16;t=5ff38eeefdc20;x=8f0e61a2f5a5c302
crash_function: pop_im
executable: /usr/libexec/ibus-engine-m17n
runlevel: N 5
uid: 1000
package: ibus-m17n-1.4.19-1.fc38
cmdline: /usr/libexec/ibus-engine-m17n --ibus
type: CCpp
comment: I can't tell......at one time i was able to accent letters and
at others not anymore.
Truncated backtrace:
Thread no. 1 (13 frames)
#0 pop_im at /usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:3778
#1 fini_ic_info at
/usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:3920
#2 destroy_ic at /usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:4073
#3 minput_destroy_ic at
/usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:4923
#4 fini_ic_info at
/usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:3930
#5 re_init_ic at /usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:4005
#6 minput_callback at
/usr/src/debug/m17n-lib-1.8.2-1.fc38.x86_64/src/input.c:6949
#8 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3851
#11 ibus_engine_service_method_call at
/usr/src/debug/ibus-1.5.28-6.fc38.x86_64/src/ibusengine.c:1345
#12 call_in_idle_cb at ../gio/gdbusconnection.c:5002
#16 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
#18 ibus_main at /usr/src/debug/ibus-1.5.28-6.fc38.x86_64/src/ibusshare.c:330
#19 start_component at
/usr/src/debug/ibus-m17n-1.4.19-1.fc38.x86_64/src/main.c:80
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219580
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 month, 2 weeks
[Bug 2248636] New: [abrt] ibus-libpinyin:
std::__glibcxx_assert_fail(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2248636
Bug ID: 2248636
Summary: [abrt] ibus-libpinyin: std::__glibcxx_assert_fail():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 39
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:90b337510822b74ec1264b8ed94bb02bf5d3006e;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: jacknlliu(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:
upgrade to fedora 39
Version-Release number of selected component:
ibus-libpinyin-1.15.4-1.fc39
Additional info:
reporter: libreport-2.17.11
journald_cursor:
s=efe1502c004e4d8fb9e372c089ce0297;i=3204d5;b=3f4d4311a5ea437cb5394fb51d9e764d;m=3258aaa;t=6099aa3bced6f;x=7855a2569304aad2
crash_function: std::__glibcxx_assert_fail
rootdir: /
reason: ibus-engine-libpinyin killed by SIGABRT
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
kernel: 6.5.9-300.fc39.x86_64
backtrace_rating: 4
runlevel: N 5
comment: upgrade to fedora 39
type: CCpp
cgroup: 0::/user.slice/user-42.slice/session-c1.scope
uid: 42
executable: /usr/libexec/ibus-engine-libpinyin
package: ibus-libpinyin-1.15.4-1.fc39
Truncated backtrace:
Thread no. 1 (27 frames)
#4 std::__glibcxx_assert_fail at
../../../../../libstdc++-v3/src/c++11/debug.cc:61
#5 std::unique_ptr<PY::LibPinyinBackEnd,
std::default_delete<PY::LibPinyinBackEnd> >::operator* at
/usr/include/c++/13/bits/unique_ptr.h:451
#7 PY::LibPinyinBackEnd::instance at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYLibPinyin.h:61
#8 PY::SuggestionEditor::~SuggestionEditor at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYPSuggestionEditor.cc:48
#10 std::_Sp_counted_ptr<PY::SuggestionEditor*,
(__gnu_cxx::_Lock_policy)2>::_M_dispose at
/usr/include/c++/13/bits/shared_ptr_base.h:428
#11 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release at
/usr/include/c++/13/bits/shared_ptr_base.h:346
#13 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count at
/usr/include/c++/13/bits/shared_ptr_base.h:1071
#14 std::__shared_ptr<PY::Editor, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr
at /usr/include/c++/13/bits/shared_ptr_base.h:1524
#15 std::shared_ptr<PY::Editor>::~shared_ptr at
/usr/include/c++/13/bits/shared_ptr.h:175
#16 PY::PinyinEngine::~PinyinEngine at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYPPinyinEngine.cc:123
#18 PY::ibus_pinyin_engine_destroy at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYEngine.cc:185
#20 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:4020
#21 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#24 ibus_object_dispose at /usr/src/debug/ibus-1.5.29
#27 g_list_foreach at ../glib/glist.c:1092
#28 g_list_free_full at ../glib/glist.c:246
#29 ibus_factory_destroy at /usr/src/debug/ibus-1.5.29
#31 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:4020
#32 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#35 ibus_object_dispose at /usr/src/debug/ibus-1.5.29
#39 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3980
#40 signal_emit_valist_unlocked at ../gobject/gsignal.c:3612
#43 emit_closed_in_idle at ../gio/gdbusconnection.c:1375
#46 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
#47 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
#49 ibus_main at /usr/src/debug/ibus-1.5.29
#50 start_component at
/usr/src/debug/ibus-libpinyin-1.15.4-1.fc39.x86_64/src/PYMain.cc:155
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2248636
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
2 months, 1 week
[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 2246246] New: [abrt] ibus-typing-booster: getFilesToDelete():
__init__.py:1081:handleError:RuntimeError: reentrant call inside
<_io.BufferedWriter name='<stderr>'>
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2246246
Bug ID: 2246246
Summary: [abrt] ibus-typing-booster: getFilesToDelete():
__init__.py:1081:handleError:RuntimeError: reentrant
call inside <_io.BufferedWriter name='<stderr>'>
Product: Fedora
Version: 39
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:6d2411693b6ba4097e2cc69aa959625eef780015;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: buhrt(a)aftinc.net
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Restart Fedora 39
Version-Release number of selected component:
ibus-typing-booster-2.24.2-1.fc39
Additional info:
reporter: libreport-2.17.11
kernel: 6.5.7-300.fc39.x86_64
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
uid: 1000
reason: __init__.py:1081:handleError:RuntimeError: reentrant call
inside <_io.BufferedWriter name='<stderr>'>
executable: /usr/share/ibus-typing-booster/engine/main.py
type: Python3
package: ibus-typing-booster-2.24.2-1.fc39
runlevel: N 5
exception_type: PermissionError
crash_function: getFilesToDelete
interpreter: python3-3.12.0-1.fc39.x86_64
comment: Restart Fedora 39
Truncated backtrace:
#1 [/usr/lib64/python3.12/logging/handlers.py:370] getFilesToDelete
#2 [/usr/lib64/python3.12/logging/handlers.py:437] doRollover
#3 [/usr/lib64/python3.12/logging/handlers.py:74] emit
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2246246
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
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