https://bugzilla.redhat.com/show_bug.cgi?id=2382958
Bug ID: 2382958
Summary: lklug-fonts: STI tests will no longer be run in F43
Product: Fedora
Version: rawhide
Status: NEW
Component: lklug-fonts
Assignee: sshil(a)redhat.com
Reporter: fedora(a)lecris.me
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pnemade(a)redhat.com,
sshil(a)redhat.com
Blocks: 2346261
Target Milestone: ---
Classification: Fedora
Dear package maintainer,
This is an automated bug created due to the announced change proposal
Disablement of STI tests.
Your project still has STI tests under `tests/tests*.yml`, which will no longer
be run soon. We suggest you
migrate these tests to TMT format instead.
In the simplest case when the STI tests is a simple wrapper around a
`tests/run_tests.sh`, the migration would
look like this:
```
$ tmt init
$ rm tests/tests.yml
$ cat <<EOF > ./plans.fmf
summary: Run all smoke tests
discover:
how: fmf
execute:
how: tmt
EOF
$ cat <<EOF > ./tests/main.fmf
summary: Smoke test
test: ./run_tests.sh
EOF
```
See https://fedoraproject.org/wiki/Changes/DisableSTI for more information,
including a link to a migration
guide.
Feel free to reach out to us here or in #fedora-ci or #tmt matrix rooms if you
need any help.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2346261
[Bug 2346261] Disablement of STI tests
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2382958
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=2363980
Bug ID: 2363980
Summary: [abrt] ibus-typing-booster: __getattr__():
_multiarray_umath.py:44:__getattr__:ImportError:
Product: Fedora
Version: 41
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:58ea2c321299b3c39013522c48d5067979462ceb;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: fedora(a)webmaxx.name
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-typing-booster-2.27.42-1.fc41
Additional info:
reporter: libreport-2.17.15
kernel: 6.14.4-200.fc41.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: _multiarray_umath.py:44:__getattr__:ImportError:
executable: /usr/share/ibus-typing-booster/engine/main.py
type: Python3
package: ibus-typing-booster-2.27.42-1.fc41
runlevel: unknown
exception_type: ImportError
crash_function: __getattr__
interpreter: python3-3.13.3-2.fc41.x86_64
Truncated backtrace:
_multiarray_umath.py:44:__getattr__:ImportError:
A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.1.3 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.
Traceback (most recent call last):
File
"/home/maxx/.local/lib/python3.13/site-packages/numpy/core/_multiarray_umath.py",
line 44, in __getattr__
raise ImportError(msg)
ImportError:
A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.1.3 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.
Local variables in innermost frame:
attr_name: '_ARRAY_API'
_multiarray_umath: <module 'numpy._core._multiarray_umath' from
'/home/maxx/.local/lib/python3.13/site-packages/numpy/_core/_multiarray_umath.cpython-313-x86_64-linux-gnu.so'>
_raise_warning: <function _raise_warning at 0x7fde242f1260>
short_version: '2.1.3'
textwrap: <module 'textwrap' from '/usr/lib64/python3.13/textwrap.py'>
traceback: <module 'traceback' from '/usr/lib64/python3.13/traceback.py'>
sys: <module 'sys' (built-in)>
msg: "\nA module that was compiled using NumPy 1.x cannot be run in\nNumPy
2.1.3 as it may crash. To support both 1.x and 2.x\nversions of NumPy, modules
must be compiled with NumPy 2.0.\nSome module may need to rebuild instead e.g.
with 'pybind11>=2.12'.\n\nIf you are a user of the module, the easiest solution
will be to\ndowngrade to 'numpy<2' or try to upgrade the affected module.\nWe
expect that some modules will need time to support NumPy 2.\n\n"
tb_msg: 'Traceback (most recent call last): File
"/usr/share/ibus-typing-booster/engine/main.py", line 133, in <module>\n
import factory\n File "/usr/share/ibus-typing-booster/engine/factory.py", line
37, in <module>\n import hunspell_table\n File
"/usr/share/ibus-typing-booster/engine/hunspell_table.py", line 58, in
<module>\n import itb_emoji\n File
"/usr/share/ibus-typing-booster/engine/itb_emoji.py", line 52, in <module>\n
import rapidfuzz\n File
"/usr/lib64/python3.13/site-packages/rapidfuzz/__init__.py", line 16, in
<module>\n from rapidfuzz import distance, fuzz, process, utils\n File
"/usr/lib64/python3.13/site-packages/rapidfuzz/distance/__init__.py", line 6,
in <module>\n from . import (\n File
"/usr/lib64/python3.13/site-packages/rapidfuzz/distance/OSA.py", line 5, in
<module>\n from rapidfuzz._utils import fallback_import as
_fallback_import\n File
"/usr/lib64/python3.13/site-packages/rapidfuzz/_utils.py", line 15, in
<module>\n from pandas import NA as pandas_NA\n File
"/home/maxx/.local/lib/python3.13/site-packages/pandas/__init__.py", line 26,
in <module>\n from pandas.compat import (\n File
"/home/maxx/.local/lib/python3.13/site-packages/pandas/compat/__init__.py",
line 27, in <module>\n from pandas.compat.pyarrow import (\n File
"/home/maxx/.local/lib/python3.13/site-packages/pandas/compat/pyarrow.py", line
8, in <module>\n import pyarrow as pa\n File
"/usr/lib64/python3.13/site-packages/pyarrow/__init__.py", line 65, in
<module>\n import pyarrow.lib as _lib\n'
line: ' File "<frozen importlib._bootstrap>", line 488, in
_call_with_frames_removed\n'
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2363980
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=2326971
Bug ID: 2326971
Summary: [abrt] ibus-typing-booster: Py_Exit(): python3.13
killed by SIGABRT
Product: Fedora
Version: 41
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:1016fbf3f898a8e267bb35897e7a7417c6d30f73;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: caferinograal(a)hotmail.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:
Switching between X11 and Wayland provokes these all the time. I got serious
keyboard issues with keys 'n', 'b', 'caps lock' and 'f1', they sometimes get
stuck so bad, get ignored or repeated, so constantly and so bad after playing a
game like WoW in Lutris. I hope this is close to the problem
Version-Release number of selected component:
ibus-typing-booster-2.26.8-1.fc41
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.13 killed by SIGABRT
journald_cursor:
s=591db716e92c4be4b4be69dcae179483;i=292599;b=c8be905267374bac9f025aaa31014421;m=4039cb539;t=6272e72d6223d;x=7b92b077f6a5b5d1
executable: /usr/bin/python3.13
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.11.7-300.fc41.x86_64
package: ibus-typing-booster-2.26.8-1.fc41
runlevel: N 5
backtrace_rating: 4
crash_function: Py_Exit
comment: Switching between X11 and Wayland provokes these all the time.
I got serious keyboard issues with keys 'n', 'b', 'caps lock' and 'f1', they
sometimes get stuck so bad, get ignored or repeated, so constantly and so bad
after playing a game like WoW in Lutris. I hope this is close to the problem
Truncated backtrace:
Thread no. 1 (36 frames)
#5 Py_Exit at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pylifecycle.c:3396
#6 handle_system_exit at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:635
#7 _PyErr_PrintEx at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:644
#8 PyErr_PrintEx at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:721
#9 pygi_signal_closure_marshal at ../gi/pygi-signal-closure.c:202
#11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3887
#12 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519
#16 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3887
#17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519
#20 emit_closed_in_idle at ../gio/gdbusconnection.c:1502
#23 g_main_context_dispatch_unlocked at ../glib/gmain.c:4208
#24 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4273
#26 ffi_call_unix64 at ../src/x86/unix64.S:104
#27 ffi_call_int at ../src/x86/ffi64.c:673
#28 ffi_call at ../src/x86/ffi64.c:710
#29 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684
#30 pygi_function_cache_invoke at ../gi/pygi-cache.c:862
#31 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727
#32 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764
#33 _callable_info_call at ../gi/pygi-info.c:548
#35 _PyObject_MakeTpCall at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Objects/call.c:242
#36 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/generated_cases.c.h:813
#37 PyEval_EvalCode at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/ceval.c:596
#38 run_eval_code_obj at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1323
#39 run_mod at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1408
#40 pyrun_file at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1241
#41 _PyRun_SimpleFileObject at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:490
#42 _PyRun_AnyFileObject at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:77
#43 pymain_run_file_obj at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:409
#44 pymain_run_file at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:428
#45 pymain_run_python at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:696
#46 Py_RunMain at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:775
#47 Py_BytesMain at
/usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:829
#48 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58
#49 __libc_start_main_impl at ../csu/libc-start.c:360
#50 _start
Potential duplicate: bug 2185830
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2326971
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=2326178
Bug ID: 2326178
Summary: Input method on login screen does not change to
English
Product: Fedora
Version: 41
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Keywords: Desktop
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: tpardesh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
On login screen, while typing the password in English, the input method
displayed is not English. The input method is displayed as per the locale the
system is installed in.
Reproducible: Always
Steps to Reproduce:
1. Install Fedora in any locale. Ex - Japanese
2. Create user and password during installation
3. Check the login screen after installation. On the top right corner, you will
see anthy (if we install system in Japanese locale) as default input method
4. Press enter on the login screen and try to enter the password. You will be
typing the password in English but the input method displayed will be anthy but
expected is English.
5. After login, expected input method(English) is displayed properly.
Actual Results:
The password is typed in English but the input method on the top right corner
does not display English as default.
Expected Results:
The input method must be English as password is typed to English to login
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2326178
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…