Hot answers tagged

5

You can install the 5.8 kernel to Ubuntu 20.04 now by running sudo apt install linux-generic-hwe-20.04-edge The kernel will get updates. But if you wait some time (it is a matter of days) linux-generic-hwe-20.04 (without edge) will also pull the 5.8 kernel.


4

The package handbrake is in Ubuntu's universe repository for Groovy. All you need to do to install it: If you added a PPA to your sources, remove it. Make sure that you have universe enabled. Then run: sudo apt update sudo apt install handbrake No need for a PPA. No need to risk destroying your package management system or your sources list. No need for a ...


3

That PPA is for testing only. In fact, the PPA description states: Unless you are testing updates, you should NOT install packages from this PPA. Disabling PPAs during a release-upgrade is normal. PPAs are NOT the supported Ubuntu Repositories, and some PPAs can introduce version conflicts with newer software. A normal (human) admin task after a release-...


3

There is no such thing as a "correct PPA". PPA is a personal package archive created by some user. You install software from PPA's at your own risk. If you installed nemo from Ubuntu official repositories, there is no reason to look for some PPA.


2

The latest build released for groovy in that PPA was built on 2020-09-07. The later version is for hirsute and not groovy. https://launchpad.net/%7Echrdevs/+archive/ubuntu/figma/+packages?field.name_filter=&field.status_filter=published&field.series_filter=groovy The build of 0.6.4 is figma-linux - 0.6.4-1ubuntu0 (changes file) 48 minutes ago ...


2

apt-key never downloaded keys by itself. apt-key adv passed on options to gpg, and gpg did the actual downloading (apt-key is a complicated shell script that itself creates temporary scripts to run gpg). You can still use gpg to import keys, e.g. instead of apt-key adv --recv-keys, you'd do something like: sudo gpg --no-default-keyring --keyring gnupg-ring:/...


1

Let's start with two items: The name of the PPA: SDL2 Backport to Bionic. Your release from the PPA URL you provided: Xenial (which is not Bionic) From these two facts, we can draw a conclusion: The 18.04 PPA is unlikely to have provided any usable packages to your 16.04 system. The corollary to that conclusion is that the PPA has perhaps never worked for ...


1

As the packages you download from launchpad are all cryptographically signed just like with every other debian repository, a man-in-the-middle attack is not really feasible. apt checks the signature of the downloaded .deb files and any tampering would lead to an invalid signature. Invalid signatures cause an error prior to installation. So I don't see this ...


1

The solution for me was to manually remove every single CURRENT VERSION of the packages that have but it is not going to be installed status. So I had driver version 440. I had to remove sudo apt purge libnvidia-gl-440 and so on for all of them. After that the error went away.


1

Your OS in docker is not the same as in your host system, your /etc/os-release file on your host does not matter. This is what's happening: Step 1/16 : FROM ubuntu If you don't specify the version of a package in your Dockerfile, it loads the latest version (ubuntu:latest) from docker hub. And there, you can read: The ubuntu:latest tag points to the "...


1

Yes, The PPAs you mentioned above belong to Ubuntu 18.04 LTS (Bionic Beaver). When you upgraded to Ubuntu 20.04 LTS (Focal Fossa) they were disabled as they were no longer needed by the system (unless you want to force it). The new PPAs of Focal Fossa were added during the upgrade process which contains the updated list of software (in repositories). If you ...


1

Be warned even with apt pinning it could turn your package management/system into chaos. No warranty from me. For security install ppa-purge first. If something goes bad you can try revert/delete packages with sudo ppa-purge system76-dev/stable another way for be prepared is /etc/apt/preferences.d/focal.pref Package: * Pin: release n=focal Pin-Priority: ...


1

The easiest way would be to remove the System76 repositories and change your desktop environment to Gnome. Log out from your current session Select your account from the login screen, then choose the "Ubuntu" option from the little gear menu in the bottom right corner to use Gnome, and sign in Remove any System76 repository references from the /...


Only top voted, non community-wiki answers of a minimum length are eligible