How to Remove a PPA from Ubuntu Linux

Broken upgrade warnings, stale repository metadata, and package conflicts often trace back to a source you no longer need. When you need to remove a PPA from Ubuntu 26.04, 24.04, or 22.04, remember that a Launchpad PPA is just one kind of APT repository entry. The safest path is to check which packages it supplied first, then choose between a quick source removal and a full rollback to Ubuntu’s packaged version.

Ubuntu 26.04 and 24.04 usually store Launchpad PPAs as DEB822 .sources files, while Ubuntu 22.04 still commonly uses legacy .list entries. The same workflow lets you list active PPAs, remove them with add-apt-repository or manual cleanup, use ppa-purge when downgrades matter, and clean up any disabled source file left behind afterward.

List Active PPAs on Ubuntu

List Current PPAs in sources.list.d on Ubuntu

Start by listing the repository files under /etc/apt/sources.list.d/. This is the fastest way to see which PPAs are still active on the system.

ls /etc/apt/sources.list.d/

Newer Ubuntu releases usually name Launchpad PPA files as owner-ubuntu-ppa-codename.sources, while older entries can still appear as .list files. The filename is what you remove later if you choose the manual cleanup path.

Ubuntu 26.04 and 24.04 create .sources files for newly added Launchpad PPAs, while Ubuntu 22.04 still uses a .list file in many cases. The removal steps below work across all three supported Ubuntu LTS releases.

Example Output from sources.list.d on Ubuntu

linuxcapable@ubuntu-26-04:~$ ls /etc/apt/sources.list.d/ | grep git-core
git-core-ubuntu-ppa-resolute.sources

If the PPA filename appears in this directory, APT still has a source entry for it.

Verify Which Packages Came From the PPA on Ubuntu

Before removing a PPA, check whether it still provides a package you care about. Replace <package> with the package name you want to inspect.

apt-cache policy <package>
apt list --installed | grep <package>

apt-cache policy shows which repositories still offer the package, while the apt list check helps you see whether it is installed already. If the PPA URL still appears in the version table, removing the source can change future upgrades or reinstall behavior.

linuxcapable@ubuntu-26-04:~$ apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"
  500 https://ppa.launchpadcontent.net/git-core/ppa/ubuntu resolute/main amd64 Packages

That line confirms the package metadata still includes the PPA.

Remove a PPA from Ubuntu

Three practical ways are available for removing a PPA. The best option depends on whether you want to keep the installed package version, delete the source file manually, or force packages back to Ubuntu’s archive version.

Method	What It Changes	Keeps Current Packages?	Best For
add-apt-repository –remove	Removes the Launchpad source entry through Ubuntu’s repository tool	Yes	Normal cleanup when you only need the PPA gone
Manual file removal	Deletes the .sources or .list file directly	Yes	Broken or hand-edited entries that add-apt-repository cannot match
ppa-purge	Disables the PPA and makes Ubuntu prefer archive versions again	No, it can downgrade or remove packages	Systems that need a clean rollback from PPA packages

• Use add-apt-repository --remove when you want the quickest way to stop using a PPA.
• Delete the source file manually when the repository was added by hand or the PPA name no longer resolves cleanly.
• Use ppa-purge when the current package version from the PPA is causing trouble and you want Ubuntu to prefer its own package again.

Remove a PPA with add-apt-repository on Ubuntu

Use add-apt-repository –remove on Ubuntu

This is the fastest option when the PPA was added normally through Ubuntu’s repository tools. The -y flag accepts the confirmation prompt automatically.

sudo add-apt-repository -y --remove ppa:username/ppa-name

If add-apt-repository is missing on a minimal or server install, refresh APT first and install software-properties-common.

sudo apt update

These commands use sudo for administrative privileges. If your account is not in the sudoers file yet, add a new user to sudoers on Ubuntu before continuing.

sudo apt install -y software-properties-common

The -y flag accepts APT’s confirmation prompt automatically.

Example: Remove the Git Core PPA on Ubuntu

To remove the Git Core PPA that was added as ppa:git-core/ppa, run the command with the Launchpad PPA name instead of the local filename.

sudo add-apt-repository -y --remove ppa:git-core/ppa

Afterward, verify that the source file is gone and the package metadata no longer references the PPA.

ls /etc/apt/sources.list.d/ | grep git-core
apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

linuxcapable@ubuntu-26-04:~$ ls /etc/apt/sources.list.d/ | grep git-core
linuxcapable@ubuntu-26-04:~$ apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

No output from either check means the PPA is no longer active.

Delete PPA Source Files Manually on Ubuntu

Remove PPA Source Files Directly on Ubuntu

Manual cleanup is the fallback when the PPA name is unknown, the entry was edited by hand, or add-apt-repository reports that the PPA is not present.

sudo rm /etc/apt/sources.list.d/username-ppa-name.sources
sudo rm /etc/apt/sources.list.d/username-ppa-name.list

If you want one last inspection before deleting the file, print the first few lines first. This is especially useful on Ubuntu 24.04 and 26.04 where the PPA data lives in a DEB822 .sources file.

sed -n '1,12p' /etc/apt/sources.list.d/username-ppa-name.sources

Types: deb
URIs: https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/
Suites: resolute
Components: main
Signed-By:
 -----BEGIN PGP PUBLIC KEY BLOCK-----

Ubuntu 22.04 often stores the same PPA as a simpler one-line .list entry such as deb https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/ jammy main.

Launchpad PPAs added with add-apt-repository usually do not need a separate key-removal step in the normal cleanup path. Removing the source entry and refreshing APT is enough unless you know the repository was added manually with its own dedicated keyring file.

Verify Manual PPA Removal on Ubuntu

Refresh APT after deleting the file, then verify that the PPA URL no longer appears in package metadata.

sudo apt update
apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

linuxcapable@ubuntu-26-04:~$ apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

An empty result means APT no longer has package metadata from that PPA.

Clean Up Packages After Removing a PPA on Ubuntu

Remove Orphaned Packages After PPA Removal on Ubuntu

Removing the source does not remove packages that were already installed from it. If you no longer need those packages or their auto-installed dependencies, clean them up afterward.

sudo apt autoremove --purge

The --purge option removes package configuration files along with packages that are no longer required.

Review the package list before you confirm the removal. Shared libraries or helper packages can still matter to other software you plan to keep.

For broader package cleanup, see how to remove packages on Ubuntu using the command line. When the PPA is gone and the system is clean again, use the guide to update packages via Ubuntu command line so APT refreshes and upgrades from the repositories you still trust.

Use ppa-purge to Roll Back a PPA on Ubuntu

Install ppa-purge on Ubuntu

Use ppa-purge when you want Ubuntu to prefer archive packages again instead of keeping the PPA version. The -y flag accepts the installation prompt automatically.

sudo apt install -y ppa-purge

If Ubuntu reports that ppa-purge has no installation candidate, enable Universe first. The package is available from Universe on supported Ubuntu releases, so start with enable Universe and Multiverse on Ubuntu and then rerun the install command.

A package-policy check confirms that ppa-purge is installed and available from Ubuntu’s Universe component.

apt-cache policy ppa-purge

linuxcapable@ubuntu-26-04:~$ apt-cache policy ppa-purge
ppa-purge:
  Installed: 0.2.8+bzr63-0ubuntu4
  Candidate: 0.2.8+bzr63-0ubuntu4
  Version table:
 *** 0.2.8+bzr63-0ubuntu4 500
        500 http://au.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
        100 /var/lib/dpkg/status

Run ppa-purge on Ubuntu

The ppa-purge command disables the PPA and makes Ubuntu prefer its own package version again. Use -y only when you are comfortable accepting the proposed downgrade or removal automatically.

sudo ppa-purge -y ppa:username/ppa-name

Example: Purge the Git Core PPA on Ubuntu

When you want Git to come from Ubuntu’s archive again instead of the Git Core PPA, purge the Launchpad entry directly.

sudo ppa-purge -y ppa:git-core/ppa

linuxcapable@ubuntu-26-04:~$ sudo ppa-purge -y ppa:git-core/ppa
Updating packages lists
PPA to be removed: git-core ppa
Package revert list generated:

Updating packages lists
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 43 not upgraded.
W: --force-yes is deprecated, use one of the options starting with --allow instead.
PPA purged successfully

After the purge completes, confirm that the PPA URL no longer appears in package metadata.

apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

linuxcapable@ubuntu-26-04:~$ apt-cache policy git | grep -F "https://ppa.launchpadcontent.net/git-core/ppa/ubuntu"

An empty result means the PPA is no longer active in APT, even if a disabled source file still exists on disk.

Clean Up Disabled .sources Files After ppa-purge on Ubuntu

On Ubuntu 24.04 and 26.04, ppa-purge can leave the PPA file behind with Enabled: no in the DEB822 entry. That disables the repository correctly, but you may still want to delete the leftover file for a cleaner /etc/apt/sources.list.d/ directory.

grep -Ril '^Enabled: no' /etc/apt/sources.list.d/
sudo rm /etc/apt/sources.list.d/username-ppa-name.sources
sudo apt update

The first command searches the source directory recursively and prints only filenames that contain Enabled: no, which makes it easier to spot leftover disabled DEB822 entries before you delete them.

Ubuntu 22.04 can leave the old .list file behind after ppa-purge too, so the same manual cleanup idea applies there.

Troubleshoot PPA Removal Problems on Ubuntu

Fix “Repository Does Not Have a Release File” Errors on Ubuntu

This error usually means a stale PPA entry is still present and APT keeps trying to refresh it. Remove the matching file from /etc/apt/sources.list.d/, then refresh APT again.

ls /etc/apt/sources.list.d/
sudo rm /etc/apt/sources.list.d/username-ppa-name.sources
sudo rm /etc/apt/sources.list.d/username-ppa-name.list
sudo apt update

Handle add-apt-repository PPA not found Errors on Ubuntu

When add-apt-repository --remove says the PPA is not present, the source was usually added manually, renamed, or already disabled. Switch to manual file removal and identify the exact filename under /etc/apt/sources.list.d/ instead of retrying the same Launchpad name.

Resolve PPA Packages Without Ubuntu Replacements

Some PPAs carry software that Ubuntu does not package at all. Before you purge the source, decide whether you want an alternative installation path or whether you still need that software.

• Search Flathub with flatpak search package-name if the software is available there.
• Check whether the upstream project offers an official .deb package or vendor repository.
• Keep the PPA temporarily if Ubuntu has no replacement yet and you still depend on that package.

PPA Removal on Ubuntu FAQ

Conclusion

Your APT sources are cleaner now, and the same workflow lets you remove a PPA from Ubuntu without leaving stale package metadata behind. If you want to keep the system tidy after the cleanup, update packages via Ubuntu command line, or install Synaptic Package Manager on Ubuntu if you prefer reviewing package changes through a graphical interface.