Problem Description:
I have a separate system that is 25.10 with NFS server exports.
The clean install App Center spins when searching indefinitely so
using apt-cache search I can no longer find nfs-common package.
Example:
click App Center → search for nfs
just see a spinning arrow circle icon
Click terminal → cli → apt-search nfs
No nfs-common package found
$ sudo apt install nfs-common
Package nfs-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Error: Package ‘nfs-common’ has no installation candidate
What I’ve Tried:
Listing the solutions or workarounds I’ve already attempted.
Internet search suggest looking at system files
$ ls -ls /etc/apt/sources.list.d/
total 8
4 -rw-r–r-- 1 root root 398 Jun 18 15:55 ubuntu.sources
4 -rw-r–r-- 1 root root 2564 Apr 22 21:22 ubuntu.sources.curtin.orig
They appear as expected but not finding nfs-common
I figured out to down load the package list and extract it as Package.Main
then search it for nfs-common
I find it in the main package list but apt and App Center don’t list it
nfs-common/resolute,now 1:2.8.5-1ubuntu1 amd64 [installed]
NFS support files common to client and server
$ apt-cache search nfs-common
dracut-network - dracut is an event driven initramfs infrastructure (network modules)
nfs-common - NFS support files common to client and server
You don’t need sudo for that. One should always run commands with the least privileges required. While it doesn’t matter in this particular instance, all kinds of weird issues can arise, when files that are supposed to be owned and readable by the normal user were accidentally created as root; for instance, there is some evidence that this user brought some headaches on himself by the careless use of sudo.
Also, direct usage of apt-cache and apt-get has been deprecated for quite a long time now; most of their functionality has been subsumed by apt(8).
BTW, it’s always nice to mark the issue as solved by selecting the respective post, so other users with the same or similar issues can find it.
The issue is not solved I just used the wrong CLI commands and sudo when not needed and then recalled from my human memory steps I have long sinced moved on from.
The Ubuntu 26.04 desktop iso does not install is the issue.
Can we get back to where I should look for help with the installation of Ubuntu desktop 26.04 ?
I have been working on this three days and using Linux for 31 years since version 2 of Red Hat in 1995.
I am just not a programmer.
I use apt so that also is good to hear about apt search -n
Wait, according to your OP the desktop did install; the only thing missing is nfs-common, according to that; easily fixed:
sudo apt install nfs-common
Sorry, when/where did I miss that’s the actual issue?
On what exactly? You seem to be talking about some other issue.
Me neither; it’s not a requirement for this issue, whatever it may actually be. In my ~25 years of experience on Debian-based systems — since Woody —, I never once had to actually write code to fix things.
After a nights sleep I powered on the system and it said BIOS had no date and time.
Maybe me replacing CMOS battery will improve the install.
The 25.10 used previously also failed to complete but boots with issues.
I am using Balena-etcher to verify iso copy as before I used disks without verify.
My Debian days are Pi and Beagle often.
Less hardware and speed on a small ARM system makes for faster learning on how to do installs.
Before that was DEC Alpha 64 bit given to me by Linus T for taking his and Bob Young at DECUS 55 in 1995.
Further progress in that 25.10 fails but only after creating bootable ssd drive.
Hardware is going read only somehow during install.
If I do not use network and minimal install without third party or media packages, it runs long enough to make the internal drive bootable.
Replacing CMOS battery helped keep time and BIOS across reboots.
I will add the /etc/sudoers.d/ with live USB while I figure why the system is turning read only.
I removed unattended upgrades after I found that system drive becomes read only after a period of time.
I have terminal pinned and auto login enabled.
I have fix broken installs and dpkg configure -a done before read only happens.
I can use the system for a few minutes before it becomes read only so it may be happening during install as well.
Anyone know if there is a simple fix to this enigma where ssd goes read only after a time ?
This sounds more like a hardware issue than anything else, I’d check if the SSD is properly plugged, if the BIOS has the proper settings for it, if your power supply is capable enough for it etc…
A filesystem being automatically remounted read-only is a last resort protection measure, when there are I/O errors on the underlying storage device, for instance. I also seem to remember that happening in some “no space left” situations. Especially when it happens just a few minutes after starting, that might be caused by unattended-upgrades trying to do its thing and finding no space to do so.
One should always run commands with the least privileges required. While it doesn’t matter in this particular instance, all kinds of weird issues can arise, when files that are supposed to be owned and readable by the normal user were accidentally created as root; for instance, there is some evidence that