As before you upgrade Ubuntu ,you have to remove unnecessary and corrupted packages . I have resolved issue by following commands:
apt list --upgradable
sudo apt autoremove
sudo do-release-upgrade -h
sudo do-release-upgrade -d -f DistUpgradeViewGtk3
There is nothing important on your list to select.
The important sources are on the "Ubuntu Software" tab. Most folks want the "Updates" and "Security" boxes. The others are optional.
"Source Code" is for folks who want to modify and recompile the software. If you don't know what that means, then you don't need to ...
Try the following steps to add the MySQL repository to your list and install MySQL 8.0. I have not tested this, but according to the docs it should work (unless I made a typing mistake).
Install the MySQL GPG Public key to your APT keyring: (also see this post)
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys 5072E1F5
Add the MySQL Xenial Repo to ...
For me the solution was install y-ppa-manager and with the ui menu install missing gpg keys. I share my solution, i hope its helps
$ sudo add-apt-repository ppa:webupd8team/y-ppa-manager
$ sudo apt update
$ sudo apt install y-ppa-manager
then run the app with "y-ppa-manager" and in the menu press "advanced" option, and the press "...
I had the same problem. Temporary solution was to change in Grub to use Linux 5.4.0.-51-generic
Wireless adapter QCA9665 / AR9565
modprobe: Fatal: Module R8101 not found in Directory /lib/modules/5.4.0.-52-generic
No sound for me either. Fixed it with...
I used aplay to find my device...
this showed me my analog output was...
HDA Intel PCH, ALC892 Analog
Hardware device with all software conversions
I tested the audio with (using 0,0 that I learnt from the previous command)...
aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Left.wav
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt do-release-upgrade (if you want to upgrade to the latest version. ex: 20.04>20.10)
If one of this commands send a error, you may upload it in the forum too
For anyone encountering this problem - I managed to fix it, although I don't know what has finally fixed it.
I've removed again ~/.config/pulse and then reboot. Didn't work. So I removed pulse directory again and then change name of "old_pulse" back into "pulse" (I've done this before). And then rebooted - and it works now. But I don't ...
Reinstall the programs, but remove corresponding files in /etc/apt/sources.list.d/. In case of Brave, see if there is any corresponding file with the command
before, remove it
sudo rm /etc/apt/sources.list.d/brave-browser-*.list
Long story short, after some research and examining the logs I decided to take a shot at reinstalling a few things. To that end I tried the following:
sudo apt-get install --reinstall dbus python-dbus python3-dbus
Fortunately this seemed to clear up the problem.
It did for me (on Chromium), but only because since Ubuntu 19.10, Chromium comes as a snap instead of a deb, meaning the location of cookies, history, user sign-ins, extensions, etc. is now at ~/snap/chromium/common/chromium/Default instead of ~/.config/chromium/Default. Copying that folder over makes all things I listed appear again in Chromium.
Possible workaround/troubleshooting procedure...
If you believe that you have a Nvidia driver problem, boot with nomodeset, and then purge the Nvidia drivers, and try to reinstall them, if you have the correct version of driver for your GPU and 20.10.
Boot to the GRUB menu
hit the e key to enter edit mode
find "quiet splash`
change it to &...
In all currently supported versions of Ubuntu open the terminal and type:
sudo apt-add-repository ppa:maarten-fonville/android-studio
sudo apt update
sudo apt purge android-studio-4.0 # completely uninstall Android Studio
sudo apt install android-studio-4.0
Some parts of Firefox seem to fail when it gets upgraded by apt while an instance is running.
This includes things such as opening a local file or accessing certain media content types, from my personal experience. Probably all things for which it would load some external libraries that it didn't have in memory before, so when it tries this after an update, ...
I have had Firefox automatically update for me all the time in the past. But, this can be disabled. The version of Firefox that is in the Ubuntu repositories no longer has the checkbox under the General tab of Preferences to enable or disable the automatic updates.
However, if you go to your address bar and type in about:config and bring it up you can set ...
I had a similar problem when upgrading from 18.04 to 20.04, although it only affected the headphones and not the laptop speakers. I also experienced problems in controlling the volume.
The root cause of the problem was in the default software settings not being ok for the specific hardware (intel card on asus laptop) while for 18.04 it had worked out of the ...
Maintainer of the NGINX PPA repository here!
It's pending being copied into the stable repository. Got some build errors hitting the builders that have prevented me copying a newer into the stable repos. I'm working on a fix for that in those repos.
Patience please, I've got a lot of obligations outside of Ubuntu to get through ;)
Note that the repository ...
Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh. You can check when it does refresh in your system.
snap refresh --time
You can also change snap refresh schedule. For example snaps refersh take places between only certain timings (between 1 and 2 , 10 and 12).
sudo snap ...
You have multiple problems. Just read your output, and it will tell you everything you need.
You have obsolete PPAs. Remove them.
You have a mangled script.
Your output says:
/usr/sbin/grub-mkconfig: 13: /etc/default/grub: After: not found
The /usr/sbin/grub-mkconfig file is provided by the grub-common package. Simply re-install it: sudo apt install --...
Actually I found an answer on Error: subprocess installed post-removal script returned error exit status 1 - Ubuntu Forums
The steps that worked for me are pasted below
The problem appears to be in the post installation script of GRUB: /etc/kernel/postrm.d/zz-update-grub
I don't have the problem but I've done what follows. The only difference is that my ...
Have you added any third party repository? If yes, please try remove or disable them. Also, clear your "apt" cache and. To the steps bellow, you need to open a terminal and be confortable with it.
To remove/clean third party repositories:
If they were added as includes to "sources.list":
sudo rm -f /etc/apt/sources.list.d/*
If they ...
sudo apt-get update –fix-missing
sudo dpkg --configure -a
sudo apt-get install -f
the problem of a broken package still exist the solution is to edit the dpkg status file manually.
sudo nano /var/lib/dpkg/status (you can use vim or gedit instead of nano)
Locate the corrupt package, and remove the whole block of information about it ...
You can use Update Manager or the shell.
Both will offer to update you only to the next LTS of Ubuntu. They won't offer to skip releases.
To prepare for a release-upgrade:
Return your system to as close to stock condition as possible.
If you have added PPAs or non-Ubuntu sources, remove them and uninstall the packages that came from those sources.
I also find this Thunderbird incompatibility between versions annoying. Logging this with Mozilla I asked if at least compatibility could be retained between say all subversions of say Thunderbird 68.x.x but got the reply that this is not considered important. I have found this to have occurred only in the past couple of years. The answer seems to be ...
After installing, you should have the following file:
with this content:
deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
This will allow you to update it with apt
sudo apt update
sudo apt upgrade
Your system might be properly broken and require a fresh installation. We upgraded many machines (>30) using this procedure recently and only one VM experienced problems.
As user206* above says, try to log in to a console or boot to a console with Ctrl + F1
# is the hard disk 100 % full ?
# try to resume the upgrade
sudo apt upgrade
# perhaps try ...
Perhaps no more place. After an update a lot of package are downloaded and your / is full and system can't not create tmp file
Try to clean package downloaded with command sudo apt-get clean.
CTRL+F1 for switching to a console.
Ubuntu 18.04 LTS Bionic Beaver is not an old-releases. It is supported release.
So you have to replace the repo-lines by archive back.
Doing this programmatically is possible by executing:
sudo sed -i "s|old-releases.ubuntu.com/ubuntu bionic|archive.ubuntu.com/ubuntu bionic|g" /etc/apt/sources.list
And then run sudo apt-get update as usual.
I can think of 2 versions:
you can write a script that interogates the right url on https://packages.ubuntu.com/ (like: https://packages.ubuntu.com/focal/mousepad) and grabs from there the info. This could be written pretty easy in python.
you can write a (bash)script that checks directly in apt if the package updated. Like: apt show package-name | grep ...
I found a related post that seems it could have addressed the issue but before getting a chance to do try it a new update came and the aforementioned problems are now resolved. I'm not sure what package was responsible for the problems but here's my apt log before and after the update that fixed it.
The update that caused the problem:
Start-Date: 2020-10-08 ...
You can find the the latest package to solve the problem .
Install the prerequisites:
sudo apt install python3-apt
From the download location of the PYZ bundle run:
sudo python3 -OEs aptsources-cleanup.pyz
Follow the instructions appearing on the screen.
REFERENCE = https://askubuntu.com/a/762815/1122646
If you simply want to update your system, you can place the following in /etc/cron.daily/update.sh, or /etc/crontab and set to run as root user:
apt update && apt upgrade -y
If you want to use a GUI application, you can simply call update-manager, which will prompt for a password when run.
user535733's answer is obviously more accurate, but I'...
Update Notifier already checks daily.
It's an apt systemd timer. It runs at a different random time each day.
In this example, you can see that apt-daily (which runs sudo apt update) ran 4:24 ago, and will run again in 1:37.
$ systemctl list-timers apt-daily.timer
NEXT LEFT LAST PASSED UNIT ...
The simplest solution is this:
Go to "Software & Sources/Updates" application.
In the other software tab, you should see your erring PPA, which is https://packages.sury.org/php bionic Release
Remove the said entry from the sources.
Try the update again.
This should solve the problem.
make sure your repositories are set on the nearest server: go to software and update, there you can select a server (most of the times you should chose your country). check your internet and try sudo apt dist-upgrade
If you have trouble installing mkusb, (also my choice for installer), you can use Gnome-Disks.
Gnome-disks has an option to "Restore Disk Image"
This option can be used to flash the ISO files of many Linux distributions to a USB drive, creating a bootable USB.
Open Disks, select the USB you want to install the ISO on, click the 3 lines ...
In the link https://launchpad.net/~wireguard it says:
This formerly was responsible for producing a PPA for WireGuard on Ubuntu. That functionality has now been folded into Ubuntu itself, so our old PPA has been removed. Simply run apt install wireguard on all Ubuntus ≥ 16.04.
Each apt-get update command is trying to fetch the package information but fails ...
The mentioned PPA owner does not provide packages anymore.
You have to remove it by
sudo apt-add-repository -r ppa:wireguard/wireguard
Instead you have to add universe pocket and install the package from it:
sudo apt-add-repository universe
sudo apt-get update
sudo apt-get install wireguard
I suggest that you download UbuntuStudio 20.04.1 LTS (or some other flavour of 20.04.1 LTS).
Then you can use dd, but it is not 'idiotproof'. Even several linux gurus have destroyed data using dd. So if you want to use it, check and double-check that you will be writing to the correct target drive, the USB pendrive.
A safer alternative is to use mkusb. ...
So I fixed it.
In short, the key parts were
Identify the failing pre-remove and insert exit 0 to skip it.
Reinstall all libappstream packages.
In detail (not all of these may be required, but this is what I did):
As written in "EDIT 2" above, I inserted exit 0 in the beginning of the pre-remove script: /var/lib/dpkg/info/pritunl-client-gtk.prerm