Request for help, I broke some graphics
Request for help, I broke some graphics
I broke some packages and I need help figuring out how to fix it.
I run Nobara and usually update via "Nobara Package Manager", however it ran into a problem:
Could not depsolve transaction; 1 problem detected:
Problem: The operation would result in removing the following protected packages: nobara-amdgpu-config
I found the solution on Nobara projects site: sudo dnf update --exclude=nobara-login --refresh && sudo dnf update --refresh
That did result in several packages begin updated, I just skimmed through the list but I remember some mesa stuff. After a reboot some apps render like in the picture - missing characters or missing text all together and flickering artefacts. I run things pretty out-of-the-box so not sure what I've done that has lead up to this, just care about gaming.
How can I troubleshoot this? Thanks in advance
You're viewing a single thread.
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:
- Ran upgrade from Nobara 37->38 following their guide: https://nobaraproject.org/docs/upgrade-troubleshooting/how-do-i-upgrade-to-a-new-nobara-version/
- Ran into conflicts:
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 - Solved it with exclusion:
sudo dnf -v system-upgrade download --releasever=38 --allowerasing --exclude=openh264.x86_64 - Fonts and glitches are gone, got some broken deps instead. So if anyone got a suggestion for that instead let me know. Otherwise I'll do as it suggest
--best --allowerasing'and see what else breaks:
Problem: The operation would result in removing the following protected packages: plasma-desktop ================================================================================ Package Arch Version Repository Size ================================================================================ Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): kde-settings noarch 38.2-5.fc38 nobara-baseos-38 33 k libkworkspace5 x86_64 5.27.8-1.fc38 nobara-baseos-38 115 k libkworkspace5 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 115 k plasma-workspace-common x86_64 5.27.8-1.fc38 nobara-baseos-38 41 k plasma-workspace-common x86_64 5.27.9.1-3.fc38 nobara-baseos-38 40 k plasma-workspace-libs x86_64 5.27.8-1.fc38 nobara-baseos-38 2.2 M plasma-workspace-libs x86_64 5.27.9.1-3.fc38 nobara-baseos-38 2.2 M plasma-workspace-wayland x86_64 5.27.8-1.fc38 nobara-baseos-38 70 k plasma-workspace-wayland x86_64 5.27.9.1-3.fc38 nobara-baseos-38 70 k Skipping packages with broken dependencies: kde-settings-plasma noarch 38.2-5.fc38 nobara-baseos-38 13 k plasma-lookandfeel-fedora noarch 5.27.8-1.fc38 nobara-baseos-38 403 k plasma-workspace i686 5.27.8-1.fc38 nobara-baseos-multilib-38 15 M plasma-workspace x86_64 5.27.8-1.fc38 nobara-baseos-38 15 M plasma-workspace i686 5.27.9.1-2.fc38 nobara-baseos-multilib-38 15 M plasma-workspace i686 5.27.9.1-3.fc38 nobara-baseos-multilib-38 15 M plasma-workspace x86_64 5.27.9.1-3.fc38 nobara-baseos-38 15 M plasma-workspace-x11 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 68 k sddm-breeze noarch 5.27.9.1-3.fc38 nobara-baseos-38 440 k Transaction Summary ================================================================================ Skip 18 PackagesNow it's trying to either partial upgrade OR delete your desktop. Your system is fucked.
It un-fucked itself thankfully, I haven't done anything to resolve that issue. But when I ran the update today it went well with several new packages. Which means Nobara or Fedora pushed some changes to packages in the repos.
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
dnfand 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.