this post was submitted on 08 Jan 2024
18 points (90.9% liked)

Linux Gaming

15842 readers
9 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
 

So, I was having a hard time trying to update Nobara 38 to Nobara 39. Did the KDE swap, followed the website instructions to upgrade but in the last part, after:

$sudo dnf system-upgrade download --releasever=39 -y

I'd get:

Error: Transaction test error:

file /usr/lib64/libopenh264.so.2.3.1 conflicts between attempted installs of noopenh264-0.1.0~openh264_2.3.1-2.fc39.x86_64 and openh264-2.3.1-2.fc39.x86_64

Tried several solutions to this without success but noticed it's just that two packages in the upgrade are trying to write the same file. My solution was to just disable the openh264 Cisco repo for the upgrade with:

$sudo dnf config-manager --set-disabled fedora-cisco-openh264

You can do this also in the Diskover preferences.

After disabling the Cisco repo you can proceed with:

$sudo dnf system-upgrade download --releasever=39 -y

$sudo system-upgrade reboot

Then, after a successful upgrade, go to Diskover > Preferences and enable (check) the fedora_cisco_openh264 repo. Finally, do perform a system update with Nobara update tool. Install whatever it tells you it's missing and then you are done.

Figured I'd share this here since the threads in Reddit don't show any clear fix to the problem. Hope someone can use it.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 3 points 10 months ago (1 children)

I updated and had lots of boot issues and gpu performance issues. After 10 boots I was able to get in and use my computer. Instead of trying to fix the problem I updated every day and after 5 days it seems to all be fixed. No idea what happened.

[โ€“] [email protected] 1 points 10 months ago

My issue was that the final step wouldn't start the upgrade process. To my knowledge there is no way to instruct dnf system-upgrade to ignore or overwrite these conflicting files.