Bug 2020980

Summary: systemd-update-helper: "Failed to connect to bus: Invalid argument"
Product: [Fedora] Fedora Reporter: Sam Varshavchik <mrsam>
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: fedoraproject, filbranden, flepied, lnykryn, msekleta, ryncsn, ssahani, s, systemd-maint, yuwatana, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-08 09:30:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sam Varshavchik 2021-11-07 22:47:29 UTC 
Description of problem:

dnf update emits a bunch of

Failed to connect to bus: Invalid argument

diagnostics when updating packages

Version-Release number of selected component (if applicable):

systemd-249.6-2.fc35.x86_64

How reproducible:

always

Steps to Reproduce:
1. ssh into a server, into a user account that has sudo permissions to run dnf
2. do a "dnf update" of some package.
3.

Actual results:

Several

Failed to connect to bus: Invalid argument

messages, mixed in with actual output.

Expected results:

No diagnostics

Additional info:

strace seems to suggest that this warning comes out of

/usr/lib/systemd/systemd-update-helper user-reload

which appears to be injected into the upgrade with /usr/lib/rpm/macros.d/macros.systemd
Comment 1 Sam Varshavchik 2021-11-07 22:51:01 UTC 
This can be reproduced by executing systemd-update-helper directly, without involving dnf.

After ssh-ing into a user account:

$ /usr/lib/systemd/systemd-update-helper user-reload
Failed to connect to bus: Invalid argument
Comment 2 Zbigniew Jędrzejewski-Szmek 2021-11-08 09:30:09 UTC 

*** This bug has been marked as a duplicate of bug 2020415 ***