https://bugzilla.redhat.com/show_bug.cgi?id=2004265
Bug ID: 2004265
Summary: Official name of Taiwan is wrong
Product: Fedora
Version: 35
Hardware: All
Status: NEW
Component: iso-codes
Assignee: pnemade(a)redhat.com
Reporter: julian.g(a)posteo.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "official name" of the country on Taiwan is wrong. It states "Province of
China", which is obviously not its official name. No country would call itself
"Province" of another country. The official name is "Republic of China".
Some sources:
- Official government website https://www.taiwan.gov.tw by the RoC Ministry of
Foreign Affairs
- You can ask any person living on the Island.
- As an IT person, you might have some hardware labeled "Made in RoC".
- The Hong Kong and the Taiwanese locale both have "中華民國" as a translation,
which means "Republic of China".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2004265
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
https://bugzilla.redhat.com/show_bug.cgi?id=2076596
Bug ID: 2076596
Summary: The KDE ibus panel does not work as expected.
Product: Fedora
Version: 36
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: lruzicka(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 1873514
--> https://bugzilla.redhat.com/attachment.cgi?id=1873514&action=edit
The ibus panel with incorrect layout.
Description of problem:
I have freshly installed KDE Live 20220418 and made following settings during
the installation:
* System language is English.
* Keyboard layout is Czech.
After the installation, the keyboard is correctly laid out to "czech" and uses
the correct czech mappings. When I check for the system settings using
`localectl status`, I get the same result:
===
System Locale: LANG=en_US.UTF-8
VC Keymap: cz
X11 Layout: cz
===
However, when I log into the KDE session, the IBUS-panel shows incorrectly
"EN", but the layout is not English and even when I specifically select it
using the panel, it does not have any influence.
Also, when I use the panel to add other languages, it does not affect the
system layout which is used for the KDE session, as well as for applications
(kwrite, konsole), which remains "czech" all the time.
Version-Release number of selected component (if applicable):
ibus-1.5.26-3
KDE Plasma 5.24.4
How reproducible:
Always
Steps to Reproduce:
1. Install KDE Live with non-english layout (as the only one)
2. Log into the newly installed session.
3. See if ibus-panel shows the correct layout.
4. Try using ibus-panel to modify keyboard layout in the KDE session.
Actual results:
ibus-panel cannot modify keyboard layout
Expected results:
ibus-panel should be able to modify keyboard layout or should not be the
default method to do so.
Additional info:
See screenshot
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2076596
https://bugzilla.redhat.com/show_bug.cgi?id=2209413
Bug ID: 2209413
Summary: Prepare for DNF 5, don't depend on `dnf`
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: system-config-language
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: egoode(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com
Target Milestone: ---
Classification: Fedora
(I'm filing issues with all the packages that currently depend on `dnf`.)
DNF 5 is a new package manager that will replace DNF 4 in Fedora 39+: Starting
in Fedora 39, the `dnf` command will be provided by the `dnf5` package rather
than the `dnf` package, and `dnf5` will obsolete `dnf`. Since
system-config-language currently depends on DNF 4, it should choose one of the
following strategies to avoid breaking the Fedora upgrade:
- Add support for DNF 5, and depend on the `dnf5` package in Fedora 39+ instead
of `dnf`. Builds of DNF 5 are available in this COPR repository:
https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf-nightly/, and
documentation is available here: https://dnf5.readthedocs.io/en/latest/.
- Alternatively, or in the meantime, change the system-config-language package
to depend on `python3-dnf` instead of `dnf`, and call the `dnf-3` binary
instead of `dnf`. The old DNF 4 command will still be available in the
distribution, but only as `dnf-3` (the binary is called `dnf-3` rather than
`dnf4` for historical reasons; it is the "Python 3 version" of DNF). The first
option is preferred to this one; it is not recommended to modify installed
software using both DNF 4 and DNF 5 on the same system.
- Or, if this package is no longer being maintained, consider removing it from
Fedora.
At some point, this project should adopt DNF 5, but the immediate issue is
removing the dependency on `dnf`. We are planning to replace DNF with DNF5 in
Fedora Rawhide very soon, by 2023-06-01, and the system-config-language package
will break as long as it still depends on the `dnf` package.
For more information about the switch to DNF 5, see
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5.
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2209413
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
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
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