Good afternoon everyone!
Currently when I update my Fedora 35, in a terminal window with the command ‘sudo dnf up’… I get this message in the middle of the update.
I found this reference: systemctl -M user@.host VERB should work · Issue #14580 · systemd/systemd · GitHub
But at my level of knowledge, I have no idea what to do.
Can someone help me?
Luca, interesting problem. Could you copy the command line and the lines leading up to the “Failed to connect to bus” message, and paste them into this thread (please use the "</> markup to keep the terminal window text looking good for people to read)
Thanks
1 Like
I’m seeing the same thing on a recently updated x86_64 laptop that went from F34 to F35. Today I did a sudo dnf update -y and in the ‘Running transaction’ part of the output I saw:
Running scriptlet: fprintd-1.92.0-2.fc35.x86_64 6/6
Failed to connect to bus: Invalid argumentFailed to connect to bus: Invalid argument
Verifying : fprintd-1.94.1-1.fc35.x86_64 1/6
Verifying : fprintd-1.92.0-2.fc35.x86_64
Nothing (so far) seems to be actually broken, but the message is a tad disturbing.
–
MC
2 Likes
Running scriptlet: tracker-miners-3.2.0-2.fc35.x86_64 124/216 Cleanup : tracker-miners-3.2.0-2.fc35.x86_64 124/216 Running scriptlet: tracker-miners-3.2.0-2.fc35.x86_64 124/216 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 Failed to connect to bus: Invalid argument
1 Like
I got the same error when running “sudo dnf upgrade”.
Transaction Summary ================================================================================ Upgrade 1 Package Total download size: 8.2 M Is this ok [y/N]: y Downloading Packages: syncthing-1.18.4-1.fc35.x86_64.rpm 4.7 MB/s | 8.2 MB 00:01 -------------------------------------------------------------------------------- Total 3.5 MB/s | 8.2 MB 00:02 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : syncthing-1.18.4-1.fc35.x86_64 1/2 Running scriptlet: syncthing-1.18.4-1.fc35.x86_64 1/2 Running scriptlet: syncthing-1.18.3-1.fc35.x86_64 2/2 Cleanup : syncthing-1.18.3-1.fc35.x86_64 2/2 Running scriptlet: syncthing-1.18.3-1.fc35.x86_64 2/2 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 Failed to connect to bus: Invalid argument Verifying : syncthing-1.18.4-1.fc35.x86_64 1/2 Verifying : syncthing-1.18.3-1.fc35.x86_64 2/2 Upgraded: syncthing-1.18.4-1.fc35.x86_64
1 Like
Many thanks to everyone who tried to help!
Despite this Fedora 35 works great, but I need my laptop for work, I use Mett at work… So I did a reinstallation… As the problem persisted, I got scared and switched to another distribution.
I thought it was a shame, as Fedora perfectly matches the hardware of the Lenovo 330 15ikb.
All gave an exact example of what happened in the update process.
In time…
May everyone be very welcome to this community!
1 Like
I note that those messages are related to the version being replaced, not the new version installed. As such, are they really anything more than a normally expected message?
1 Like
I hope it’s “something expected”… I would love to get back to Fedora.
But it seems that not even the developers themselves know what it is… If they did, they would have already answered…
the developers do not read these messages. If you really want to send a message to developers, you should file a bug https://bugzilla.redhat.com/index.cgi.
2 Likes
I believe we must agree to disagree…
The Fedora Project Leader himself participates here… If he didn’t answer, it’s because he doesn’t know, maybe it’s not his area, or because he didn’t want to…
I do note that there has been an increase in posts about this, and it seems to be affecting several different packages. Although to me it seems the message is coming from the cleanup scripts when the package is removed so it may not really be an issue. I think the cleanup process really should not be spitting out that type message if the ‘error’ or ‘warning’ that triggers it is normally expected.
One user just reported that message when doing a swap (both directions) of wireplumber and pipewire-media-session packages.
2 Likes
Same problem here when updating via dnf:
Cleanup : imlib2-1.6.1-4.fc35.x86_64 30/30
Running scriptlet: imlib2-1.6.1-4.fc35.x86_64 30/30
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
2 Likes
I got exactly the same, on the same package, when I updated a couple of minutes ago.
2 Likes
Similar issue for me, FC35, all video players are not working, I just see a freeze frame.
Running scriptlet: mpv-1:0.34.0-7.git459f7d4.fc35.x86_64 30/30
Running scriptlet: smplayer-21.10.0-7.fc35.x86_64 30/30
Running scriptlet: bluez-libs-5.62-1.fc35.x86_64 30/30
Failed to connect to bus: Invalid argument
Failed to connect to bus: Invalid argument
Verifying : mpv-1:0.34.0-7.git459f7d4.fc35.x86_64 1/30
Verifying : mpv-1:0.33.1-12.gitc27c17f.fc35.x86_64 2/30
Verifying : mpv-libs-1:0.34.0-7.git459f7d4.fc35.x86_64 3/30
Verifying : mpv-libs-1:0.33.1-12.gitc27c17f.fc35.x86_64 4/30
Verifying : smplayer-21.10.0-7.fc35.x86_64 5/30
Verifying : smplayer-21.8.0-7.fc35.x86_64 6/30
Verifying : smtube-21.10.0-7.fc35.x86_64 7/30
Verifying : smtube-21.8.0-7.fc35.x86_64 8/30
Verifying : bluez-5.62-2.fc35.x86_64 9/30
Verifying : bluez-5.62-1.fc35.x86_64 10/30
Verifying : bluez-cups-5.62-2.fc35.x86_64 11/30
Verifying : bluez-cups-5.62-1.fc35.x86_64 12/30
Verifying : bluez-libs-5.62-2.fc35.x86_64 13/30
Verifying : bluez-libs-5.62-1.fc35.x86_64 14/30
2 Likes
I believe that the “failed to connect …” message during your update is a red herring, unrelated to your overall video play issue. It may be useful for you to review some of the other conversations specifically about video players. This seemingly benign “failed to connect …” issue seems to be a general noisy bug with commonality across dnf update scriptlets.
I have the same issue as well. I’ve also been using the testing updates and have the latest kernel 5.14.17 .It hasn’t affected anything in the system that I’ve noticed. Nvidia is still working so I’m guessing it’s nothing serious.
2 Likes