[Bug 2070187] New: please branch ibus-kkc for epel9
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2070187
Bug ID: 2070187
Summary: please branch ibus-kkc for epel9
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-kkc
Assignee: dueno(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
Target Milestone: ---
Classification: Fedora
Description of problem:
I would like to have ibus-kkc with libkkc in epel9
and would be happy to help build it if you like.
Could you please request an epel9 branch?
If you don't mind to make me comaintainer that would be fine too.
(libkkc got orphaned during the F35 cycle, I think
so I was able to branch that already.)
Thanks
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2070187
2 hours, 6 minutes
[Bug 2192853] New: [abrt] ibus: g_menu_model_get_n_items():
ibus-extension-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2192853
Bug ID: 2192853
Summary: [abrt] ibus: g_menu_model_get_n_items():
ibus-extension-gtk3 killed by SIGSEGV
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:49fccb793796915e78c43a088bda22e4cff833f8;VAR
IANT_ID=kde;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: oper.kh(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
Version-Release number of selected component:
ibus-1.5.28-4.fc38
Additional info:
reporter: libreport-2.17.9
type: CCpp
reason: ibus-extension-gtk3 killed by SIGSEGV
journald_cursor:
s=a32adcab7d4146c890beacb253c58fb2;i=315adc;b=21dc8809e9a74379baf3ef9921e32de4;m=1e69768ff;t=5fac79969bccc;x=53b07cc084ee6f8d
executable: /usr/libexec/ibus-extension-gtk3
cmdline: /usr/libexec/ibus-extension-gtk3
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-com.redhat.imsettings@0.service
rootdir: /
uid: 1000
kernel: 6.2.14-300.fc38.x86_64
package: ibus-1.5.28-4.fc38
runlevel: N 5
backtrace_rating: 4
crash_function: g_menu_model_get_n_items
Truncated backtrace:
Thread no. 1 (19 frames)
#0 g_menu_model_get_n_items at ../gio/gmenumodel.c:500
#1 gtk_application_window_update_shell_shows_app_menu at
../gtk/gtkapplicationwindow.c:322
#2 gtk_application_window_real_realize at ../gtk/gtkapplicationwindow.c:683
#3 _g_closure_invoke_va at ../gobject/gclosure.c:895
#6 gtk_widget_realize at ../gtk/gtkwidget.c:5523
#7 gtk_window_show at ../gtk/gtkwindow.c:6206
#9 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3742
#12 gtk_widget_show at ../gtk/gtkwidget.c:4852
#13 ibus_emojier_real_show_all
#14 panel_binding_real_panel_extension_received
#16 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3851
#19 ibus_panel_service_service_method_call
#20 call_in_idle_cb at ../gio/gdbusconnection.c:5000
#24 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
#26 gtk_main at ../gtk/gtkmain.c:1329
#27 _g_closure_invoke_va at ../gobject/gclosure.c:895
#30 g_application_activate at ../gio/gapplication.c:2312
#31 g_application_real_local_command_line at ../gio/gapplication.c:1148
#32 g_application_run at ../gio/gapplication.c:2542
Potential duplicate: bug 1451647
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2192853
2 hours, 10 minutes
[Bug 2185830] New: [abrt] ibus-typing-booster: Py_Exit(): python3.11
killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2185830
Bug ID: 2185830
Summary: [abrt] ibus-typing-booster: Py_Exit(): python3.11
killed by SIGABRT
Product: Fedora
Version: 38
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:1016fbf3f898a8e267bb35897e7a7417c6d30f73;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: vladislav.inu(a)gmail.com
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
Version-Release number of selected component:
ibus-typing-booster-2.22.2-1.fc38
Additional info:
reporter: libreport-2.17.9
type: CCpp
reason: python3.11 killed by SIGABRT
journald_cursor:
s=ea8f1ea7412e46b6a5353afa22fa7be4;i=e85a;b=d3999bf12e7d45efa833e6ddcd5e4ab9;m=1669657280;t=5f8fe63f93bb0;x=8989452a1e24b345
executable: /usr/bin/python3.11
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
rootdir: /
uid: 1000
kernel: 6.2.9-300.fc38.x86_64
package: ibus-typing-booster-2.22.2-1.fc38
runlevel: N 5
dso_list: /usr/bin/python3.11 python3-3.11.3-1.fc38.x86_64 (Fedora
Project) 1680959302
backtrace_rating: 4
crash_function: Py_Exit
Truncated backtrace:
Thread no. 1 (34 frames)
#5 Py_Exit at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pylifecycle.c:2944
#6 handle_system_exit at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:771
#7 _PyErr_PrintEx at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:781
#8 PyErr_PrintEx at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:876
#9 pygi_signal_closure_marshal at ../gi/pygi-signal-closure.c:202
#11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802
#18 emit_closed_in_idle at ../gio/gdbusconnection.c:1375
#22 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
#24 ffi_call_unix64 at ../src/x86/unix64.S:104
#25 ffi_call_int at ../src/x86/ffi64.c:673
#26 ffi_call at ../src/x86/ffi64.c:710
#27 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684
#28 pygi_function_cache_invoke at ../gi/pygi-cache.c:862
#29 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727
#30 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764
#31 _callable_info_call at ../gi/pygi-info.c:548
#32 _PyObject_MakeTpCall at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Objects/call.c:214
#33 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:4773
#34 _PyEval_EvalFrame at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Include/internal/pycore_ceval.h:73
#35 _PyEval_Vector at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:6438
#36 PyEval_EvalCode at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:1154
#37 run_eval_code_obj at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1714
#38 run_mod at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1735
#39 pyrun_file at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1630
#40 _PyRun_SimpleFileObject at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:440
#41 _PyRun_AnyFileObject at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:79
#42 pymain_run_file_obj at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:360
#43 pymain_run_file at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:379
#44 pymain_run_python at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:601
#45 Py_RunMain at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:680
#46 Py_BytesMain at
/usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:734
#47 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58
#48 __libc_start_main_impl at ../csu/libc-start.c:360
#49 _start
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2185830
2 hours, 26 minutes
[Bug 2095164] New: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
Bug ID: 2095164
Summary: Conversion region of ibus-anthy is invisible in
konsole, kwrite, kate
Product: Fedora
Version: 36
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 1888253
--> https://bugzilla.redhat.com/attachment.cgi?id=1888253&action=edit
Video showing the the conversion region is visible in some places but
invisible in konsole, kwrite, kate
Using Fedora-Workstation-Live-x86_64-36-1.2.iso installed in qemu-kvm with all
current updates.
kwrite, kate, and konsole, do not show the conversion region when using
ibus-anthy
konsole5-22.04.1-1.fc36.x86_64
kwrite-22.04.1-1.fc36.x86_64
kate-21.12.2-1.fc36.x86_64
It does not matter whether these programs are used in
Plasma(X11), Plasma(Wayland), Gnome(Xorg), Gnome(Wayland), the behaviour is
always the same, the conversion region is never visible.
In konsole the behaviour is even worse because not even the cursor is shown at
the start of the conversion region.
When testing in Plasma(Wayland) or Plasma(X11) and typing with ibus-anthy into
the search field of the KDE control center, the conversion region is coloured
and thus visible. It is also visible when typing into the entry field for a
command which opens with Alt+F2. So there are only some programs in KDE where
it does not work like konsole, kwrite, kate, ... whereas it works in other
places.
See the attached video.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095164
2 hours, 49 minutes
[Bug 2090204] New: [abrt] ibus: __strndup(): ibus-extension-gtk3
killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2090204
Bug ID: 2090204
Summary: [abrt] ibus: __strndup(): ibus-extension-gtk3 killed
by SIGSEGV
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:8c2b2d109d6c6600cfdf1e41632f3398d6d21e15;VAR
IANT_ID=workstation;
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
Description of problem:
Version-Release number of selected component:
ibus-1.5.26-6.fc36
Additional info:
reporter: libreport-2.17.1
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
cmdline: /usr/libexec/ibus-extension-gtk3
crash_function: __strndup
dso_list: /usr/libexec/ibus-extension-gtk3 ibus-1.5.26-6.fc36.x86_64
(Fedora Project) 1653401127
executable: /usr/libexec/ibus-extension-gtk3
journald_cursor:
s=3da4198b50ed40bb8e39aac19c44f062;i=15b44;b=4f87f45459b64f7299ca0a57d8a15df6;m=51ec68d6;t=5dfc2daddfca9;x=e27b7bc9d78e7740
kernel: 5.17.9-300.fc36.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2090204
2 hours, 49 minutes
[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.
2 hours, 52 minutes
[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1847347
Bug ID: 1847347
Summary: gnome-terminal and xfce4-terminal get surrounding text
from previous application
Product: Fedora
Version: 32
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 made the following screenshots and video by testing on Gnome-Xorg, but the
problem occurs on Gnome-Wayland as well.
How to reproduce (see also attached screenshots and video):
- To show what happens with the surrounding text, I first opened the
setup tool of ibus-typing-booster and set the debug level in the
options tab to 3.
When the debug level is high, the auxiliary text above the candidate
list shows what context has been obtained by using surrounding text
(if surrounding text is available, if it is not available like when
using xterm, the context is just remembered from what was typed
last).
- I opened 3 windows: gedit, firefox, and gnome-terminal.
- I focus on gedit and type "a b c d e"
On top of the candidate list one can see: "Context: b c d"
This is because when the letter "e" was typed, ibus-typing-booster
got the surrounding text at the cursor position and parsed the last
3 tokens left of the cursor out of the result. And these
last 3 tokens left of the cursor are "b c d".
- Now I focus on firefox and type "f g h i j"
On top of the candidate list one can see: "Context: g h i"
I.e. the correct context "g h i" to the left of the just typed "j"
(which is still in preedit) has been found using surrounding text.
- Now I focus on gnome-terminal and type "k l m"
On top of the candidate list one can see: "Context h i j"
This comes from the surrounding text left of the cursor in
*firefox*, *not* from gnome-terminal.
Although gnome-terminal reports that surrounding text is supported, i.e.
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is True (see the code to get the context at:
https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hun...
)
gnome-terminal does not really seem to support surrounding text.
The surrounding text comes from the previous client which really supported
surrounding text.
If the previous client was firefox, one still gets the surrounding text from
firefox while typing in gnome-terminal.
Same with gedit, if the previous client before focussing on gnome-terminal
was gedit, one still gets the surrounding text from gedit while typing in
gnome-terminal.
- The same problem occurs when using xfce4-terminal instead of gnome-terminal.
- When using xterm, the problem does *not* occur because when using xterm
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is False and then the get_context() immediately returns and the context
remembered from the last text typed is used as a fallback.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 hours, 52 minutes
[Bug 2258723] New: Variable fonts packages dont include all axis
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2258723
Bug ID: 2258723
Summary: Variable fonts packages dont include all axis
Product: Fedora
Version: 39
OS: Linux
Status: NEW
Component: google-noto-fonts
Keywords: RFE
Severity: low
Assignee: tagoh(a)redhat.com
Reporter: sharpenedblade(a)proton.me
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
The *-vf packages package files from the `slim-variable-ttf` dir, which do not
include every axis available for the font. Variable font files with all
supported axis are in `variable-ttf` dir instead.
Reproducible: Always
Steps to Reproduce:
1. Install `google-noto-sans-vf`
2. Check which axis are supported
3. Download
`https://github.com/notofonts/notofonts.github.io/archive/refs/tags/noto-monthly-release-23.8.1.tar.gz`
and look in the `fonts/NotoSans/unhinted/variable-ttf` direcotry
Actual Results:
Only the weight axis is variable in this package
Expected Results:
The weight and width axis are variable in this package
Changing the path at
https://src.fedoraproject.org/rpms/google-noto-fonts/blob/rawhide/f/googl...
works for every variable font/script except for NotoKufiArabic, which has the
complete font files in the `variable` dir.
Before compression, this is ~16mb larger than before (total, across all
subpackages).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2258723
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 day, 12 hours