[Bug 2011130] New: [abrt] ibus-mozc:
__gnu_cxx::__verbose_terminate_handler()(): ibus-engine-mozc killed by
SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2011130
Bug ID: 2011130
Summary: [abrt] ibus-mozc:
__gnu_cxx::__verbose_terminate_handler()():
ibus-engine-mozc killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:f003f9842f924762d98c734b478bf77d21a0e328;VAR
IANT_ID=matecompiz;
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: buribullet(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
1. Launch RStudio (rstudio-desktop-1.4.1717-2.fc34.x86_64)
2. Open new Rmd
3. Turn ibus-mozc on and Enter multilingual texts like Japanese hiragana.
Then, ibus-mozc dies with SEGV at mozc::ibus::(anonymous
namespace)::GetSurroundingText(_IBusEngine*,
mozc::ibus::SelectionMonitorInterface*, mozc::ibus::(anonymous
namespace)::SurroundingTextInfo*) [clone .part.0] [clone .constprop.0]
(engine=<optimized out>,
Version-Release number of selected component:
ibus-mozc-2.25.4190.102-5.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-engine-mozc --ibus
crash_function: __gnu_cxx::__verbose_terminate_handler()
executable: /usr/libexec/ibus-engine-mozc
journald_cursor:
s=56ad17da12da4eed800e68e166be00cd;i=7b37d1;b=f5aaea975c544d17b3b8f1ab25b1ec94;m=113dfa89293;t=5cd7162a6a7c5;x=5d0f1fdfb0e35252
kernel: 5.13.12-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#2 __gnu_cxx::__verbose_terminate_handler() at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#3 __cxxabiv1::__terminate(void (*)()) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#4 std::terminate() at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
#5 __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) at
../../../../libstdc++-v3/libsupc++/eh_throw.cc:95
#6 std::__throw_length_error(char const*) at
../../../../../libstdc++-v3/src/c++11/functexcept.cc:82
#7 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::_M_check_length(unsigned long, unsigned long, char
const*) const at /usr/include/c++/11/bits/basic_string.h:323
#8 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::_M_replace(unsigned long, unsigned long, char const*,
unsigned long) at /usr/include/c++/11/bits/basic_string.tcc:452
#9 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::replace(unsigned long, unsigned long, char const*,
unsigned long) at /usr/include/c++/11/bits/basic_string.h:1946
#10 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::replace(__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >) at
/usr/include/c++/11/bits/basic_string.h:2168
#11 std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::assign<__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, void>(__gnu_cxx::__normal_iterator<char const*,
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >
>, __gnu_cxx::__normal_iterator<char const*, std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >) at
/usr/include/c++/11/bits/basic_string.h:1478
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2011130
1 year, 4 months
[Fedora-i18n-bugs] [Bug 1899794] New: Fails to run on KDE in Rawhide
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1899794
Bug ID: 1899794
Summary: Fails to run on KDE in Rawhide
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: system-config-language
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
pnemade(a)redhat.com, psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
In current Rawhide, system-config-language is installed on KDE out of the box,
but fails to run. Running from a console, after you are prompted for the root
password, you get these errors:
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
(system-config-language.py:2146): Gtk-WARNING **: 18:09:41.831: cannot open
display: :1
then it exits back to the console.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 4 months
[Fedora-i18n-bugs] [Bug 1919963] New: /usr/share/doc/libunistring-devel/libunistring.html missing in devel
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1919963
Bug ID: 1919963
Summary: /usr/share/doc/libunistring-devel/libunistring.html
missing in devel
Product: Fedora
Version: 32
Hardware: All
OS: All
Status: NEW
Component: libunistring
Severity: medium
Assignee: p(a)draigbrady.com
Reporter: reini.urban(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jim(a)meyering.net, p(a)draigbrady.com,
redhat-bugzilla(a)linuxnetz.de
Target Milestone: ---
Classification: Fedora
Description of problem:
after installing libunistring and libunistring-devel the main doc entrypoint
for html is missing.
/usr/share/doc/libunistring-devel/libunistring.html
Version-Release number of selected component (if applicable):
libunistring-devel-0.9.10-7.fc32.x86_64
How reproducible:
Open a html doc, and click on Contents.
e.g firefox /usr/share/doc/libunistring-devel/libunistring_1.html
Haven't checked if that is an upstream problem, or just a bad rpm spec.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 4 months
[Bug 2001332] New: pango-view with --backend=ft2 and
---antialias=none generates antialiased renderings
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2001332
Bug ID: 2001332
Summary: pango-view with --backend=ft2 and ---antialias=none
generates antialiased renderings
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1820649
--> https://bugzilla.redhat.com/attachment.cgi?id=1820649&action=edit
image showing the problem
Description of problem:
Hello Fedora Team,
I have a recently updated Fedora 34 installation.
The problem I want to report is that it looks like
the pango-view tool is always turning antialiasing on
when one uses the FreeType backend --backend=ft2,
even when one explicitly switches antialiasing off with --antialias=none,
whereas it works for the --backend=cairo option.
A second question would be if the FreeType backend
generally doesn't/can't support --antialias=none?
I tried to find some examples in C with antialising turned off
but I wasn't successful.
I must confess I didn't check other distributions.
As pango-view is regarded as a tool for creating minimal reproducers
against the font rendering stack, I dare to set the severity to 'high' :-)
Best Regards
Andre
Version-Release number of selected component (if applicable):
$ uname -a
Linux localhost.localdomain 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dnf list installed | grep dejavu
dejavu-lgc-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-serif-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-serif-fonts.noarch 2.37-16.fc34
@fedora
$ dnf list installed | grep ImageMagick
ImageMagick.x86_64 1:6.9.11.27-3.fc34
@fedora
ImageMagick-libs.x86_64 1:6.9.11.27-3.fc34
@fedora
$ dnf list installed | grep pango
pango.i686 1.48.9-2.fc34
@updates
pango.x86_64 1.48.9-2.fc34
@updates
pango-devel.x86_64 1.48.9-2.fc34
@updates
pangomm.x86_64 2.46.1-1.fc34
@updates
$ dnf list installed | grep freetype
freetype.i686 2.10.4-3.fc34
@fedora
freetype.x86_64 2.10.4-3.fc34
@fedora
freetype-devel.x86_64 2.10.4-3.fc34
@fedora
$ dnf list installed | grep fontconfig
fontconfig.i686 2.13.94-2.fc34
@updates
fontconfig.x86_64 2.13.94-2.fc34
@updates
fontconfig-devel.x86_64 2.13.94-2.fc34
@updates
$ dnf list installed | grep cairo
cairo.i686 1.17.4-3.fc34
@fedora
cairo.x86_64 1.17.4-3.fc34
@fedora
cairo-devel.x86_64 1.17.4-3.fc34
@fedora
cairo-gobject.i686 1.17.4-3.fc34
@fedora
cairo-gobject.x86_64 1.17.4-3.fc34
@fedora
cairomm.x86_64 1.14.2-8.fc34
@fedora
python2-cairo.x86_64 1.18.2-8.fc34
@fedora
python3-cairo.x86_64 1.20.0-2.fc34
@fedora
How reproducible:
Always
Steps to Reproduce:
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-none.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-subpixel.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-none.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-subpixel.png
$ gimp abc-*.png
Actual results:
Attached pngs.
The file abc-ft2-aa-none.png is in gray-scale and not as expected in
black-white.
The file abc-cairo-aa-none.png is in black-white as expected.
Expected results:
I would have expected the files abc*--aa-none.png looking near identical.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 4 months
[Bug 2015628] New: No entry /sys/class/leds for Fn 5 key that
toggles keyboard backlight
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
Bug ID: 2015628
Summary: No entry /sys/class/leds for Fn 5 key that toggles
keyboard backlight
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: eb30750(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Keyboard backlight worked until upgrading to FC34. The
Fn 5 key toggled the keyboard backlight on and off. In researching the new
method to expose the Fn keys to the user I found that there is no input/input5.
The input/input3 is configured.
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::capslock ->
../../devices/platform/i8042/serio0/input/input3/input3::capslock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::numlock ->
../../devices/platform/i8042/serio0/input/input3/input3::numlock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::scrolllock ->
../../devices/platform/i8042/serio0/input/input3/input3::scrolllock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 phy0-led ->
../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/leds/phy0-led
Version-Release number of selected component (if applicable):
5.14.11-200.fc34.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
A script or kernel option that builds the /sys/class/leds/input/input5
hierarchy.
Additional info:
If the input5 exists then simply changing the brightness value should turn on
the keyboard backlight.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
1 year, 5 months
[Fedora-i18n-bugs] [Bug 1903877] New: kde-l10n-pa missing translated file
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1903877
Bug ID: 1903877
Summary: kde-l10n-pa missing translated file
Product: Fedora
Version: 33
Status: NEW
Component: kde-l10n
Keywords: i18n
Assignee: than(a)redhat.com
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz,
rdieter(a)gmail.com, smparrish(a)gmail.com,
than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1735891
--> https://bugzilla.redhat.com/attachment.cgi?id=1735891&action=edit
KDE system Tray (software, Keyboard Indicator)
Description of problem:
Version-Release number of selected component (if applicable):
kde-l10n-pa-17.08.3-9.fc33.noarch
apper-1.0.0-6.fc32.x86_64
How reproducible:
every time
Steps to Reproduce:
1. translation is not available for various KDE packages
2.rpm -q kde-l10n-pa -l|grep apper||grep
rpm -q kde-l10n-pa -l|grep kdeplasma
3.
Actual results:
applications are untranslated. Various untranslated section on KDE desktop in
Punjabi
No output for file search
Expected results: 4 following files
apper._desktop_.po
apper.po
org.kde.apper.appdata.po
plasma_applet_org.packagekit.updater.po
Additional info:
KDE svn source has apper fully transalted files for Punjabi since 2011:
https://websvn.kde.org/trunk/l10n-kf5/pa/messages/apper/
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 5 months
[Fedora-i18n-bugs] [Bug 1809989] New: By default install Noto fonts for Unicode scripts not already covered by default
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1809989
Bug ID: 1809989
Summary: By default install Noto fonts for Unicode scripts not
already covered by default
Product: Fedora
Version: 31
Status: NEW
Component: google-noto-fonts
Assignee: petersen(a)redhat.com
Reporter: hsivonen(a)hsivonen.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
There is currently movement towards protecting browser users from font
fingerprinting. This means refusing, by default, to load user-installed fonts,
which makes the set of fonts that each OS installs by default even more
important than before.
Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1582687
W3C CSS WG issue:
https://github.com/w3c/csswg-drafts/issues/4497
Currently, Windows 10, macOS, Android, and Chrome OS provide broader
installed-by-default Unicode coverage than Fedora.
Examples of living scripts that have enough active users to make it to the list
at
https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scr...
but are not supported by default in Fedora 31 include Javanese, Sundanese,
Batak, Balinese, Mongolian, and New Tai Lue.
Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't
support out of the box but Windows 10, macOS, Chrome OS, and Android do.
To remedy this with minimal disk space impact, I suggest the same approach that
Apple took. Apple bundles with macOS those Noto fonts that cover scripts that
were not already covered by the previous installed-by-default set of fonts on
macOS. In the macOS case, the on-disk footprint of the Noto fonts that were
required to take macOS to Android/Chrome OS-competitive Unicode coverage was
only a couple of megabytes. (The fonts are hidden in /Library/Application
Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto
fonts required to reach the Chrome OS / Android level of script coverage is a
bit larger than in the macOS case but should still be manageable.
Please install, by default, those Noto fonts that provide support for scripts
that are not properly supported by the fonts that Fedora already installs by
default.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 5 months
[Fedora-i18n-bugs] [Bug 1832351] New: Macintosh keyboard variants not available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1832351
Bug ID: 1832351
Summary: Macintosh keyboard variants not available
Product: Fedora
Version: 32
Hardware: x86_64
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: mthoemme(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, negativo17(a)gmail.com,
peter.hutterer(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I do not have any variants for Macintosh available when trying to change the
keyboard layout via the GUI (Region & Language Settings).
Trying to manually set the keymap in the locale works for the VC keymap, but
not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac"
respectively, leave the X11 Layout at "de"
localectl set-keymap de-mac
Digging even deeper, the following commands all yield the same errors:
localectl set-x11-keymap de-mac
localectl set-x11-keymap de_mac
localectl set-x11-keymap de macintosh de_mac
All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing
as invalid."
Version-Release number of selected component (if applicable):
dnf info xkeyboard-config
Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST.
Installed Packages
Name : xkeyboard-config
Version : 2.29
Release : 1.fc32
Architecture : noarch
Size : 5.5 M
Source : xkeyboard-config-2.29-1.fc32.src.rpm
Repository : @System
From repo : anaconda
Summary : X Keyboard Extension configuration data
URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig
License : MIT
Description : This package contains configuration data used by the X Keyboard
Extension (XKB),
: which allows selection of keyboard layouts when using a
graphical interface.
How reproducible:
Happens consistently. I'm on a fresh Fedora 32 install.
Steps to Reproduce:
1. localectl set-x11-keymap de macintosh de_mac
Actual results:
"Failed to set keymap: Specified keymap cannot be compiled, refusing as
invalid."
Expected results:
Successfully sets the keyboard layout to a Macintosh variant.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 6 months
[Bug 1961723] New: dnf reports errors when processing
translate-toolkit.noarch
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1961723
Bug ID: 1961723
Summary: dnf reports errors when processing
translate-toolkit.noarch
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: translate-toolkit
Severity: high
Assignee: suanand(a)redhat.com
Reporter: grgoffe(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Attempting upgrade of this system; dnf reports an error
condition which stops upgrade (see below)
Version-Release number of selected component (if applicable):
see below
How reproducible:
always
Steps to Reproduce:
1.see below
2.
3.
Actual results: see below
Expected results: successful and clean system upgrade
Additional info:
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
--setopt=zchunk=0 --exclude='*'kernel'*' --exclude=erlang'*'
--exclude='environment-modules*' --exclude=Lmod upgrade /root/upgrade.log
Script started, output log file is '/root/upgrade.log'.
Fedora rawhide openh264 (From Cisco) - x86_64
2.5 kB/s | 989 B 00:00
Fedora - Modular Rawhide - Developmental packages for the next Fedora release
679 kB/s | 1.6 MB 00:02
Fedora - Rawhide - Developmental packages for the next Fedora release
1.3 MB/s | 64 MB 00:47
Error:
Problem: cannot install the best update candidate for package
translate-toolkit-3.3.5-1.fc35.noarch
- problem with installed package translate-toolkit-3.3.5-1.fc35.noarch
- nothing provides python3.9dist(lxml) >= 4.6.3 needed by
translate-toolkit-3.3.6-1.fc35.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 6 months