Display errors when running dnf5 for upgrades

Ask Fedora
,
1

There are often errors seen with systemd when doing an upgrade using dnf5.

Dnf5 also has problems with displaying messages in that it does not erase an earlier message line before displaying the new one.
In my last update, every message at the end that begins with Running has failed to remove the earlier message related to whatever?. Note the trailing characters on each such line

>>> Running post-transaction scriptlet: kernel-core-0:6.11.10-300.fc41.x86_641.x86_64
                                                                             ^^^^^^^^
>>> Finished post-transaction scriptlet: kernel-core-0:6.11.10-300.fc41.x86_64
>>> Scriptlet output:
>>> Generating grub configuration file ...
>>> Adding boot menu entry for UEFI Firmware Settings ...
>>> done
>>> 
>>> Running trigger-install scriptlet: systemd-0:256.8-1.fc41.x86_64c41.x86_64h4
                                                                    ^^^^^^^^^^^^
>>> Finished trigger-install scriptlet: systemd-0:256.8-1.fc41.x86_64
>>> Scriptlet output:
>>> Reload daemon failed: Transport endpoint is not connected
>>> Failed to start jobs: Transport endpoint is not connected
>>> 
>>> Running trigger-post-uninstall scriptlet: systemd-0:256.8-1.fc41.x86_6486_64
                                                                           ^^^^^
>>> Finished trigger-post-uninstall scriptlet: systemd-0:256.8-1.fc41.x86_64
>>> Scriptlet output:
>>> Reload daemon failed: Transport endpoint is not connected
>>> 
>>> Running trigger-post-uninstall scriptlet: systemd-0:256.8-1.fc41.x86_64fc41.noarch
                                                                           ^^^^^^^^^^
>>> Finished trigger-post-uninstall scriptlet: systemd-0:256.8-1.fc41.x86_64
>>> Scriptlet output:
>>> Failed to start jobs: Transport endpoint is not connected
>>>

I marked the errors above
I believe there is already a bug report on this but I did not search for it.

2

i get similar on toolbox little difrent but similar

3

Yours appear to be from dmesg. Mine were from the screen directly as I did the upgrade.

1 Like
4

I usually use an automated process to do the routine updates of my systems. This run dnf without a tty so it does not do the update tricks.
That means for the logs I have there is not overwriting.

But i was doing an interactive reinstall and noticed a lot of “triggered” messages overwriting each other.

I think that is you pipe dnf through cat that is turned off.

5

The "Complete!" message of dnf upgrade overlaps with the old log · Issue #1899 · rpm-software-management/dnf5 · GitHub

2 Likes