[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-...
2 hours, 10 minutes
[Bug 2277316] New: Included CMake config file is broken
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2277316
Bug ID: 2277316
Summary: Included CMake config file is broken
Product: Fedora
Version: 40
Hardware: x86_64
OS: Linux
Status: NEW
Component: harfbuzz
Severity: medium
Assignee: pnemade(a)redhat.com
Reporter: michael(a)cullen-online.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com
Target Milestone: ---
Classification: Fedora
The included CMake configuration file (in
/usr/lib64/cmake/harfbuzz/harfbuzz-config.cmake) is broken - it appears to
contain unsubstituted autoconf variables.
Reproducible: Always
Steps to Reproduce:
1. build something attempting to pull in harfbuzz via CMake -
find_package(harfbuzz REQUIRED)
Actual Results:
CMake Error at /usr/lib64/cmake/harfbuzz/harfbuzz-config.cmake:1:
Parse error. Expected a command name, got unquoted argument with text
"@PACKAGE_INIT@".
Call Stack (most recent call first):
makefiles/TPSDKs.cmake:68 (find_package)
CMakeLists.txt:197 (include)
CMake Error at makefiles/TPSDKs.cmake:68 (find_package):
find_package Error reading CMake code from
"/usr/lib64/cmake/harfbuzz/harfbuzz-config.cmake".
Call Stack (most recent call first):
CMakeLists.txt:197 (include)
-- Configuring incomplete, errors occurred!
Expected Results:
Not produce errors
Looking at the RPMs, this is broken in F40 - both 8.3.0 and 8.4.0 - but looks
fine in F39's 8.2.1-2
I suspect the upstream change
https://github.com/harfbuzz/harfbuzz/commit/da9b838910e62825717a8b2de8ce9...
broke it by rewriting the file
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2277316
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
5 days, 9 hours
[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
6 days, 23 hours
[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
1 week, 5 days
[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
1 week, 5 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.
1 week, 5 days
[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
1 week, 5 days