Re: During the first update after installation: Failed to connect to bus: Invalid argument

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Nov 9, 2021 at 5:53 PM Adam Williamson
<adamwill@xxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, 2021-11-09 at 14:06 +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?
>
> Yeah, some standard %post script is triggering it most likely. I see it
> frequently in Rawhide updates. It's most likely one of the systemd
> scriptlets that calls /usr/lib/systemd/systemd-update-helper . I dunno
> if anyone's filed a bug on it yet.

Yes, there's been multiple bug reports filed for this:
https://bugzilla.redhat.com/show_bug.cgi?id=2020415

And as you suspected, it's a problem in systemd RPM scriptlet helper scripts.

Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux