`dnf` progress bars rendering incorrectly

[priscira]

Describe the bug:
I tried running sudo dnf upgrade on Fedora, which normally displays a progress bar showing the installation progress. However, I noticed the following:

[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                73% [=============     ] |   3.9 MiB/s |   7.2 MiB |  00m00s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                80% [==============    ] |   3.9 MiB/s |   7.9 MiB |  00m00s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                86% [================  ] |   3.9 MiB/s |   8.5 MiB |  00m00s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                93% [================= ] |   3.9 MiB/s |   9.2 MiB |  00m00s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                98% [==================] |   3.9 MiB/s |   9.7 MiB |  00m00s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              13% [==                ] |   0.0   B/s |  64.0 KiB |  00m06s
[165/179] python3-libs-0:3.14.3-2.fc43.x86_64                                                                    100% |   3.3 MiB/s |   9.9 MiB |  00m03s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                              16% [===               ] |  24.2 KiB/s |  80.0 KiB |  00m16s
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                            0% [                  ] |   0.0   B/s |  64.0 KiB |  02m22s
[166/179] python3-boto3-0:1.42.82-1.fc43.noarch                                                                  100% | 163.3 KiB/s | 481.7 KiB |  00m03s
---------------------------------------------------------------------------------------------------------------------------------------------------------
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                            0% [                  ] |  23.7 KiB/s |  80.0 KiB |  06m06s
[165/179] Total                                                                              96% [================= ] |   3.9 MiB/s | 414.5 MiB |  00m03s
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   1.0   B/s |   0.0   B |  19d03h
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                            6% [=                 ] |  23.7 KiB/s | 608.0 KiB |  05m44s
---------------------------------------------------------------------------------------------------------------------------------------------------------
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   1.0   B/s |   0.0   B |  19d03h
[166/179] Total                                                                              96% [================= ] |   3.9 MiB/s | 414.9 MiB |  00m03s
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                           16% [===               ] |  23.7 KiB/s |   1.4 MiB |  05m09s
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   1.0   B/s |   0.0   B |  19d03h
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                           25% [=====             ] |  23.7 KiB/s |   2.2 MiB |  04m34s
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   1.0   B/s |   0.0   B |  19d03h
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                           36% [=======           ] |   2.9 MiB/s |   3.1 MiB |  00m01s
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   0.0   B/s |   0.0   B |  19d03h
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                           46% [========          ] |   2.9 MiB/s |   4.0 MiB |  00m01s
[168/179] python3-cryptography-0:46.0.6-1.fc43.x86_64                                         0% [<=>               ] |   0.0   B/s |   0.0   B |  19d03h
[167/179] python3-botocore-0:1.42.82-1.fc43.noarch                                           56% [==========        ] |   2.9 MiB/s |   4.9 MiB |  00m01s

Please note that the above output is what I saw after the command finished.

As you can see, a package like python3-boto3-0:1.42.82-1.fc43.noarch appears many times (just as an example), and the same happens with other packages.

My guess is that there is an issue with how the progress bar output is being handled.

Screenshots:

Platform (please complete the following information):

• Linux Fedora 6.19.8-200.fc43.x86_64 Fri Mar 13 22:06:06 UTC 2026 x86_64 GNU/Linux
• Alacritty
• murex v7.1.4143 (unknown)

Additional context

Why it's all red? It should not be stderr. However, it doesnt matter.

[lmorg]

I wonder if dnf is writing to stderr. You can easily test this by running the following:

config set proc force-tty true

...then dnf like usual.

This will force stderr to use the same TTY as stdout (Murex reads them separately to provide the red highlights -- it's a hack but it mostly works well).

If this does fix the issue then I can add an integration so that dnf always runs this way via a wrapper script

[priscira]

This has indeed taken effect.
Thanks!

[priscira]

I couldn't find proc force-tty in the documentation.
Could you please point me to where this setting is documented?

[lmorg]

force-tty specifically isn't, but config is https://murex.rocks/commands/config.html

The original intention for config options were that they'd be self documenting. for example the description below:

~ » config -> [[ .proc.force-tty ]]
{
    "Data-Type": "bool",
    "Default": false,
    "Description": "This is used to override the red highlighting on STDERR on a per-process level",
    "Dynamic": false,
    "Global": false,
    "Value": false
}

But this clearly isn't enough so Murex really could benefit from having more in-depth documentation here. I can add that to the requirements for next release (along with adding dnf integration that defaults to enabling force-tty