VMware ESXi and vSphere Cluster Management

Synaptic Package Manager: Install, Search, Update, and Remove Software

Learn how to use Synaptic, the graphical APT package manager, to install, inspect, update, repair, and remove software on Debian- and Ubuntu-based Linux systems.

Synaptic is a graphical package manager for Debian-based Linux systems. It provides a desktop interface for APT, allowing you to search repositories, inspect package metadata, install and remove software, apply updates, and investigate dependency problems without entering every package command manually.

This lesson covers Synaptic on Debian, Ubuntu, and compatible derivatives. Menu names can vary slightly between releases, but the basic workflow is consistent: select an action, review the queued changes, and choose Apply to execute them.

What Synaptic Is

Synaptic is a desktop graphical front end for APT. APT is the package-management framework used by Debian and many related distributions to retrieve package information, download software, install packages, upgrade installed software, and remove packages.

A package is a distributable unit of software plus metadata such as its version, dependencies, description, and installation files. A repository is a configured software source containing package indexes and package files. Synaptic reads the local package indexes maintained by APT and presents their contents in a searchable interface.

Synaptic complements command-line tools such as apt, apt-get, and dpkg; it does not replace them. The graphical interface is useful for browsing packages, examining dependencies, and reviewing a complete change plan. Command-line APT remains valuable for automation, remote administration, detailed recovery messages, and situations where the graphical desktop is unavailable.

Reading package information normally does not require administrator access. Installing, upgrading, removing packages, changing repositories, and repairing package configuration require root privileges, meaning administrative authorization. Synaptic usually requests authentication through the desktop's privilege system when an operation needs it.

Installing and Opening Synaptic

On Debian or Ubuntu, install Synaptic from a terminal with an account permitted to use sudo:

sudo apt update && sudo apt install synaptic

The older apt-get command is also valid on systems that provide it. After installation, open Synaptic from the desktop application menu by searching for Synaptic Package Manager. You can also start it from a terminal:

synaptic

A graphical desktop session and administrator authentication are normally required. If authentication fails, ask an administrator to provide authorization rather than running package changes from an untrusted account.

Recognizing the Main Window

• Category or filter pane: Browses sections, package status, origin, custom filters, or other groupings.
• Package list: Shows matching packages and their status icons or markers.
• Search and filter controls: Find packages by name, description, section, version, or other fields, depending on the selected filter.
• Details pane: Displays descriptions, versions, dependencies, files, size information, and related metadata for the selected package.
• Toolbar: Common controls include Reload, Mark All Upgrades, and Apply.
• Pending-changes summary: Shows actions queued for later execution. Marking a package does not immediately change the system.

The exact arrangement depends on the Synaptic and desktop version. When in doubt, select a package and inspect its context menu or properties window.

Core Package-Management Concepts

Synaptic separates marking from execution. To mark a package means to queue an action such as installation, upgrade, removal, or complete removal. Synaptic calculates related dependency changes and displays them for review. Clicking Apply executes the complete set of queued actions.

A dependency is another package or capability required by a package. For example, a graphical application may depend on shared libraries, desktop components, or supporting utilities. A reverse dependency is a package that depends on the package currently being inspected. Reverse dependencies are especially important before removing a library or system component.

Finding Software

Use Quick Search

1. Reload package information if the index may be outdated.
2. Enter the application name or a descriptive keyword in the quick-search field.
3. Review the matching package names, descriptions, versions, and status indicators.
4. Select a likely match and inspect its details before marking it.

A search for a familiar application name may return several packages: the main program, development files, documentation, language packs, plugins, libraries, or unrelated packages with similar names. Do not select a package solely because its name looks familiar.

Use the search filter or search-fields setting when available to search package names, descriptions, maintainers, sections, versions, or other metadata. You can also browse categories and status filters instead of searching directly.

Inspecting Package Details

Select a package and open its properties or details view. Depending on the Synaptic version, this may be available through a context menu, a package menu, or a properties button.

Useful information includes:

• The package description, which explains its purpose and often identifies whether it is an application, library, plugin, documentation package, or development package.
• The installed version and the newest version available from configured repositories.
• Dependencies required by the package.
• Reverse dependencies, which show installed or available packages that rely on it.
• Provided files, where available, to see what the package installs.
• Download size, installed size, and other size information, where available.
• Repository origin, section, architecture, and candidate version information.

Use this metadata to evaluate compatibility and purpose before making a change. In particular, inspect reverse dependencies before removing libraries, desktop components, meta-packages, or packages whose names suggest system-wide functionality.

Installing a Package Through Synaptic

The following example installs a graphical application while checking its source and dependencies:

1. Choose Reload if the package information may be stale.
2. Search for the application by name.
3. Select the intended package and open its details. Verify the description, repository origin, architecture, and available version.
4. Choose Mark for Installation.
5. When Synaptic proposes additional packages, read the dependency list. Accept required dependencies only when the complete plan makes sense.
6. Review the pending changes summary and open the detailed change list.
7. Choose Apply, confirm the summary, and authenticate when prompted.
8. Wait for downloading, unpacking, configuration, and any post-installation steps to finish.
9. Confirm that the package now has an installed status. You can also launch the application from the desktop menu.

Removing Software

Ordinary Removal

1. Find the installed package.
2. Choose Mark for Removal, not complete removal.
3. Inspect any dependent packages proposed for removal.
4. Review the pending changes and choose Apply.

Ordinary removal uninstalls the package but typically keeps package-managed system configuration files. This can be useful if you may reinstall the application and want its system settings preserved.

Complete Removal

Choose Mark for Complete Removal when you want to uninstall the package and remove its package-managed configuration files. This is often called purging. It does not necessarily delete personal data stored in a user's home directory, and it does not guarantee removal of every manually created file.

Before applying either removal type, inspect the full list of affected packages. Removing a meta-package, desktop component, core package, or shared dependency can cause many other packages to be removed. If the list is unexpectedly large, cancel the pending action and inspect reverse dependencies.

Updating Package Information and Upgrading the System

Reload refreshes local package indexes from configured repositories. It does not itself upgrade installed software. Reload before searching for newly available packages or checking for updates:

1. Choose Reload and wait for all repository indexes to finish downloading.
2. Read any warnings or errors reported during the refresh.
3. Choose Mark All Upgrades for routine eligible updates, or mark one package for upgrade.
4. Inspect additional installations, removals, replacements, or version changes required by the upgrade.
5. Choose Apply and wait until all operations complete.

Do not interrupt package operations by closing Synaptic, powering off the computer, or terminating the process while packages are being unpacked or configured. Keep stable power and network access, especially on a portable computer.

Routine package upgrades are different from a major distribution release upgrade. A release upgrade may change repositories, packages, boot components, and configuration across the system. Follow the distribution's documented release-upgrade procedure and back up important data before starting one. Do not assume that Mark All Upgrades is a substitute for that procedure.

Repositories and Software Sources

APT repositories determine which package names, versions, and updates Synaptic can see. Sources are commonly configured in /etc/apt/sources.list and files under /etc/apt/sources.list.d/. Prefer Synaptic's repository settings or the distribution's software-sources tool when editing them.

When reviewing sources, check:

• That each source matches the installed distribution release and architecture.
• That the source is reachable and maintained.
• That package signatures and trusted signing keys are handled by the distribution's supported method.
• That disabling a source will not unexpectedly remove access to packages needed by installed software.

Enable or disable repositories cautiously. Third-party repositories can provide useful software, but they can also introduce incompatible versions or dependency conflicts. Never add an untrusted source merely to obtain a newer package. After changing sources, choose Reload and read the result before marking changes.

Repairing Broken Dependencies

Broken packages are packages whose required dependencies or configuration steps are incomplete or inconsistent. Causes include an interrupted installation, incompatible versions, a failed upgrade, or conflicting third-party repositories.

1. Use the status filter to identify packages reported as broken.
2. Use Synaptic's Fix Broken Packages function when it is available.
3. Read the proposed corrective actions carefully.
4. Pay particular attention to unexpected removals, downgrades, or changes involving core packages.
5. Apply the repair only when the plan is understood and acceptable.

If graphical repair is insufficient, a terminal recovery command is:

sudo apt --fix-broken install

Review the proposed changes before confirming. If the problem involves a repository conflict, correct the source configuration first. For persistent failures, consult the documentation for the installed distribution and preserve the exact APT error messages for troubleshooting.

Synaptic and APT Command-Line Equivalents

Practical Investigation Workflow

When you are unsure whether to change a package, use this cautious sequence:

1. Select the package in the results list.
2. Open properties or details.
3. Read the description and compare installed and available versions.
4. Inspect dependencies and reverse dependencies.
5. Check the repository origin and package status.
6. Mark the intended action, then review every queued change before applying it.

This workflow is useful for deciding whether a package is the main application, an optional component, a development package, or a shared system dependency.

Safety and Operational Cautions

• Review every queued installation, upgrade, and removal before selecting Apply.
• Do not use unknown repositories or manually downloaded packages from untrusted sources.
• Maintain sufficient free disk space for downloaded archives, temporary files, and unpacked packages.
• Use stable power and network access during package operations.
• Do not run Synaptic at the same time as another APT client, Software Updater, software center, or unattended update process.
• Back up important data before broad upgrades or repository changes.
• Treat removal of core packages, desktop components, meta-packages, and shared libraries as a potentially wide system change.

Troubleshooting Common Problems

Synaptic Cannot Be Installed or Expected Packages Are Missing

Common causes include stale package indexes, disabled or incorrect repositories, and network or DNS failures. Choose Reload and read the reported errors. Verify network connectivity, check that repository entries match the installed release, correct source settings, and reload again.

Package Operations Report Broken Dependencies

An interrupted installation, incompatible package versions, or a third-party repository conflict may be responsible. Use the broken-package repair feature and inspect the plan. Do not accept broad removals without understanding them. If necessary, use sudo apt --fix-broken install and resolve conflicting sources.

Another Package Manager Is Using the System

An APT process, software center, Software Updater, or unattended update may be active. Wait for it to finish. Do not delete package-manager lock files while a valid process may still be running. If a process appears stuck, verify its state carefully before taking recovery action.

Apply Fails Because of Insufficient Disk Space

Check free space on the root filesystem and the area used for APT downloads. Remove unneeded files or obsolete packages using a method appropriate for the distribution, then retry with enough space for both downloads and unpacking.

A Package Is Unavailable or Has an Unexpected Version

The package may not exist in enabled repositories, may be hidden by a filter, or may have an older or conflicting candidate version. Clear or adjust filters, inspect package version information, and review enabled repositories. Avoid adding an untrusted source simply to obtain a different version.

Removing a Package Would Remove Many Others

The selected package may be a dependency, meta-package, desktop component, or core component. Cancel the pending action and inspect reverse dependencies. Proceed only after confirming that the full removal impact is intended.

Exam-Relevant Notes

• Reload refreshes package indexes; it does not install upgrades.
• Mark queues an action; Apply executes queued actions.
• Removal generally preserves package-managed configuration, while complete removal purges it.
• A dependency is required by a package; a reverse dependency relies on the package being inspected.
• APT sources control which packages and versions Synaptic can see.
• Package changes require root privileges, even though browsing package information may not.
• Synaptic is a graphical interface to APT and complements, rather than replaces, command-line package tools.

For a concise companion reference, see Synaptic Package Manager.