Hot answers tagged upgrade
This is an issue that has appeared before: 4 years ago when upgrading from 12.04 to 14.04.1: Why is "No new release found" when upgrading from a LTS to the next? It looks like the same issue exists for the upgrade to 16.04.1 from Trusty Tahr with the relevant update log not yet updated. There is a choice of two reasonable solutions at the ...
Run cat /etc/lsb-release and you will see that you already have 16.04.1. If not, run sudo apt update && sudo apt upgrade. In System Settings GUI you see the major release number.
This read/input-output error indicates serious disk failure! Back up all important data immediately and look for a new hard disk. You can find out more details about your disk health by checking its S.M.A.R.T. status. Open gnome-disks, select your HDD in the device list on the left and click the hamburger menu in the top right corner. Chose SMART Data &...
Try this please as a last possible solution. Open a terminal and type these commands: sudo rm /var/lib/apt/lists/* -vf sudo apt-get clean sudo apt-get update If this doesn't work either, then the hard disk problem is the most probable cause for this message unfortunately.
This is more of a guess than an actual answer. If you update the package-lists do you get any warning or errors? sudo apt-get update -- go through and check for warnings And are the sources good? cat /etc/apt/sources.list -- check if something important is out-commented.
'While Ubuntu 16.04.1 LTS has been released, automatic upgrades from Ubuntu 14.04 LTS will not begin until "early next week" according to the Ubuntu Release Team.' https://www.reddit.com/r/Ubuntu/comments/4tzgou/ubuntu_16041_lts_released_1404_users_see_upgrade/d5lp6s4
It looks like you are trying to use a CD as a repository. You can't do that in this way, because the CD doesn't have the necessary structure. If you want to make a CD accessible to APT, you have to use apt-cdrom. You can find further information on apt-cdroms man page man apt-cdrom And, no offence meant, but the error messages you quoted in your question ...
it ended up being a permission issue. so a sudo chmod 0777 -R /var/lib/plexmediaserver sudo chown plex:plex -R /var/lib/plexmediaserver sudo service plexmediaserver restart solved the issue It appears as well that the sudo apt-get remove --purge plexmediaserver does not clean all things.
A change to your alsa-base.conf in /etc/modprobe.d/ may be needed but it is not possible to say for certain as you have not listed what make and model your computer is (there are sometimes specific changes for specific hardware required in /etc/modprobe.d/alsa-base.conf and your device may not have the correct device selected even if it is not a device ...
Yes, I have done this when I moved from Mythbuntu 14.04 to Mythbuntu 16.04. I had the database backup (mythconverg-1317-20160708233351.sql.gz, automaticaly generated by the Mythbuntu 14.04 system) and the recordings on one drive, and then I installed Mythbuntu 16.04 on a different drive. I mounted the recordings in the same place in the filesystem as before. ...
Only top voted, non community-wiki answers of a minimum length are eligible