It seems the problem is back again! I am not able to upgrade to 38 cause of this problem.
I tried to do an upgrade from 37 to 38 and got:
Error: Transaction test error:
file /usr/bin/pw-jack conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjack.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjacknet.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjackserver.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/share/pipewire/jack.conf conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
Any hint how to proceed? Simply wait on a fix “some day” will appear?
Please always use the preformatted text tags available with the </> button on the toolbar when posting data that is copied and pasted from your screen.
Note the extreme difference in readability between the way it shows in your post and the below. The only difference is the tags.
Error: Transaction test error:
file /usr/bin/pw-jack conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjack.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjacknet.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjackserver.so.0 conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/share/pipewire/jack.conf conflicts between attempted installs of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64 and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
Did you perform the always recommended dnf upgrade --refresh step before attempting the system-upgrade process? Or are you using the gnome-software process to upgrade?
In either case I recommend you do the dnf upgrade command first then retry the upgrade.
You also did not show enough information for us to see the actual cause AND your upgrade is from 37 to 38 while this original thread is about upgrading from 38 to 39.
I recommend you start a new thread for the 37 to 38 upgrade and avoid confusion for readers that attempt to assist.
dnf update --refresh was executed before upgrade command. Upgrade was performed from command line.
The thread here is about update on fedora 38 and my upgrade is from 37 to 38. The bug comes from the packages in 38. This is the reason why I post my topic exactly within this thread, because the reason is related to dependencies of packages within F38.
I don’t know about @computersavvy, but my thought was that we do not know that this is a problem with packages in f38 because you are not yet using f38.
Knowing all of the steps you took and were able to complete successfully during your attempt at doing the system-upgrade from f37 to f38 might help with that. In other words, this is a case of first things first.
I moved this to a new topic so it gets the attention it deserves. The original topic already had a posted solution and yours seems different since it is related to an upgrade from F37 to F38 while the original was a problem with updates on F38.
Please post the output of cat /etc/fedora-release and inxi -Fzxx so we may see the hardware and drivers as well as the answer to the question asked by @jrredho just above.
Detailed information is needed so if you were to post the actual commands used and the results that you copy and paste from the screen into the discussion here it would help us to help you. Please use the preformatted text tags with the </> button from the toolbar or use triple back quotes [```] on the lines preceding and following the pasted text so we can see it formatted as you do on screen.
I suggest to first remove pipewire-jack-audio-connection-kit and if it causes too many dependencies to be removed, abort the removal. One of the dependencies could be the cause of the problem.
If I format it like this
file /usr/bin/pw-jack conflicts between attempted installs
of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64
and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjack.so.0 conflicts between attempted installs
of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64
and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjacknet.so.0 conflicts between attempted installs
of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64
and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/lib64/pipewire-0.3/jack/libjackserver.so.0 conflicts between attempted installs
of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64
and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
file /usr/share/pipewire/jack.conf conflicts between attempted installs
of pipewire-jack-audio-connection-kit-libs-0.3.84-2.fc38.x86_64
and pipewire-jack-audio-connection-kit-0.3.67-1.fc38.x86_64
Hi pipewire-jack-audio-connection-kit is at the last version, but not 0.3.84. There is no upgrade for fedora 37.
If I remove pipewire-jack-audio-connection-kitThe system remove many software (like Audacity for example), and other.
Removing only jack* remove only that packet.
I indicate the solution that work for me.
I glad to learn you discovered what was happening, and that it was relatively easy to sort out, thanks to @vekruse, of course.
I can’t help from wondering, though, if doing some of the things listed in the “Optional post-upgrade tasks” in the upgrade via dnf section of the docs after your last system-upgrade wouldn’t have saved you some trouble.
I know that I’ll be more diligent about doing these in the future…