I just upgraded from Fedora 42 to 43, and now whenever I open the Discover app I get the following error:
Could not depsolve transaction; 1 problem detected:
Problem: The operation would result in removing the following protected packages: systemd, systemd-udev
Does anyone know how to resolve this?
Thanks,
I am wondering what happens if you try doing manual updates from the command line. Will you get the same message? I did Google “Could not depsolve transaction” and there were lots of hits for it… Maybe give that a try.
I tried doing dnf update and dnf upgrade, but there are no updates available. No error message though.
I believe using “update” or “upgrade” are the same thing. You can always try sudo dnf --refresh update as well…
In my own case, Gnome Software showed upgrades while DNF did not.
But with “dnf check-upgrades” I got the same upgrades as Gnome Software and after that “dnf upgrade” found them.
So now I always do both commands.
It’s luck about which mirror you check for updates.
Some mirrors will have the new RPMs others will not.
dnf check-upgrades does not change any state that would affect dnf upgrade.
Yes that is what I thought before but apparently I got stuck for a while until I did the two stages procedure. Since it doesn’t cost me much, why not.
Because it does not actually help do anything for you.
Over time you may forget why you do these commands that way and tell other people they should.
Then I write it again. I could not upgrade via usual “dnf upgrade” and it was critical because I was waiting for the fix on Gnome Online Accounts and Deja Dup. There wasn’t anything wrong apparently, DNF did not find any upgrade. I don’t know, maybe there is some way to force DNF to look in a different way but the basic “check-upgrade” did the trick. Since it does not make any harm (I mean, otherwise why the commant would exist in first place), I think it is worth trying.
Also I believe there is a per-user cache. So sudo dnf upgrade (hits the root cache) may give different results from dnf check-upgrade (using the user’s cache).
I suspect that always specifying --refresh would eliminate the difference, but haven’t looked in detail.
Yeah, I usually use the --refresh when doing an update from the command line.
So, apps started becoming non-responsive, and removing and reinstalling them wouldn’t fix it. I was also getting more errors in the Discover app, so I tried downgrading to Fedora 42. I found that running updates after a clean install resulted in the same errors in Discover.
I also tried doing a clean install of Fedora 43, but after installation it doesn’t seem to have a boot loader or something, because it just doesn’t boot.
I’m back on Windows now until I can make Linux work.
What are the symptoms when you try to boot? Does Grub even show up?
Also it really is best to do some troubleshooting using journalctl because that will tell you what is going on.
Nope, nothing. The drive doesn’t appear in the BIOS as a bootable device.
I don’t know if it’s related, but I have to use CSM to get the install media to boot. With Fedora 42 I could disable it again after installation, but nothing seems to make a clean install of 43 bootable on my system.
I was able to resolve the issue. I was finally able to boot into the install disk by disabling the TPM chip in my BIOS. I did a clean install of Fedora 43 and all of the issues are resolved.
Thanks for the feedback!