Comments
adelton
provided feedback
on kernel-5.8.17-300.fc33
4 years ago
The build fixed the issue for me on Fedora 32.
The build fixed the GSSAPI issue. Thank you.
The CPU Frequency Monitor is working again with this build. Thank you, jan
Current packages in epel-testing make pylint work for me. Thank you.
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1788084#c15, this update together with https://kojipkgs.fedoraproject.org//packages/python-astroid/2.3.3/4.gitace7b29.fc31/noarch/python3-astroid-2.3.3-4.gitace7b29.fc31.noarch.rpm makes things work, so reverting the karma to +1.
Fresh installation of python3-pylint-2.3.1-2.fc31.noarch with https://kojipkgs.fedoraproject.org//packages/python-astroid/2.3.3/3.gitace7b29.fc31/noarch/python3-astroid-2.3.3-3.gitace7b29.fc31.noarch.rpm causes things to fail with pkg_resources.DistributionNotFound: The 'six~=1.12' distribution was not found and is required by astroid.
So that's probably another dependency which is needed.
Upgrading python-lazy-object-proxy does not seem to fix the pylint problem.
With terminus-fonts-4.48-2.fc31.noarch, Terminus Medium 8 fonts works fine with xfce4-terminal-0.8.8-2.fc31.x86_64 and pango-1.44.7-1.fc31.x86_64. Thank you.
https://kojipkgs.fedoraproject.org//packages/cri-o/1.16.1/1.module_f31+7193+28fb818f/x86_64/cri-o-1.16.1-1.module_f31+7193+28fb818f.x86_64.rpm seems to work fine but the update is not in updates-testing yet.
Upgrading from cri-o-1.16.0-0.1.rc1.git6a4b481.module_f31+6837+7e34758d.x86_64 to ccri-o-1.16.0-0.4.rc2.module_f31+7054+4022d60f.x86_64 does not fix the problem:
Nov 25 03:39:32 machine.example.test systemd[1]: Starting Container Runtime Interface for OCI (CRI-O)... Nov 25 03:39:32 machine.example.test crio[10053]: time="2019-11-25 03:39:32.135457557-05:00" level=fatal msg="Invalid character(s) found in build meta data \"7054+4022d60f-rc2\"" Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Failed with result 'exit-code'. Nov 25 03:39:32 machine.example.test systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).
The build addresses the segfault reported in https://bugzilla.redhat.com/show_bug.cgi?id=1665490
The https://bugzilla.redhat.com/show_bug.cgi?id=1755643 is fixed by this build.
The https://bugzilla.redhat.com/show_bug.cgi?id=1755643 is fixed by this build: https://travis-ci.org/freeipa/freeipa-container/jobs/603619439
I experience https://bugzilla.redhat.com/show_bug.cgi?id=1755643 with the 2.2.2-1 SSSD version.
This updated causes https://bugzilla.redhat.com/show_bug.cgi?id=1743902.
I don't see https://bugzilla.redhat.com/show_bug.cgi?id=1665490 fixed, I'm still getting the Segfault.