Bug 2020980 - systemd-update-helper: "Failed to connect to bus: Invalid argument"
Summary: systemd-update-helper: "Failed to connect to bus: Invalid argument"
Keywords:
Status: CLOSED DUPLICATE of bug 2020415
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-07 22:47 UTC by Sam Varshavchik
Modified: 2021-11-08 09:30 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-08 09:30:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.