When doing an upgrade with dnf (going from 34 to 35), I’m getting a slew of transaction test errors like these:

file /usr/bin/qemu-alpha-static from install of qemu-user-static-2:6.1.0-16.fc35.x86_64 conflicts with file from package qemu-user-static-alpha-2:6.2.0-17.fc36.x86_64
file /usr/share/systemtap/tapset/qemu-alpha-static.stp from install of qemu-user-static-2:6.1.0-16.fc35.x86_64 conflicts with file from package qemu-user-static-alpha-2:6.2.0-17.fc36.x86_64
file /usr/lib64/python3.10/site-packages/pycrypto-2.6.1-py3.10.egg-info from install of python3-crypto-2.6.1-36.fc35.x86_64 conflicts with file from package python3-crypto-2.6.1-39.fc36.x86_64
file /usr/lib/udev/rename_device from install of initscripts-10.15-1.fc35.x86_64 conflicts with file from package initscripts-rename-device-10.16-3.fc36.x86_64

Anyone know what’s going on, and how to fix it?

[Update Monday morning]

OK, the problem is that I’m trying to upgrade to 35 when in fact I’m running 36. And the weird thing is that ‘uname -r’ says it’s 34, while /etc/fedora-release says it’s 36. And when I boot it, it’s using a 34 kernel. So, I decided to upgrade to 37 instead, since in actuality, other than the kernel, all my packages are 36. That upgrade went well, but I don’t know what will happen if I actually do a reboot into the new version. I’m asking people on the Fedora forum. The mystery is why it’s running on a 34 kernel.

[Bumped]

When I did the latest Fedora install, it created a home directory for me called “randsimberg.” I always name my directory “simberg,” so I did a ‘mv randsimberg simberg’. Now I can’t launch a terminal, because the bash script is looking for the “randsimberg” directory.

Fun.

I’m trying to install on a new machine with Windows, and the LiveCD boots, but it doesn’t seem to see the keyboard or mouse. I can boot from Windows and another Linux drive, but when I boot from the LiveCD to do an installation, it just ignores me. Any ideas?

[Saturday-morning update]

OK, buy jiggering with the BIOS and UEFI settings, I managed to get it to boot. It says it installed Fedora on the drive that I shrunk the Windows partition. But when I reboot it without the USB key, I don’t get grub; it just boots into Windows. Now what?

[Update a while later]

OK, I don’t know why the BIOS wasn’t seeing it, or why I couldn’t add it, but Windows was seeing it. I forced Windows to load it on boot by editing the boot manager, so it seems to be working now.

[Update a while later]

OK, new problem. Grub is coming up now that I played around in Windows, but it’s making Fedora the default, which is a problem because I’m the only one who will be using it, and only a few times a year. I’ve read through all the instruction about changing it in Fedora, but they don’t show the Windows bootloader, and when I look at it in Windows, I don’t see anything except Windows, so I can’t change the order there, either.

[Update a few minutes later]

Success! I used this program to reconfigure grub, and although Linux is still at the top of the order, Windows now has an asterisk, and is the new default.