https://bugzilla.redhat.com/show_bug.cgi?id=2436031
Bug ID: 2436031
Summary: [abrt] ibus-typing-booster:
_atspi_dbus_call_partial_va(): python3.14 killed by
SIGSEGV
Product: Fedora
Version: 43
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:73256a6f593877c8123e20da5fd990c7e6846fca;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: 4242eli(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
gnome calendar crashes when you select a day open the keyboard and when you
type one word. if you using x11 problem not occur.
Version-Release number of selected component:
ibus-typing-booster-2.30.2-1.fc43
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.14 killed by SIGSEGV
journald_cursor:
s=c88be49776e442c1ad412a666ac413fb;i=12dbd;b=10fd69e491504b4abfa7699dd7b003fe;m=3a9ef5a;t=649ca92597c7d;x=3038981150607bef
executable: /usr/bin/python3.14
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.18.7-1.surface.fc43.x86_64
package: ibus-typing-booster-2.30.2-1.fc43
runlevel: /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: _atspi_dbus_call_partial_va
comment: gnome calendar crashes when you select a day open the keyboard
and when you type one word. if you using x11 problem not occur.
Truncated backtrace:
Thread no. 1 (30 frames)
#0 _atspi_dbus_call_partial_va at ../atspi/atspi-misc.c:1321
#1 _atspi_dbus_call_partial at ../atspi/atspi-misc.c:1361
#2 atspi_accessible_get_state_set at ../atspi/atspi-accessible.c:734
#4 ffi_call_unix64 at ../src/x86/unix64.S:104
#5 ffi_call_int at ../src/x86/ffi64.c:676
#6 ffi_call at ../src/x86/ffi64.c:713
#7 pygi_invoke_c_callable at ../gi/pygi-invoke.c:711
#8 pygi_function_cache_invoke at ../gi/pygi-cache.c:838
#9 pygi_callable_info_invoke at ../gi/pygi-invoke.c:756
#10 _callable_info_vectorcall at ../gi/pygi-info.c:547
#11 _function_info_vectorcall at ../gi/pygi-info.c:611
#12 _PyObject_VectorcallTstate at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_call.h:169
#13 PyObject_Vectorcall at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Objects/call.c:327
#14 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/generated_cases.c.h:4079
#15 _PyEval_EvalFrame at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_ceval.h:121
#16 _PyEval_Vector at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/ceval.c:2083
#17 _PyFunction_Vectorcall at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Objects/call.c:413
#18 _PyObject_VectorcallTstate at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_call.h:169
#19 method_vectorcall at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Objects/classobject.c:73
#20 _PyObject_VectorcallTstate at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_call.h:169
#21 context_run at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/context.c:728
#22 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/generated_cases.c.h:3744
#23 _PyEval_EvalFrame at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_ceval.h:121
#24 _PyEval_Vector at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/ceval.c:2083
#25 _PyFunction_Vectorcall at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Objects/call.c:413
#26 _PyObject_VectorcallTstate at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Include/internal/pycore_call.h:169
#27 method_vectorcall at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Objects/classobject.c:73
#28 thread_run at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Modules/_threadmodule.c:359
#29 pythread_wrapper at
/usr/src/debug/python3.14-3.14.2-1.fc43.x86_64/Python/thread_pthread.h:242
#31 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Potential duplicate: bug 2328000
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2436031
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2417582
Bug ID: 2417582
Summary: [abrt] ibus-libpinyin: _check_offset():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 43
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:4a46cf28b71b7bda85a0968e1bf6ade5d591a433;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: rimacc2ev(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:
When choosing parts of chinese characters,this issue may appear randomly.
Sorry for cannot provide the detailed reproduce steps.
Version-Release number of selected component:
ibus-libpinyin-1.16.5-2.fc43
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-engine-libpinyin killed by SIGABRT
journald_cursor:
s=bc9246776a724277b46330b2f1aee892;i=78307;b=6dd9b410261f4251bd0aa2d6b9fc6181;m=1b2bf92437;t=6448761901280;x=be24863ca019a1bd
executable: /usr/libexec/ibus-engine-libpinyin
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.17.8-300.fc43.x86_64
package: ibus-libpinyin-1.16.5-2.fc43
runlevel: /bin/sh: 行 1: runlevel: 未找到命令
backtrace_rating: 4
crash_function: _check_offset
Truncated backtrace:
Thread no. 1 (16 frames)
#5 _check_offset at
/usr/src/debug/libpinyin-2.10.2-2.fc43.x86_64/src/pinyin.cpp:2173
#6 pinyin_guess_candidates at
/usr/src/debug/libpinyin-2.10.2-2.fc43.x86_64/src/pinyin.cpp:2222
#7 PY::PhoneticEditor::update at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:355
#8 PY::PhoneticEditor::selectCandidate at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:529
#9 PY::PhoneticEditor::selectCandidateInPage at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:547
#10 PY::PinyinEditor::processNumber at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEditor.cc:81
#11 PY::PinyinEditor::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEditor.cc:204
#12 PY::PinyinEngine::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEngine.cc:437
#13 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at
/usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusmarshalers.c:280
#17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3548
#20 ibus_engine_service_method_call at
/usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusengine.c:1323
#21 call_in_idle_cb at ../gio/gdbusconnection.c:5476
#24 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425
#25 g_main_context_iterate_unlocked at ../glib/gmain.c:4490
#27 ibus_main at /usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusshare.c:336
#28 start_component at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYMain.cc:161
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2417582
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Bug ID: 2395836
Summary: don't combine pinyin Chinese IME and bopomofo Chinese
IME into one single package
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-libpinyin
Keywords: Desktop, RFE
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: lutingrong(a)hotmail.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
Hello the authors of ibus-libpinyin ,
I'm using ibus-libpinyin on fedora 42 . I found ibus-libpinyin provides both
pinyin Chinese IME and bopomofo Chinese IME . Could you please consider split
ibus-libpinyin into ibus-libpinyin and ibus-libbopomofo ? The reason is that
those who use pinyin IME doesn't know bopomofo IME at all , and vice verse
those who use bopomofo IME doesn't know pinyin IME neither . So I can install
only the package which I use . Why must combine pinyin IME and bopomofo IME
into one single package ? Most hope there is no unnecessary codes in their
computers . Hope ibus-libpinyin more modularized and more divided ! Thanks for
your time and consideration!
Best regards,
Tingrong
Reproducible: Always
Steps to Reproduce:
1. sudo dnf install ibus-libpinyin
2. ibus-setup
3. will see there are both pinyin Chinese IME and bopomofo Chinese IME
Actual Results:
one single package -- ibus-libpinyin provides more than one IME .
Expected Results:
one package provides only one IME .
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2319795
Bug ID: 2319795
Summary: Please branch and build translate-toolkit for EPEL 10
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Assignee: petersen(a)redhat.com
Reporter: xavier(a)bachelot.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, sshil(a)redhat.com,
sundeep_anand(a)yahoo.com
Blocks: 2303880 (EPEL10Tracker)
Target Milestone: ---
Classification: Fedora
Hi,
Could you please branch and build translate-toolkit for EPEL 10 ?
It is needed to build another package.
Regards,
Xavier
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2303880
[Bug 2303880] EPEL 10 Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2319795
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
Bug ID: 2368622
Summary: ibus-daemon uses insane amounts of CPU and causes a
laggy experience
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Keywords: Desktop
Severity: high
Assignee: tfujiwar(a)redhat.com
Reporter: torvalds(a)linux-foundation.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Not a lot of details here, but I decided that instead of just fixing it with
killall ibus-daemon
which gets rid of that broken thing, I would at least open a bug report to see
if there is some official fix for this.
Google shows a lot of people complaining about this going back years, so it's
not me.
There's no crash, and no obvious system logs either. All I see in system logs
is gdm-wayland-session activating, and when I kill it systemd seems to log
consumtion information like
org.freedesktop.IBus.session.GNOME.service: Consumed 26min 22.196s CPU
time, 125.1M memory peak.
(That was after the system had been up for one day, so 26 min of CPU time seems
pretty excessive)
Reproducible: Sometimes
Steps to Reproduce:
1. Boot the system
2. Be happy
3. Some time randomly later, notice laggy behavior and ibus-daemon using 100%
CPU in top
Actual Results:
Slow keyboard response on a fast system
Expected Results:
Snappy action
Additional Information:
Sorry for the horrible bug report, but can we please just disable ibus-daemon
by default as a useless problem-causing thing?
When google shows this problem going back AT LEAST to 2020 (and probably
longer), with the solution invariably being "kill, restart or disable
ibus-daemon to fix the problem temporarily", why is that thing enabled by
default in the first place?
Please at least give a good setting for this, so that the answer can be for
people to not enable that thing.
And if somebody has "please debug this next time it happens by doing Xyz", I'll
happily do that. But you need to tell me what Xyz is, because I don't know the
first thing about ibus-daemon.
I know that the "i" is supposed to stand for "intelligent". But honestly, I can
come up with a lot better suggestions for what that "i" might stand for. And
absolutely *none* of them are polite.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2368622
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2378003
Bug ID: 2378003
Summary: python-polib: Stop using deprecated
%py3_build/%py3_install macros
Product: Fedora
Version: rawhide
Status: NEW
Component: python-polib
Assignee: petersen(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, reallylongword(a)gmail.com,
sundeep_anand(a)yahoo.com
Blocks: 2376118
Target Milestone: ---
Classification: Fedora
Dear package maintainer,
this bugzilla is automated becasue the number of impacted packages it too high
to go trough manually.
It appears that your package uses the deprecated %py3_build and/or %py3_install
macro.
See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros for why the
macros are deprecated.
%py3_install expands to python setup.py install. This has been a deprecated
command for 5 years and will likely stop working in Fedora 45.
Please migrate to %pyproject_buildrequires + %pyproject_wheel +
%pyproject_install macros instead.
See
https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros#Migrating_to_…
for migration guide.
See https://github.com/hroncok/pyprojectize/ for a tool that can help you
automate the migration.
Thank you. Let me know if you need help.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2376118
[Bug 2376118] Deprecate RPM Macros for setup.py-based Python Builds
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2378003
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…