On Tue, Nov 09, 2021 at 02:06:54PM +0100, Peter Boy wrote:
While updating right after installation of Fedora Server 35 today I
get:
> [...]# sudo dnf update
> ...
> Cleanup : glibc-langpack-de-2.34-7.fc35.x86_64 303/306
> Cleanup : glibc-gconv-extra-2.34-7.fc35.x86_64 304/306
> Running Scriptlet: glibc-gconv-extra-2.34-7.fc35.x86_64 304/306
> Cleanup : glibc-common-2.34-7.fc35.x86_64 305/306
> Cleanup : tzdata-2021b-1.fc35.noarch 306/306
> Running Scriptlet: grub2-common-1:2.06-8.fc35.noarch 306/306
> Running Scriptlet: selinux-policy-targeted-35.5-1.fc35.noarch 306/306
> Running Scriptlet: clevis-18-4.fc35.x86_64 306/306
> Running Scriptlet: libwbclient-2:4.15.1-0.fc35.x86_64 306/306
> Running Scriptlet: kernel-core-5.14.16-301.fc35.x86_64 306/306
> Running Scriptlet: sssd-common-2.6.0-2.fc35.x86_64 306/306
> Running Scriptlet: tzdata-2021b-1.fc35.noarch 306/306
> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
>
> Failed to connect to bus: Invalid argument
> Failed to connect to bus: Invalid argument
>
> Verifying : clevis-pin-tpm2-0.3.0-2.fc35.x86_64 1/306
> Verifying : freetype-2.11.0-1.fc35.x86_64 2/306
I first suspected there was an error during installation and repeated it, watching for
error / warning messages (none). The error messages during the update occurred again.
I can’t remember these messages some days ago after another installation using an
activated root account.
I didn’t found any issues yet.
Anyone else got these messages?
Yes. I ignored them because they had no obvious effect on anything.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top