{"id":23009,"date":"2026-07-16T00:03:43","date_gmt":"2026-07-15T18:03:43","guid":{"rendered":"https:\/\/mcqacademy.com\/en\/?p=23009"},"modified":"2026-08-05T18:09:45","modified_gmt":"2026-08-05T12:09:45","slug":"how-to-install-and-uninstall-software-on-linux-mint-and-debian-based-linux","status":"publish","type":"post","link":"https:\/\/mcqacademy.com\/en\/how-to-install-and-uninstall-software-on-linux-mint-and-debian-based-linux\/2026\/","title":{"rendered":"How to Install and Uninstall Software on Linux Mint and Debian-Based Linux"},"content":{"rendered":"\n<p>Installing software on Linux Mint, Ubuntu, Debian, and other Debian-based Linux distributions is usually simple. However, Linux applications are distributed in several formats, including APT packages, <code>.deb<\/code> files, Flatpaks, Snaps, AppImages, compressed archives, and source code.<\/p>\n\n\n\n<p>Each format uses a different installation and removal method. For example, an AppImage is normally removed by deleting its file, while an application installed through APT should be removed with an APT command.<\/p>\n\n\n\n<p>This guide explains how to safely install, update, identify, troubleshoot, and uninstall software on Linux Mint and other Debian-based operating systems. It is written for beginners but also includes useful commands for experienced Linux users.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Important Corrections to Common Linux Commands<\/h2>\n\n\n\n<p>Before starting, it is important to correct a few common misunderstandings about Linux software installation.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A <code>.tar.gz<\/code> file is a compressed archive. It is <strong>not a Snap package<\/strong>.<\/li>\n\n\n\n<li>An AppImage is normally a portable executable file. It is not managed by <code>apt<\/code> or <code>dpkg<\/code>.<\/li>\n\n\n\n<li>To remove an AppImage, you normally delete the AppImage file and any optional shortcuts or settings it created.<\/li>\n\n\n\n<li>For a local <code>.deb<\/code> package, <code>sudo apt install .\/package.deb<\/code> is usually better than <code>sudo dpkg -i package.deb<\/code> because APT can resolve dependencies.<\/li>\n\n\n\n<li>You normally do not need <code>sudo<\/code> to make an AppImage executable.<\/li>\n\n\n\n<li><code>apt purge<\/code> removes package-managed configuration files, but it does not normally remove all personal settings from your home directory.<\/li>\n<\/ul>\n\n\n\n<!--more-->\n\n\n\n<h2 class=\"wp-block-heading\">Choose the Correct Installation Method<\/h2>\n\n\n\n<p>The correct installation command depends on the software format.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Software format<\/th><th>Install with<\/th><th>Remove with<\/th><\/tr><\/thead><tbody><tr><td>Linux repository package<\/td><td><code>apt install<\/code><\/td><td><code>apt remove<\/code> or <code>apt purge<\/code><\/td><\/tr><tr><td><code>.deb<\/code> package<\/td><td><code>apt install .\/file.deb<\/code><\/td><td><code>apt purge package-name<\/code><\/td><\/tr><tr><td>Flatpak<\/td><td><code>flatpak install<\/code><\/td><td><code>flatpak uninstall<\/code><\/td><\/tr><tr><td>Snap<\/td><td><code>snap install<\/code><\/td><td><code>snap remove<\/code><\/td><\/tr><tr><td>AppImage<\/td><td>Make executable and run<\/td><td>Delete the AppImage file<\/td><\/tr><tr><td><code>.tar.gz<\/code> or <code>.tar.xz<\/code><\/td><td>Extract and follow its instructions<\/td><td>Depends on how it was installed<\/td><\/tr><tr><td><code>.run<\/code>, <code>.bin<\/code>, or installer script<\/td><td>Run the verified installer<\/td><td>Use the vendor-provided uninstaller<\/td><\/tr><tr><td>Source code<\/td><td>Compile using its build system<\/td><td>Use its uninstall target or installation record<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Which Method Should We Prefer?<\/h2>\n\n\n\n<p>When the same application is available in several formats, the following order is generally easier and safer to maintain:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Linux Mint Software Manager or the official APT repositories<\/li>\n\n\n\n<li>The software developer\u2019s official APT repository<\/li>\n\n\n\n<li>A verified Flatpak from a trusted publisher<\/li>\n\n\n\n<li>An official <code>.deb<\/code> package<\/li>\n\n\n\n<li>An official AppImage or Snap package<\/li>\n\n\n\n<li>A precompiled archive supplied by the developer<\/li>\n\n\n\n<li>Compiling the application manually from source code<\/li>\n<\/ol>\n\n\n\n<p>Software installed through a package manager is usually easier to update, repair, and remove. Manually installed applications give you more control, but Linux may not automatically know which files belong to them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Considerable Security Checks Before Installing Software<\/h2>\n\n\n\n<p>Installing software means allowing code to run on your computer. A malicious installer may steal passwords, browser sessions, personal files, SSH keys, or other sensitive information.<\/p>\n\n\n\n<p>Before installing software from outside the official Linux repositories, check the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Download the file from the application\u2019s official website or verified repository.<\/li>\n\n\n\n<li>Check that the website address is spelled correctly.<\/li>\n\n\n\n<li>Confirm that the package supports your Linux distribution and version.<\/li>\n\n\n\n<li>Confirm that it supports your computer\u2019s processor architecture.<\/li>\n\n\n\n<li>Compare the downloaded file&#8217;s checksum with the checksum published by the developer.<\/li>\n\n\n\n<li>Verify the digital signature when the developer provides one.<\/li>\n\n\n\n<li>Read the installation instructions before running commands with <code>sudo<\/code>.<\/li>\n\n\n\n<li>Create a Timeshift snapshot before installing drivers, kernels, or other system-level software.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Check Your Linux Architecture<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg --print-architecture\nuname -m<\/code><\/pre>\n\n\n\n<p>Common architecture names include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>amd64<\/code> or <code>x86_64<\/code> for most modern Intel and AMD computers<\/li>\n\n\n\n<li><code>arm64<\/code> or <code>aarch64<\/code> for 64-bit ARM devices<\/li>\n\n\n\n<li><code>i386<\/code> for older 32-bit computers<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Verify a SHA-256 Checksum<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sha256sum downloaded-file.deb<\/code><\/pre>\n\n\n\n<p>Compare the displayed value with the SHA-256 value published on the developer\u2019s official website.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Security warning:<\/strong> Avoid blindly running commands such as <code>curl example.com\/script.sh | sudo bash<\/code>. Download the script, inspect it, and confirm that it comes from a trusted source before executing it.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Method 1: Install Software with Linux Mint Software Manager<\/h2>\n\n\n\n<p>Software Manager is the easiest option for most Linux Mint users. It provides a graphical interface for installing and removing applications.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the Linux Mint application menu.<\/li>\n\n\n\n<li>Search for <strong>Software Manager<\/strong>.<\/li>\n\n\n\n<li>Open Software Manager and search for the application.<\/li>\n\n\n\n<li>Check whether the result is a system package or Flatpak.<\/li>\n\n\n\n<li>Review the description, publisher, source, and permissions.<\/li>\n\n\n\n<li>Click <strong>Install<\/strong>.<\/li>\n\n\n\n<li>Enter your password when requested.<\/li>\n<\/ol>\n\n\n\n<p>To uninstall it later, open its page in Software Manager and click <strong>Remove<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 2: Install Software with APT<\/h2>\n\n\n\n<p>APT is the standard package-management system used by Debian, Ubuntu, Linux Mint, and many related distributions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Update the Package List<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update<\/code><\/pre>\n\n\n\n<p>This command downloads the latest package information from your configured repositories. It does not install all available updates.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Search for a Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt search application-name<\/code><\/pre>\n\n\n\n<p>Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt search vlc<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">View Package Information<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt show package-name<\/code><\/pre>\n\n\n\n<p>This displays information such as the package version, download size, installed size, dependencies, description, and homepage.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Install the Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install package-name<\/code><\/pre>\n\n\n\n<p>Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install vlc<\/code><\/pre>\n\n\n\n<p>Always review the list of packages that APT plans to install before confirming.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Reinstall a Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install --reinstall package-name<\/code><\/pre>\n\n\n\n<p>This can help when an installed package has missing or damaged files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 3: How do we Install a Local .deb File<\/h2>\n\n\n\n<p>A <code>.deb<\/code> file is a Debian package. Many developers provide <code>.deb<\/code> downloads for Debian, Ubuntu, and Linux Mint.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Inspect the Package<\/h3>\n\n\n\n<p>Display basic package information:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg-deb --info package-name.deb<\/code><\/pre>\n\n\n\n<p>List the files stored inside the package:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg-deb --contents package-name.deb<\/code><\/pre>\n\n\n\n<p>Display the internal package name:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg-deb -f package-name.deb Package<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended Installation Command<\/h3>\n\n\n\n<p>Open the terminal in the directory containing the downloaded file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd ~\/Downloads\nsudo apt install .\/package-name.deb<\/code><\/pre>\n\n\n\n<p>The <code>.\/<\/code> prefix tells APT that you are installing a local file.<\/p>\n\n\n\n<p>You may also use the complete file path:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install \/home\/username\/Downloads\/package-name.deb<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Alternative dpkg Command<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dpkg -i package-name.deb<\/code><\/pre>\n\n\n\n<p>The <code>dpkg<\/code> command installs the package directly, but it may not automatically install missing dependencies.<\/p>\n\n\n\n<p>If you face dependency errors, run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt --fix-broken install\nsudo dpkg --configure -a<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 4: Install Software from a Third-Party APT Repository<\/h2>\n\n\n\n<p>Some developers provide their own APT repositories. This allows the application to receive updates through your normal package-update system.<\/p>\n\n\n\n<p>Adding a repository also gives that repository permission to provide software to your system. Therefore, only add repositories from trusted developers.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Follow instructions from the developer\u2019s official website.<\/li>\n\n\n\n<li>Confirm that the repository supports your Linux version.<\/li>\n\n\n\n<li>Avoid using the deprecated <code>apt-key<\/code> method when modern keyring instructions are available.<\/li>\n\n\n\n<li>Do not add repositories from random blogs or copied commands without checking them.<\/li>\n\n\n\n<li>Remove unused repositories when you no longer use their applications.<\/li>\n<\/ul>\n\n\n\n<p>After adding a valid repository, applications are normally installed with:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update\nsudo apt install package-name<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 5: Install and Remove Flatpak Applications<\/h2>\n\n\n\n<p>Flatpak is a cross-distribution application format commonly used for desktop software. Flatpak applications run with sandboxing and may request permission to access files, devices, or other system resources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Check Whether Flatpak Is Installed<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak --version<\/code><\/pre>\n\n\n\n<p>Install Flatpak when necessary:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update\nsudo apt install flatpak<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Search for an Application<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak search application-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">How to Install using Flatpak<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak install flathub application-id<\/code><\/pre>\n\n\n\n<p>Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak install flathub org.videolan.VLC<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Get the List of Installed Flatpak Applications<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak list --app<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Update Flatpak Applications<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Review Application Permissions<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak info --show-permissions application-id<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">How to Uninstall using Flatpak<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak uninstall application-id<\/code><\/pre>\n\n\n\n<p>To remove the application together with its Flatpak-managed data:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak uninstall --delete-data application-id<\/code><\/pre>\n\n\n\n<p>Remove unused runtimes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak uninstall --unused<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 6: Install and Remove Snap Packages<\/h2>\n\n\n\n<p>Snap is another cross-distribution software format. Snap applications are managed by the <code>snapd<\/code> service.<\/p>\n\n\n\n<p>Linux Mint disables Snap installation through APT by default. Enable it only when you intentionally want to use Snap packages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Enable Snap on Linux Mint<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rm -f \/etc\/apt\/preferences.d\/nosnap.pref\nsudo apt update\nsudo apt install snapd<\/code><\/pre>\n\n\n\n<p>After installation, log out and log in again, or restart your computer if Snap applications do not appear immediately.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Search for a Snap Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>snap find application-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Install a Snap Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo snap install snap-name<\/code><\/pre>\n\n\n\n<p>Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo snap install vlc<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">List Installed Snaps<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>snap list<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Update Snap Packages<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo snap refresh<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Review Snap Permissions<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>snap connections snap-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Remove a Snap Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo snap remove snap-name<\/code><\/pre>\n\n\n\n<p>To remove it without creating an automatic Snap data snapshot:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo snap remove snap-name --purge<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 7: Run and Remove an AppImage<\/h2>\n\n\n\n<p>An AppImage is usually a portable application stored in one executable file. It normally does not need a traditional installation process.<\/p>\n\n\n\n<p>Create a directory for AppImages:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir -p ~\/Applications<\/code><\/pre>\n\n\n\n<p>Move the downloaded file into that directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mv ~\/Downloads\/Application.AppImage ~\/Applications\/<\/code><\/pre>\n\n\n\n<p>Make it executable:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>chmod +x ~\/Applications\/Application.AppImage<\/code><\/pre>\n\n\n\n<p>Run it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>~\/Applications\/Application.AppImage<\/code><\/pre>\n\n\n\n<p>Do not normally run an AppImage with <code>sudo<\/code>. A desktop application rarely needs full administrative access.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Remove an AppImage<\/h3>\n\n\n\n<p>Close the application and delete the AppImage file:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rm ~\/Applications\/Application.AppImage<\/code><\/pre>\n\n\n\n<p>If the application created a menu shortcut, search for it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>find ~\/.local\/share\/applications -iname '*application-name*.desktop' -print<\/code><\/pre>\n\n\n\n<p>Review the result before deleting the exact shortcut file.<\/p>\n\n\n\n<p>The application may also store settings under:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>~\/.config\/<\/code><\/li>\n\n\n\n<li><code>~\/.local\/share\/<\/code><\/li>\n\n\n\n<li><code>~\/.cache\/<\/code><\/li>\n<\/ul>\n\n\n\n<p>Search for related files before deleting them:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>find ~\/.config ~\/.local\/share ~\/.cache \\\n-maxdepth 2 -iname '*application-name*' -print<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Method 8: Use a .tar.gz or .tar.xz Archive<\/h2>\n\n\n\n<p>A <code>.tar.gz<\/code>, <code>.tgz<\/code>, <code>.tar.xz<\/code>, or similar file is a compressed archive. It may contain source code, a ready-to-run application, an installer, or ordinary files.<\/p>\n\n\n\n<p>There is no universal installation command for every compressed archive.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">View the Archive Contents<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>tar -tf application.tar.gz | less<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Extract the Archive<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>tar -xf application.tar.gz<\/code><\/pre>\n\n\n\n<p>Alternatively, extract it into a dedicated directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir extracted-application\ntar -xf application.tar.gz -C extracted-application<\/code><\/pre>\n\n\n\n<p>Open the extracted directory and look for instructions:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd extracted-application\nls -la\nless README\nless INSTALL<\/code><\/pre>\n\n\n\n<p>The documentation files may also be named <code>README.md<\/code>, <code>INSTALL.md<\/code>, or something application-specific.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Run a Precompiled Program<\/h3>\n\n\n\n<p>If the archive contains a ready-to-run program, its instructions may ask you to run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>chmod +x application-binary\n.\/application-binary<\/code><\/pre>\n\n\n\n<p>To remove a portable application extracted from an archive, delete the directory where you extracted it, provided it did not install files elsewhere.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 9: Compile Software from Source Code<\/h2>\n\n\n\n<p>Advanced users may compile software from source code. The correct commands depend on the project\u2019s build system.<\/p>\n\n\n\n<p>The following is a common example for software that uses GNU Autotools:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update\nsudo apt install build-essential\ntar -xf application.tar.gz\ncd application-directory\n.\/configure --prefix=\/usr\/local\nmake -j\"$(nproc)\"\nmake check\nsudo make install<\/code><\/pre>\n\n\n\n<p>Do not run the normal compilation command with <code>sudo<\/code>. Administrative access is usually needed only for the final installation step.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Uninstall Software Installed with make install<\/h3>\n\n\n\n<p>Return to the original source and build directory. If the project provides an uninstall target, run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo make uninstall<\/code><\/pre>\n\n\n\n<p>Not every project supports this command. When no uninstall option exists, consult the project\u2019s documentation or installation manifest.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 10: Use .run, .bin, or .sh Installers<\/h2>\n\n\n\n<p>Some proprietary applications and hardware tools are distributed as executable installer files.<\/p>\n\n\n\n<p>First, verify the source and checksum. Then make the file executable:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>chmod +x installer.run<\/code><\/pre>\n\n\n\n<p>Run it as your normal user when possible:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>.\/installer.run<\/code><\/pre>\n\n\n\n<p>Use <code>sudo<\/code> only when the verified vendor instructions require administrative access:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo .\/installer.run<\/code><\/pre>\n\n\n\n<p>There is no universal removal command for these installers. Check the installer\u2019s help:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>.\/installer.run --help<\/code><\/pre>\n\n\n\n<p>The installer may provide an uninstall script, an application-menu option, or an argument such as <code>--uninstall<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Identify How an Application Was Installed<\/h2>\n\n\n\n<p>Before uninstalling software, determine which package manager or installation method owns it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Find the Application Command<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>command -v application-name\ntype -a application-name<\/code><\/pre>\n\n\n\n<p>Resolve a symbolic link to its actual path:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>readlink -f \"$(command -v application-name)\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Check Whether a Debian Package Owns It<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg -S \"$(readlink -f \"$(command -v application-name)\")\"<\/code><\/pre>\n\n\n\n<p>If a Debian package owns the file, remove the package through APT instead of deleting the file manually.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Search Installed APT Packages<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt list --installed 2&gt;\/dev\/null | grep -i application-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Search Installed Flatpaks<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>flatpak list --app | grep -i application-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Search Installed Snaps<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>snap list | grep -i application-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Check Common Manual Installation Locations<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -la \/opt\nls -la \/usr\/local\/bin\nls -la ~\/Applications\nls -la ~\/.local\/bin<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Remove or Purge an APT Package<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Remove the Application but Keep Its Configuration<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt remove package-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Remove the Application and Package Configuration<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt purge package-name<\/code><\/pre>\n\n\n\n<p>The purge command removes configuration files managed by the Debian package. It does not normally remove your personal documents or all settings stored in your home directory.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Preview the Removal<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt -s purge package-name<\/code><\/pre>\n\n\n\n<p>The <code>-s<\/code> option simulates the operation without changing the system.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Remove Unused Dependencies<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt autoremove --purge<\/code><\/pre>\n\n\n\n<p>Always review the proposed package list before confirming. Avoid automatically adding <code>-y<\/code> until you are sure that APT will not remove anything important.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Remove Remaining Application Data Safely<\/h2>\n\n\n\n<p>An application may leave settings, caches, logs, databases, or user profiles after the main package has been removed.<\/p>\n\n\n\n<p>Common system-wide locations include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\/etc\/application-name\/<\/code><\/li>\n\n\n\n<li><code>\/var\/lib\/application-name\/<\/code><\/li>\n\n\n\n<li><code>\/var\/log\/application-name\/<\/code><\/li>\n\n\n\n<li><code>\/opt\/application-name\/<\/code><\/li>\n<\/ul>\n\n\n\n<p>Common user-specific locations include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>~\/.application-name\/<\/code><\/li>\n\n\n\n<li><code>~\/.config\/application-name\/<\/code><\/li>\n\n\n\n<li><code>~\/.local\/share\/application-name\/<\/code><\/li>\n\n\n\n<li><code>~\/.cache\/application-name\/<\/code><\/li>\n<\/ul>\n\n\n\n<p>Search for matching files before deleting anything:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>find ~\/.config ~\/.local\/share ~\/.cache \\\n-maxdepth 2 -iname '*application-name*' -print<\/code><\/pre>\n\n\n\n<p>For system directories:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo find \/etc \/var\/lib \/var\/log \/opt \\\n-maxdepth 3 -iname '*application-name*' -print<\/code><\/pre>\n\n\n\n<p>Back up important data and delete only paths you have checked carefully.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Warning:<\/strong> The <code>rm -rf<\/code> command permanently deletes files and directories. It does not move them to the desktop Trash. Never run it with an uncertain path or broad wildcard.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Remove an Unused Third-Party Repository<\/h2>\n\n\n\n<p>Removing an application does not always remove the repository that supplied it. An unused repository may later cause update errors or package conflicts.<\/p>\n\n\n\n<p>Search the APT configuration for the developer\u2019s name or domain:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -Ril \"vendor-name-or-domain\" \\\n\/etc\/apt\/sources.list \\\n\/etc\/apt\/sources.list.d\/ 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p>Review the results and remove only the exact <code>.list<\/code> or <code>.sources<\/code> file belonging to that repository.<\/p>\n\n\n\n<p>After removing the repository, refresh APT:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Complete Example: Remove AnyDesk Safely<\/h2>\n\n\n\n<p>The following example shows how to remove AnyDesk when it was installed as a Debian package.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Identify the Installation Method<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>command -v anydesk\ndpkg-query -W | grep -i anydesk\nflatpak list --app | grep -i anydesk\nsnap list | grep -i anydesk<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Stop and Disable Its Service<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo systemctl disable --now anydesk.service<\/code><\/pre>\n\n\n\n<p>If the service does not exist, systemd will display an error. You can continue with the correct removal method.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Purge the Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt purge anydesk<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Remove Unused Dependencies<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt autoremove --purge<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Find Its Repository<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -Ril \"anydesk\" \\\n\/etc\/apt\/sources.list \\\n\/etc\/apt\/sources.list.d\/ 2&gt;\/dev\/null<\/code><\/pre>\n\n\n\n<p>Remove the exact AnyDesk repository file only after confirming that it belongs to AnyDesk. Then run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6: Search for Remaining Data<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo find \/etc \/var\/lib \/var\/log \\\n-maxdepth 3 -iname '*anydesk*' -print\n\nfind ~\/.config ~\/.local\/share ~\/.cache ~ \\\n-maxdepth 2 -iname '*anydesk*' -print<\/code><\/pre>\n\n\n\n<p>When you have confirmed that the following directories belong to AnyDesk and you no longer need their contents, remove them carefully:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rm -rf -- \/etc\/anydesk \/var\/lib\/anydesk\nrm -rf -- ~\/.anydesk<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Step 7: Verify the Removal<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>command -v anydesk || echo \"AnyDesk command removed\"\n\ndpkg-query -W anydesk 2&gt;\/dev\/null \\\n|| echo \"AnyDesk package not installed\"\n\nsystemctl status anydesk.service --no-pager<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">How to Verify That an Application Is Completely Removed<\/h2>\n\n\n\n<p>Run several checks because the same application may be installed in more than one format.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>command -v application-name \\\n|| echo \"Command not found\"\n\ntype -a application-name\n\ndpkg-query -W | grep -i application-name\n\nflatpak list --app | grep -i application-name\n\nsnap list | grep -i application-name<\/code><\/pre>\n\n\n\n<p>If your terminal still remembers a removed command, clear the shell command cache:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hash -r<\/code><\/pre>\n\n\n\n<p>Check for remaining services:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl list-unit-files | grep -i application-name\n\nsystemctl --user list-unit-files \\\n| grep -i application-name<\/code><\/pre>\n\n\n\n<p>Check whether any related process is still running:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pgrep -a -i application-name<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshoot Failed APT Installations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Fix Broken Dependencies<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt --fix-broken install\nsudo dpkg --configure -a\nsudo apt update<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Check for Partially Installed Packages<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dpkg --audit<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Check Available Package Versions<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt-cache policy package-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Check Available Disk Space<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>df -h\ndf -i<\/code><\/pre>\n\n\n\n<p>The first command checks storage space. The second checks available inodes, which can run out when a filesystem contains a very large number of files.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Handle an APT Lock Error<\/h3>\n\n\n\n<p>An APT lock error usually means that another package-management process is running.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ps aux | grep -E '&#91;a]pt|&#91;d]pkg'\n\nsudo fuser \/var\/lib\/dpkg\/lock-frontend<\/code><\/pre>\n\n\n\n<p>Wait for Update Manager or the other package operation to finish.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p><strong>Do not immediately delete APT or dpkg lock files.<\/strong> Removing a lock while another package process is active may damage the package database.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Useful Commands for Experienced Linux Users<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">List Files Installed by a Package<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg -L package-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Find Which Package Owns a File<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg -S \/path\/to\/file<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Display Package Status<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dpkg-query -s package-name<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">View APT Installation History<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>less \/var\/log\/apt\/history.log\nless \/var\/log\/dpkg.log<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Clean Downloaded Package Files<\/h3>\n\n\n\n<p>Remove outdated cached packages:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt autoclean<\/code><\/pre>\n\n\n\n<p>Remove all cached package archives:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt clean<\/code><\/pre>\n\n\n\n<p>These commands remove downloaded package files. They do not uninstall applications.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Dangerous Commands and Practices to Avoid<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not run unverified internet scripts with <code>sudo<\/code>.<\/li>\n\n\n\n<li>Do not use <code>sudo chmod -R 777<\/code> to solve permission problems.<\/li>\n\n\n\n<li>Do not run normal desktop applications as root.<\/li>\n\n\n\n<li>Do not install unsigned packages with <code>--allow-unauthenticated<\/code>.<\/li>\n\n\n\n<li>Do not use <code>dpkg --force-all<\/code> as a normal dependency fix.<\/li>\n\n\n\n<li>Do not add random third-party repositories or PPAs.<\/li>\n\n\n\n<li>Do not manually delete files from <code>\/usr\/bin<\/code> when they belong to an installed package.<\/li>\n\n\n\n<li>Do not delete APT lock files while another package process is running.<\/li>\n\n\n\n<li>Do not use <code>rm -rf<\/code> with an uncertain path, empty variable, or broad wildcard.<\/li>\n\n\n\n<li>Do not mix repositories intended for different Debian or Ubuntu releases.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Quick Command Reference<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Task<\/th><th>Command<\/th><\/tr><\/thead><tbody><tr><td>Refresh APT package information<\/td><td><code>sudo apt update<\/code><\/td><\/tr><tr><td>Install an APT package<\/td><td><code>sudo apt install package-name<\/code><\/td><\/tr><tr><td>Install a local Debian package<\/td><td><code>sudo apt install .\/file.deb<\/code><\/td><\/tr><tr><td>Remove an APT package<\/td><td><code>sudo apt remove package-name<\/code><\/td><\/tr><tr><td>Purge an APT package<\/td><td><code>sudo apt purge package-name<\/code><\/td><\/tr><tr><td>Remove unused APT dependencies<\/td><td><code>sudo apt autoremove --purge<\/code><\/td><\/tr><tr><td>Install a Flatpak<\/td><td><code>flatpak install flathub application-id<\/code><\/td><\/tr><tr><td>Remove a Flatpak<\/td><td><code>flatpak uninstall application-id<\/code><\/td><\/tr><tr><td>Remove a Flatpak with its data<\/td><td><code>flatpak uninstall --delete-data application-id<\/code><\/td><\/tr><tr><td>Install a Snap<\/td><td><code>sudo snap install snap-name<\/code><\/td><\/tr><tr><td>Remove a Snap<\/td><td><code>sudo snap remove snap-name<\/code><\/td><\/tr><tr><td>Run an AppImage<\/td><td><code>chmod +x file.AppImage &amp;&amp; .\/file.AppImage<\/code><\/td><\/tr><tr><td>Remove an AppImage<\/td><td>Delete the exact AppImage file<\/td><\/tr><tr><td>Extract a compressed archive<\/td><td><code>tar -xf archive.tar.gz<\/code><\/td><\/tr><tr><td>Fix broken packages<\/td><td><code>sudo apt --fix-broken install<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is a .tar.gz file an installer?<\/h3>\n\n\n\n<p>Not necessarily. It is a compressed archive that may contain source code, a ready-to-run program, an installer, or ordinary files. Extract it and read its documentation before proceeding.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I use apt or dpkg to install a .deb file?<\/h3>\n\n\n\n<p>Use <code>sudo apt install .\/package.deb<\/code> in most cases. APT can resolve dependencies, while <code>dpkg -i<\/code> may leave the package partially configured when dependencies are missing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I uninstall an AppImage with apt or dpkg?<\/h3>\n\n\n\n<p>Normally, no. Delete the AppImage file and remove any optional menu shortcut or application-specific settings you no longer need.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between apt remove and apt purge?<\/h3>\n\n\n\n<p><code>apt remove<\/code> removes the package but keeps package-managed configuration files. <code>apt purge<\/code> also removes those package-managed configuration files. Neither command normally removes all personal settings from your home directory.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I always run apt autoremove?<\/h3>\n\n\n\n<p>You may use it to find dependencies that are no longer required. However, always review the package list before confirming the removal.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does a command still work after I removed the package?<\/h3>\n\n\n\n<p>The same application may also be installed as a Flatpak, Snap, AppImage, or manually copied executable. Use <code>type -a application-name<\/code> to find every matching command and run <code>hash -r<\/code> to clear your terminal\u2019s command cache.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is sudo required for every installation?<\/h3>\n\n\n\n<p>No. APT normally requires administrative access, but AppImages and many user-level applications can run without root privileges. Use only the permissions required for the task.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Final Recommendations<\/h2>\n\n\n\n<p>For most Linux Mint users, Software Manager and trusted APT repositories are the easiest and safest ways to install software. They provide automatic updates, dependency management, and predictable removal.<\/p>\n\n\n\n<p>Before uninstalling an unfamiliar application, identify whether it was installed through APT, Flatpak, Snap, AppImage, a vendor installer, or a source-code build. Using the correct removal method helps prevent broken packages, abandoned services, obsolete repositories, and unwanted configuration files.<\/p>\n\n\n\n<p>Most importantly, treat every installer as executable code. Verify its source, checksum, permissions, and commands before allowing it to run\u2014especially before using <code>sudo<\/code>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Installing software on Linux Mint, Ubuntu, Debian, and other Debian-based Linux distributions is usually simple. However, Linux applications are distributed in several formats, including APT packages, .deb files, Flatpaks, Snaps, AppImages, compressed archives, and source code. Each format uses a different installation and removal method. For example, an AppImage is normally removed by deleting its [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":23011,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","mcq_note":"","mcq_options":[],"mcq_multi_answer":"","mcq-view-count":0,"footnotes":""},"categories":[1871],"tags":[3221,3217,3218,3225,3222,3223,3224,3219,3215,3220,3226,3216],"class_list":["post-23009","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-tutorials","tag-appimage","tag-apt-package-manager","tag-deb-package","tag-debian-linux","tag-flatpak","tag-linux-commands","tag-linux-mint","tag-linux-package-management","tag-linux-software-installation","tag-snap-packages","tag-ubuntu-linux","tag-uninstall-software-in-linux"],"_links":{"self":[{"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/posts\/23009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/comments?post=23009"}],"version-history":[{"count":3,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/posts\/23009\/revisions"}],"predecessor-version":[{"id":23055,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/posts\/23009\/revisions\/23055"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/media\/23011"}],"wp:attachment":[{"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/media?parent=23009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/categories?post=23009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mcqacademy.com\/en\/wp-json\/wp\/v2\/tags?post=23009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}