On Sun, 03 Jul 2016 19:22:54 -0000
"Travis Lankow" <ad7d(a)fedoraproject.org> wrote:
Hi all,
I'm running into that error when attempting to dnf upgrade.
I'm running a normal Fedora kernel, but I did install 24 from one of
the release candidates instead of the release media. I've checked
dnf.conf and installonly_limit=3.
sudo dnf list installed kernel:
kernel.x86_64
4.5.7-300.fc24 @updates
sudo fpaste --sysinfo:
https://paste.fedoraproject.org/387453/46748723
Kinda out of ideas except manually installing a new kernel, which I
shouldn't have to do, or re-installing from release media which sucks
since I just got my laptop setup how I like.
I have tried sudo dnf distro-sync --best --allowerasing and setting
installonly_limit=99 to the same result. The only kernel-related
change I've made since install has been enabling TRIM: "grubby
--update-kernel=ALL --args=rd.luks.options=discard"
Just some ideas that might trigger a solution for you.
What happens if you undo this change of enabling TRIM?
Have you rebuilt the rpm database?
rpm --rebuilddb
At the bottom of the man page for yum2dnf, there are some commands for
dnf to check the consistency of the installation. You should run those
to see if there are any problems with your install. These are the
replacements for the old package-cleanup commands under yum.
Try skipping kernel update with
dnf -x kernel upgrade 2> /tmp/dnf_error
If this works, then there is something incorrect in your kernel update
configuration.
If it doesn't, you might see the problem in the errors
in /tmp/dnf_error, though dnf isn't as helpful in that regard as yum
was. They are working on making it more helpful, but not there yet.
If the rest of the updates complete,
cd /boot/grub2
and run
grub2-mkconfig -o grub.cfg
to create a new grub config file. Reboot.
Then try running dnf upgrade again, and see if this has changed the
behavior.