https://bugzilla.redhat.com/show_bug.cgi?id=2431892
Bug ID: 2431892
Summary: Provide a meta-package that prioritizes VFs
Product: Fedora
Version: 43
Hardware: x86_64
OS: Linux
Status: NEW
Component: google-noto-fonts
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: EpicTux123(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
Hi there.
Currently, the "google-noto-fonts-all" meta-package installs many font
duplicates. Fedora seems to prever VF variants (
https://fedoraproject.org/wiki/Changes/VariableNotoFonts ,
https://fedoraproject.org/wiki/Changes/Noto_CJK_Variable_Fonts ), but the
meta-package installs both Static and VF variants of the same fonts. Example
from command "dnf repoquery --requires google-noto-fonts-all":
------------------------------------------------------
google-noto-serif-hebrew-fonts = 20250901-1.fc43
google-noto-serif-hebrew-fonts = 20251101-2.fc43
google-noto-serif-hebrew-vf-fonts = 20250901-1.fc43
google-noto-serif-hebrew-vf-fonts = 20251101-2.fc43
------------------------------------------------------
I would like to request the creation of a meta-package that prioritizes VF
variants and don't install their equivalent duplicates in Static variant.
For example, the meta-package would install Hebrew VF fonts, but not Hebrew
Static fonts.
This eliminates the duplicates, while still keeping the Static fonts in a
meta-package for the fonts that don't have VF variants.
Additional note: the current "google-noto-fonts-all" should probably install
the other "-all" meta-packages as well, since it includes all of their deps as
well.
Thanks.
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=2431892
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=2428613
Bug ID: 2428613
Summary: "IBus Wayland integration fails in Fedora 44 Budgie"
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Keywords: Desktop, Translation
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: yusufxkhalid(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
the problem is how ibus integrates with Wayland. This results in DBus errors,
wallpaper failures, and screensaver crash notifications. IBus should be called
from the
desktop session in Wayland. For
KDE, you can launch
systemsettings utility and go
to “Input & Output” → “Keyboard”
→ “Virtual Keyboard” section and
select “IBus wayland” icon and
click “Apply” button to configure
IBus in Wayland. For other
desktop sessions, you can run
ibus start command. Please
refer each document about the
“Wayland input method”
configuration. Before you
configure the “Wayland input
method”, you should make sure
that QT_IM_MODULE and
GTK_IM_MODULE environment
variables are unset in the
desktop session.
Reproducible: Always
Steps to Reproduce:
1.Install Fedora 44 Budgie Rawhide
2. Log into Budgie (Wayland)
3.Use the default installed packages
4. Observe desktop startup and notifications
Actual Results:
IBus should be called from the
desktop session in Wayland. For
KDE, you can launch
systemsettings utility and go
to “Input & Output” → “Keyboard”
→ “Virtual Keyboard” section and
select “IBus wayland” icon and
click “Apply” button to configure
IBus in Wayland. For other
desktop sessions, you can run
ibus start command. Please
refer each document about the
“Wayland input method”
configuration. Before you
configure the “Wayland input
method”, you should make sure
that QT_IM_MODULE and
GTK_IM_MODULE environment
variables are unset in the
desktop session.
Expected Results:
Login should be smooth with no error message.
Additional Information:
rpm -q swaylock
package swaylock is not installed
yusufk@fedora:~$ which swaylock
/usr/bin/which: no swaylock in
(/home/yusufk/.local/bin:/home/yusufk/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
yusufk@fedora:~$ rpm -q gtklock
gtklock-4.0.0-2.fc44.x86_64
yusufk@fedora:~$ rpm -q budgie-screensaver
package budgie-screensaver is not installed
yusufk@fedora:~$ rpm -q budgie-session
budgie-session-1.0.0-1.fc44.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=2428613
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=2429288
Bug ID: 2429288
Summary: CVE-2026-22693 harfbuzz: Null Pointer Dereference in
harfbuzz [fedora-43]
Product: Fedora
Version: 43
Status: NEW
Whiteboard: {"flaws": ["9a132224-d774-465d-b84b-e175909efd82"]}
Component: harfbuzz
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: pnemade(a)redhat.com
Reporter: jmoroney(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
kalevlember(a)gmail.com, moceap(a)hotmail.com,
pnemade(a)redhat.com
Blocks: 2428439
Target Milestone: ---
Classification: Fedora
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2429288
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=2429736
Bug ID: 2429736
Summary: Can't login with diacritics in a password after update
Product: Fedora
Version: 43
URL: https://gitlab.gnome.org/GNOME/gdm/-/issues/1018
OS: Linux
Status: NEW
Component: ibus
Keywords: Regression
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: monteiro(a)protonmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
After a recent update fedora regressed and is no longer possible to login
normally with diacritics in the password field.
Apparently was a regression in IBUS and it was fixed already upstream but at
least not yet in current fedora silverblue 43.
Reproducible: Always
Steps to Reproduce:
1. Use diacritics in the password of a user.
2. Try to login in GDM right after booting with diacritics in the password.
Actual Results:
Diacritics don't work properly.
Expected Results:
Should be able to use diacritics in the password field.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2429736
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=2402600
Bug ID: 2402600
Summary: google-roboto-fonts-3.013 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: google-roboto-fonts
Keywords: FutureFeature, Triaged
Assignee: dtardon(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: davide(a)cavalca.name, dtardon(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Releases retrieved: 3.000, 3.001, 3.002, 3.003, 3.004, 3.005, 3.006, 3.007,
3.008, 3.009, 3.010, 3.011, 3.012, 3.013
Upstream release that is considered latest: 3.013
Current version/release in rawhide: 2.138-20.fc43
URL: https://github.com/googlefonts/roboto-3-classic
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/12041/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/google-roboto-fonts
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2402600
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=2425585
Bug ID: 2425585
Summary: IBus not initialized correctly in LXQt
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: me(a)basilcrow.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
When I start LXQt (including the Fedora LXQt Spin Live ISO), I get the
following notification:
> IBus should be called from the desktop session in Wayland. For KDE, you can launch ‘systemsettings5’ utility and go to “Input Devices” → “Virtual Keyboard” section and select “IBus Wayland” icon and click “Apply” button to configure IBus in Wayland. For other desktop sessions, you can copy the ‘Exec=’ line in org.freedesktop.IBus.Panel.Wayland.Gtk3.desktop file to a configuration file of the session. Please refer each document about the “Wayland input method” configuration. Before you configure the “Wayland input method”, you should make sure that QT_IM_MODULE and GTK_IM_MODULE environment variables are unset in the desktop session.
I followed this advice and added a ~/.config/autostart/ibus-wayland.desktop
file calling
Exec=/usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args
"--xim --panel disable"
just as in org.freedesktop.IBus.Panel.Wayland.Gtk3.desktop. But that didn't
stop the notice from appearing. The only thing that made the notice disappear
was removing the imsettings and im-chooser packages. This seems like a bug.
Reproducible: Always
Steps to Reproduce:
1. Start LXQt from the Live ISO (or the result of installing it).
2. Log in.
Actual Results:
You see the annoying message printed above.
Expected Results:
No annoying message should be printed. IBus should be initialized correctly by
default.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2425585
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…