this post was submitted on 26 Nov 2023
110 points (95.8% liked)
Linux
48083 readers
1183 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Oof. You uninstalled Mesa's AMD config because a troll on the internet tried to partial upgrade your system. You're kinda fucked.
Yeah I kind of realised that the instructions assumed I had already upgraded, will try to keep track of new updates better in the future. So for sake of completion here's how I solved it in the end:
file /usr/lib64/libopenh264.so.2.3.1 conflicts between attempted installs of openh264-2.3.1-2.fc38.x86_64 and noopenh264-0.1.0~openh264_2.3.1-2.fc38.x86_64
sudo dnf -v system-upgrade download --releasever=38 --allowerasing --exclude=openh264.x86_64
--best --allowerasing'
and see what else breaks:I saw that error when I first installed nobara. Googled it, and the solution was just to not use dnf to update, but nobara-sync instead.
Yeah I forgot to mention that I'll not be using dnf manually but rely on nobara-sync. But I must stress that I already did that before this issue, BUT I followed advice on nobaras own website where the solution was to use
dnf
and I still ended up with this problem. The real issue was still my own though, I should have upgraded to Nobara 38 before trying the workarounds, since 37 isn't supported any more.