Bug 2022122 - Failed to connect to bus: Invalid Argument
Summary: Failed to connect to bus: Invalid Argument
Keywords:
Status: CLOSED DUPLICATE of bug 2020415
Alias: None
Product: Fedora
Classification: Fedora
Component: imlib2
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Smetana
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2021923 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-10 19:29 UTC by david.halpern
Modified: 2023-01-13 13:05 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-12 09:57:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description david.halpern 2021-11-10 19:29:59 UTC
When I update fedora using "sudo dnf update" I receive the error "Failed to connect to bus: Invalid argument" appear 4 times after the scriplet for imlib2 has been run. This error is reproducible in several workstations that I use.

Comment 1 Jakob Hirsch 2021-11-11 08:30:17 UTC
probably duplicate of #2021771

Comment 2 Tomas Smetana 2021-11-11 09:12:51 UTC
Thanks for reporting. Since this seems to affect more packages I doubt it's something wrong with imlib itself. There is only the %ldconfig_scriptlets macro being called -- no specific postinstall scripts. I'm also not sure if these messages are not printed asynchronously, i.e. they may not actually belong to imlib (or java-11-openjdk-headless as in the bug #2021771) but to some other package that was updated in the batch. The error itself looks like coming from systemctl (updating some unit file for other package being installed). Or was imlib2 the only package you updated in the transaction? (If yes, then it's not the systemd macros but that would be really weird.)

Comment 3 Tomas Smetana 2021-11-11 09:31:12 UTC
*** Bug 2021923 has been marked as a duplicate of this bug. ***

Comment 4 telometto 2021-11-11 10:22:35 UTC
(In reply to Tomas Smetana from comment #2)
> Thanks for reporting. Since this seems to affect more packages I doubt it's
> something wrong with imlib itself. There is only the %ldconfig_scriptlets
> macro being called -- no specific postinstall scripts. I'm also not sure if
> these messages are not printed asynchronously, i.e. they may not actually
> belong to imlib (or java-11-openjdk-headless as in the bug #2021771) but to
> some other package that was updated in the batch. The error itself looks
> like coming from systemctl (updating some unit file for other package being
> installed). Or was imlib2 the only package you updated in the transaction?
> (If yes, then it's not the systemd macros but that would be really weird.)

Thank you for the reply, Tomas.

No, several packages were updated so you are probably right about it being the systemd macros.
Anyway, I saw this reply a bit too late, so I already submitted another bug report regarding java-11-openjdk-headless).
I'll see if I can manage to merge it with bug #2021771.

Cheers.

Comment 5 Tomas Smetana 2021-11-12 09:57:45 UTC

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

Comment 6 Villy Kruse 2021-11-12 12:38:10 UTC
(In reply to Tomas Smetana from comment #2)
> Thanks for reporting. Since this seems to affect more packages I doubt it's
> something wrong with imlib itself. There is only the %ldconfig_scriptlets
> macro being called -- no specific postinstall scripts. I'm also not sure if
> these messages are not printed asynchronously, i.e. they may not actually
> belong to imlib (or java-11-openjdk-headless as in the bug #2021771) but to
> some other package that was updated in the batch. The error itself looks
> like coming from systemctl (updating some unit file for other package being
> installed). Or was imlib2 the only package you updated in the transaction?
> (If yes, then it's not the systemd macros but that would be really weird.)

More likely filetrigger from systemd

   rpm -q --filetriggers systemd

Comment 7 Ben Cotton 2023-01-13 13:05:40 UTC
Un-setting the prioritized bug request. This is an invalid request because
1. the bug is closed
2. the reported release is EOL

If this is still an issue, please nominate an open bug or create a new one.


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