Thanks George I will look at the link. The problem now is how to get to terminal prompt to follow suggestions without the computer booting? Can do anything through BIOS options? (I am seeing this on a different device but the Linux fedora computer won’t boot at all - although I can get into BIOS).
You can try booting to a text console by using the grub editor to remove the rhgb quiet from the kernel command line and adding a <space>3 at the end of the command line.
If that isn’t helpful, run journalctl --directory=.... in a Live USB system to view the journals in the system disk. See man journalctl for details. Mount the system “root” directory with Gnome disks and then .... should be <mount_location>/var/log/journal/<long_random_string>/user-<uid>.journal.
I managed to boot the computer into permissive emergency mode. How do I find out what the file problem is and begin to correct it? I would like the computer to be able to boot normally without having to do a repeat editing of the grub to enter emergency mode each time.
I tried that fix but it did not work - touch was an unrecognised command.
Same for fixfiles command. Neither were recognised.
Then I tried booting within emergency mode again and tried the same commands within terminal - but permission was denied.
There was more success with fixfiles relabel in terminal - command was recognised but again the operation was not permitted on the removal of temp files.
Could not set context for /…: Operation not permitted
systemd-private-…:Permission denied
That would happen if you tried to run the commands in the grub shell – they are meant to be run in the text console, which is a bash shell in a fresh install of Fedora Workstation.
I have decades of experience introducing new users to Linux, so have seen this confusion before. While many users never need to use a terminal, it is an essential tool for solving problems and has the advantage that it is easy to post error messages as searchable text.
Linux Command is a time-tested reference that has helped many new users with command-line tools. I recommend spending a few hours learning your way around the reference and then referring back to it when you try something new.
glibc-2.40-23.fc41.x86_64 does not belong to a distupgrade repository
problem with installed package
Problem 2: installed package google-noto-sans-meetei-mayek-vf-fonts-20240701-2.fc41.noarch requires google-noto-fonts-common = 20240701-2.fc41, but none of the providers can be installed
google-noto-fonts-common-20240701-2.fc41.noarch does not belong to a distupgrade repository
problem with installed package
Problem 3: installed package mozjs128-128.5.1-2.fc41.x86_64 requires libicui18n.so.74()(64bit), but none of the providers can be installed
installed package mozjs128-128.5.1-2.fc41.x86_64 requires libicuuc.so.74()(64bit), but none of the providers can be installed
libicu-74.2-2.fc41.x86_64 does not belong to a distupgrade repository
problem with installed package
Problem 4: installed package add-determinism-0.3.6-3.fc41.x86_64 requires libc.so.6(GLIBC_2.39)(64bit), but none of the providers can be installed
installed package glibc-2.40-23.fc41.x86_64 requires glibc-langpack = 2.40-23.fc41, but none of the providers can be installed
installed package build-reproducibility-srpm-macros-0.3.6-3.fc41.noarch requires add-determinism = 0.3.6-3.fc41, but none of the providers can be installed
glibc-langpack-en-2.40-23.fc41.x86_64 does not belong to a distupgrade repository
glibc-all-langpacks-2.40-23.fc41.x86_64 does not belong to a distupgrade repository
problem with installed package
You can try to add to command line:
–skip-broken to skip uninstallable packages
I previously tried to remove skype which is now redundant, but, for the same reason as above; it resulted in - unable to complete - conflicting requests
conflicting requests
Problem 2: installed package kernel-modules-6.5.10-100.fc37.x86_64 requires kernel-modules-core-uname-r = 6.5.10-100.fc37.x86_64, but none of the providers can be installed
conflicting requests
You can try to add to command line:
–skip-broken to skip uninstallable packages
A more successful command was to run: sudo rpmconf -a
This gave me a list of updates to confirm with Y/N 's - I opted Y for all…
conflicting requests
Problem 2: installed package kernel-modules-6.5.10-100.fc37.x86_64 requires kernel-modules-core-uname-r = 6.5.10-100.fc37.x86_64, but none of the providers can be installed
conflicting requests
You can try to add to command line:
–skip-broken to skip uninstallable packages
curl: (37) Couldn’t open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39
Could not execute curl
christiantaylor@Fedora:~$
rpmconf helps deal with configuration files, but you have packages from Fedora 37 and 39. This can happen when a package is abandoned so there is no upgrade available, but there are current versions of the Fedora 41 kernel modules and rpmconf. It seems you have some old packages built with old libraries that break updating to Fedora 41.
At this point, you may be better off making a backup of user files and local configuration changes (usually edits to configuration files under /etc) and doing a fresh install. If that is not an option (e.g., you depend on a a package that is not available in F41), you would need to make a list of installed packages from older Fedora versions (in a terminal, sudo dnf list installed grep -v fc41). Decide if any are “mission critical”, and try to remove the others. Look for current replacements for “mission critical” packages.
As a last resort, you can create a VM running an older Fedora version, but often old “mission critical” packages are no longer available. If source is available you may be able to build the app.
Thank you George, I think I’ll try a fresh f14 install having first saved my files onto an external disk. It seems by far the easiest option at this stage although I was kind of holding out for some magic terminal command that would succeed in deleting all the older packages leaving only the f41 system behind. Thank you for your patience and kind advice.