By adding the Pop PPA, you've received the patched version of GNOME Control Center, which pulls in pop-upgrade, which will prompt to upgrade to Pop!_OS 19.10. It's a required dependency of the patched version of gnome-control-center, so removing it would also remove the control center. We don't recommend adding the Pop! ppa on top of Ubuntu. We apologize for ...
You had a ppa installed that got removed at some point (maybe on an earlier Ubuntu upgrade), but the packages installed from that ppa are still on your system, resulting in dependency problems.
From your apt outputs, it seems to be ppa:oibaf/graphics-drivers.
Try adding that same ppa again, it seems to be available for cosmic:
sudo add-apt-repository ppa:...
Upgrades from previous versions are only switched on by the release team when they are are happy that there are no massive upgrade bugs hiding anywhere.
In the past, this has varied from enabling them later on the actual release day, all the way to nearly a week after release. There is absolutely no fixed rule.
In the case of this release, when I queried ...
Looks like you've added a PPA that's meant for the team that's working to integrate Firefox, Thunderbird etc. into Ubuntu
500 http://ppa.launchpad.net/mozillateam/firefox-next/ubuntu xenial/main amd64 Packages
That PPA seems to contain preliminary, "work in progress" versions. You might want to remove the PPA from ...
Following leads picked up from @Raffa (Thanks Raffa!), I managed to get things working after doing the following:
First, manually reinstall Python:
apt-get download python3 python3.7 python3.7-minimal libpython3.7-minimal
sudo dpkg -i *python3*.deb
sudo apt install -f
Then manually reinstall software-properties-common:
apt-get download software-...
Ok after a long struggle I have been able to fix this with the help of previous answers and trial and errors.
I booted into Advanced mode while booting Ubuntu press F2 when you see grub2 bootloader. On some systems you may need to press Shift to get to advanced boot menu.
In my case since I was in a VMware Workstation environment I pressed Shift or F2 to ...
You need to start reading error messages:
error: rename involves overwriting
with different file
Some file that should be written exists, and overwriting is "not allowed".
To fix, move the original ...
It takes about a week or two after release before the upgrade path that is 'automated' with the upgrade manager or do-release-upgrade is actually opened. (Why this is the case I'm not sure, but I think it has to do with bug squashing and bug handling of major issues detected post-release)
Patience is your best call here. It should be available within the ...
So I figured out what the issue is after some detective work and some experimentation. I had the Pop! ppa on my system for some reason. I guess this was a side effect of using the Pop Icon theme. I was searching through folders in /var/lib/ and found an empty pop-upgrade folder. At first I was not certain what it was, but it was entirely too coincidental for ...
I've just updated to 19.10 and had similar issue. It didn't started successfully after the automatical revoot triggered by the system update.
I restarted, chose advanced options in grub and continued with the previous kernel version (was something like 5.0.0....)
When it started I run:
sudo apt-get upgrade
It failed and asked me to run:
sudo dpkg --...
bentolor's answer led me to a different command which seemed to ultimately fix the problem:
sudo apt-get install --reinstall ubuntu-keyring
I'm guessing this restores the keyring to defaults, something must have changed since the package was last installed. Now I can run the command sudo do-release-upgrade -m desktop without the Authentication failed error....
I ran into the exact same problem. The problem is a missing signing gpg key 871920D1991BC93C. apt-key adv --keyserver http://keyserver.ubuntu.com:80 --recv-keys 871920D1991BC93C did not solve the issue as the key doesn't seem to publicy available.
$ sudo apt-key update
Warning: 'apt-key update' is deprecated and should not be used anymore!
gpg: key ...
Download the extensions you want from https://extensions.gnome.org/
Select the latest version of that extension.
Most of the time they will be in zip format so extract the file from the zip folder.
Open the extracted folder and locate the metadata.json file.
In that file, replace the shell-version with the one you currently have and save. Also copy the uuid ...
Look at the manifest. It specifies all the snaps and snap-associated packages that would be installed.
snap:core stable 7917
snap:core18 stable 1223
snap:gnome-3-28-1804 stable/ubuntu-19.10 71
The way point releases work for LTS cycle is thus:
XX.04 - initial release
XX.04.1 - second initial release with same kernel version
XX.04.2 - first HWE release, using HWE kernel (from XX.10 release)
XX.04.3 - second HWE release, using HWE kernel (from XX+1.04 release)
XX.04.4 - third HWE release, using HWE kernel (from XX+1.10 release)
XX.04.5 - final HWE ...
I experienced the same issue after updating to Ubuntu 19.10.
The following was able to solve it for me:
sudo apt-get --reinstall install yaru-theme-gnome-shell
Followed by a reboot.
I also disabled shell extensions prior to that but I'm not sure if that was necessary
I had at some point installed the yaru colors theme and my thought is that didn't play ...
The issue is not with the /usr/bin/python3 symlink, but with /usr/bin/python
To correct, for 19.04, I ran
sudo ln -sf /usr/bin/python2.7 /usr/bin/python
I found the solution here: "Your python3 install is corrupted"
looking at the answer from J. B. Rainsberger
To force the older Firefox to use your profile, invoke it with:
$ firefox --allow-downgrade
You might also want -P in there, to pick which profile is used.
(Source: Mozilla Support)
I had the same experience as you with the Firefox Beta PPA: after upgrading to 71.0b8, it refuses to run. I then downloaded Firefox Beta directly from Mozilla. That was also ...
I manage to get the system working again. First, doing sudo dpkg --remove broadcom-sta-dkms allowed sudo apt upgrade to run properly. After that, I removed the wireless drivers from dkms and reinstalled them. During reinstallation it again got stuck after depmod.... After waiting for a while I used Ctrl+C to stop the process. I thought installation hadn't ...
19.10 comes with a new version of Grub 2.04 that many have reported bugs with.
A common solution is to turn off TPM in BIOS. However other options are detailed in the bug reports and there other things to try if that doesn't work.
apt-get and Software center are just different front-ends for the same procedure. There are even more options like aptitude or Synaptic.
If that is the case, is it safe enough to only use the terminal and ignore the software center just for system updates?
Yes, after you upgrade your packages using the terminal, the Software center should stop offering ...
I solved this problem with the help of System 76 support. I downloaded a new .iso image of Ubuntu 19.04 onto a flash drive and did a clean reinstall of the operating system.
It still wasn't easy. My first attempt used a 32GB flash drive, but for some reason it got stuck, too. A second attempt with a 16GB flash drive did the trick.
I've had to download ...
I had the exact same issue and fixed it by following below steps:
Trigger CLI from the error screen using Ctrl+Alt+F3 and Login.
Then execute the command for release upgrade:
If there was issue with new release download, this should solve it, else it will print out:
No new release found.
If so, continue by updating the package ...
MySQL Server cannot be started to finish its installation:
Error while setting value 'IGNORE_SPACE,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' to 'sql_mode'
One or multiple of these sql modes are no longer available in the new MySQL version. In your case it is NO_AUTO_CREATE_USER.
See a list of valid ...
Take a look at the official list of Ubuntu mirrors.
See the ones in red? Those are not up to date. They will get up to date, eventually, by syncing with the master repository. When that's underway, file sizes won't match the master file size, and errors like this will occur.
Solution: Use another mirror. How do I change my update server in Ubuntu 18....
Was having the same here, on my new i3-8100. I believe it would affect most recent i3 and i5 without a grphical card, as these CPU have their own graphics integrated: HD 620, 630. Maybe it affects lots more people... don't know.
All new distros release was not working because of this for me.
This bug have appears between version 5.3.0 and 5.3.3 inclusively....