How to Manage Software with Synaptic Package Manager on Ubuntu and Debian

Learn how to install, update, inspect, remove, and repair APT-managed packages with Synaptic on Ubuntu, Debian, and related Linux distributions.

Synaptic is a graphical front end for APT, the package-management framework used by Debian, Ubuntu, and related distributions. It provides a visual way to search repositories, inspect package information, queue changes, and apply software transactions without performing every task in a terminal.

Synaptic is not an independent software store. It displays packages from the APT repositories configured on your system. Repository settings determine which packages and versions Synaptic can see.

What Synaptic manages

A package is a distributable software unit. It may contain an application, library, documentation, development files, metadata, or a meta-package that depends on a collection of other packages.

Synaptic can install individual packages, upgrade installed packages, perform broader dependency-aware upgrades, remove applications, purge system-wide configuration files, search and filter package records, inspect dependencies, refresh package indexes, and attempt to repair broken dependency states.

APT obtains package information from configured repositories. A repository is a software source containing package indexes and package files. A local package index is the downloaded metadata that describes what those repositories provide.

Installing Synaptic

Synaptic may not be installed on a modern Ubuntu or Debian desktop. Install it with APT from a terminal:

sudo apt-get install synaptic

Enter your administrator password when prompted. The command needs working repositories and network access. The shorter form is also commonly used:

sudo apt install synaptic

After installation, launch Synaptic from the application menu, or run:

synaptic

The desktop may request administrator authentication when the application starts. Do not run Synaptic at the same time as another package tool, such as a software updater or an active APT command.

Understanding the main interface

The exact appearance varies by desktop environment and Synaptic version, but the main window normally contains these areas:

Toolbar: actions such as reload, mark upgrades, apply changes, and search.
Search control: finds packages by name, description, or other selected fields.
Category or filter pane: narrows the package list by installation state, section, origin, upgrade availability, or custom criteria.
Package list: displays matching packages and their status indicators.
Detail pane: shows descriptions, versions, dependencies, repository information, and other package data.
Pending-changes area: summarizes actions that have been marked but not yet applied.

Viewing a package does not change it. Marking a package queues an installation, upgrade, removal, or related action. Those actions remain pending until you review and choose Apply.

Common package states

State	Meaning	Typical next action
Not installed	The package is available but absent.	Inspect it or mark it for installation.
Installed	The package is currently installed.	Inspect, upgrade, remove, or purge it.
Installed and upgradable	A newer candidate version is available.	Review and mark the upgrade.
Marked for installation	Installation is queued but has not occurred.	Review dependencies or unmark it.
Marked for removal	Removal is queued but has not occurred.	Review affected packages or cancel it.
Broken or dependency issue	Current package requirements cannot be satisfied.	Inspect the conflict and consider dependency repair.

Finding packages

Use the search control to search by an exact package name, partial name, description, or keyword. A program's menu name is not always its package name. Searching for a broader term can reveal the correct package, a replacement package, a transitional package, or related libraries.

Use filters to narrow results by installation state, upgrade availability, repository origin, section, or custom criteria when your version of Synaptic provides them. Before marking a similarly named package, inspect its:

Full package name and description.
Installed version and candidate version.
Maintainer information.
Repository origin and distribution release.
CPU architecture.
Dependencies and related packages.

Installing software with Synaptic

Open Synaptic and authenticate.
Choose Reload if package information may be outdated.
Search for the intended package, such as gimp.
Inspect its description, version, architecture, and repository origin.
Mark the package for installation.
Review the dependency prompt. An application may require libraries, themes, data files, or other supporting packages.
Review the complete pending transaction, including additions, upgrades, removals, and disk-space effects.
Choose Apply and wait for the transaction to finish.
Confirm success in the completion dialog, then launch the application from the desktop menu or its normal command.

Marking a package does not install it immediately. You can cancel a pending action by unmarking the package or clearing the queued changes before applying them.

Synaptic actions and their effects

Action	What changes	When to use it	Important caution
Mark for Installation	Queues a package and required dependencies.	When adding software.	Review all newly selected packages.
Mark for Upgrade	Queues a newer available version.	When an installed package has an update.	Check dependency adjustments.
Mark for Removal	Queues removal of package files while normally retaining system configuration.	When uninstalling but possibly retaining settings.	Inspect dependent packages.
Mark for Complete Removal	Queues removal of package files and system-level configuration.	When a package and its configuration should be purged.	User files in a home directory may remain.
Reload	Downloads current package indexes.	Before searching or checking updates.	Repository errors must be corrected first.
Mark All Upgrades	Queues available package upgrades.	For routine system maintenance.	Review additions and removals.
Fix Broken Packages	Asks the resolver to correct unsatisfied dependencies.	After an interrupted or inconsistent operation.	Never accept unexplained essential-package removals.
Apply	Commits the complete queued transaction.	After reviewing all changes.	Do not power off or close Synaptic during the transaction.

Inspecting package information

Open a package's properties or details view to examine what it is and what it needs. Important fields include the installed version, candidate version, description, maintainer, architecture, repository source, dependencies, reverse dependencies, and installed files where available.

A dependency is a package required by another package. A reverse dependency is a package that depends on the package being inspected. Reviewing reverse dependencies is especially important before removal: a library that appears unimportant may be required by many applications.

The installed version is the version currently on the system. The candidate version is the version APT currently prefers based on repository priorities and package rules. A package can therefore be installed while also being available for upgrade.

Distinguish an application from its libraries, documentation packages, development packages, and meta-packages. Removing a meta-package can remove the marker that keeps a desktop environment or software collection complete, even though many of its dependencies may initially remain installed.

Example: inspect `curl` before changing it

Search for curl.
Open its properties or details view.
Record its installed and candidate versions.
Read its description and repository source.
Inspect dependencies to see what it requires.
Inspect reverse dependencies to understand which packages may be affected by removal or version changes.

Removing and purging software

Mark an installed application for normal removal when its program files should be uninstalled but its system-wide configuration should normally remain. Retaining configuration can make a later reinstall preserve previous system settings.

Choose complete removal, also called purge, when the package and its associated system-level configuration files should be removed. A purge does not necessarily delete user-specific files in a home directory, such as personal settings or documents.

Operation	Program files	System configuration files	User home-directory data	Typical use case
Removal	Removed	Normally retained	Normally retained	Uninstall while preserving settings.
Complete removal or purge	Removed	Removed	May remain	Clean out system package configuration.

Shared dependencies are not necessarily removed when an application is removed. If another installed package still needs them, APT generally keeps them. Always inspect proposed removals, especially when the list includes a desktop environment, kernel, essential component, or meta-package.

Refreshing information and upgrading

Choose Reload before searching for newly published software or updates. Reloading downloads repository metadata; it does not upgrade installed packages.

Reload package information.
Use the upgrade-marking action to select available updates.
Review additions, removals, version changes, held packages, and disk-space requirements.
Accept dependency adjustments only when their purpose is clear.
Apply the transaction and read the completion output for errors.

A routine upgrade replaces installed packages with newer versions without making major dependency changes. A dependency-aware or “smart” upgrade may add or remove packages to resolve relationships. That broader operation requires especially careful review.

A reboot may be needed after updates affecting the kernel, graphical stack, init system, or core libraries. If an upgrade ends incompletely, complete pending configuration and repair dependencies before starting another large operation.

Repositories and software sources

APT source configuration determines which packages and versions Synaptic can display. Common source categories include distribution repositories, security updates, regular updates, optional components, and third-party repositories.

Source definitions are commonly stored in:

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

Changing a source affects the entire package system, not merely one application. Use official distribution repositories whenever possible. For third-party sources, check trust, signing keys, release compatibility, and whether the source supports the exact distribution release and architecture you use.

Do not casually mix repositories intended for different distribution releases. Incompatible sources can expose conflicting versions, create unmet dependencies, or cause an upgrade to propose removing large parts of the desktop. After changing sources, reload package information and inspect package origins before applying changes.

Broken packages and dependency repair

A broken package is in a state where its dependency requirements cannot currently be satisfied. Common causes include an interrupted installation, incompatible repositories, held packages, conflicting versions, and a partial upgrade.

Read the broken-package warning and inspect the dependency details.
Run Synaptic's Fix Broken Packages operation.
Review every proposed installation, upgrade, and removal.
Apply the repair only if the resolution makes sense.
If Synaptic cannot finish, use terminal-based APT and dpkg recovery.

Do not accept a proposed fix merely because it removes the error. Stop if it removes essential packages, a kernel, or a desktop environment without an understood reason.

Command-line recovery

dpkg is the lower-level tool that installs and records individual Debian-format packages. If configuration was interrupted, complete pending configuration with:

sudo dpkg --configure -a

Then ask APT to correct dependency problems:

sudo apt --fix-broken install

Review the proposed transaction, particularly any removals. Return to Synaptic only after the package system is consistent.

Troubleshooting common problems

Another package manager is running

A package lock prevents simultaneous APT or dpkg operations. Wait for a legitimate terminal command, software updater, or background operation to finish. Identify active package-management processes before taking action, and do not delete lock files as a first response. If no package process is active, use configuration repair only when appropriate.

Reload cannot download package lists

Check network connectivity and read the exact error. A failing source may have an incorrect address, an unsupported distribution release, a DNS or proxy problem, or a signing-key/authentication issue. Correct or disable the failing third-party source, confirm that sources match the installed release, and reload again.

Unmet dependencies prevent installation

Inspect the dependency conflict for partial upgrades, mixed repositories, conflicting versions, or held packages. Try the graphical repair option, or use sudo apt --fix-broken install and sudo dpkg --configure -a when appropriate. Avoid forcing installation outside the normal dependency resolver.

An upgrade proposes removing many packages

Stop rather than applying immediately. Check repository origins, release compatibility, changed dependency relationships, and whether a meta-package is being removed. If essential or desktop packages are listed, restore correct source configuration before retrying.

A package is missing from search results

Reload package information, search by broader keywords or descriptions, and check enabled repository components. The application name may differ from the package name, or the package may be unavailable for the current release or architecture.

An application remains partially configured

An interrupted installation or failed maintainer script may have left configuration incomplete. Do not start a competing Synaptic operation. Run sudo dpkg --configure -a, then use APT dependency repair, and return to Synaptic after the package state is consistent.

Safe operating practices

Refresh package lists before major changes.
Read the complete transaction summary every time before applying changes.
Avoid removing packages marked essential.
Do not remove a desktop meta-package without understanding the resulting dependency changes.
Prefer official distribution repositories.
Back up important data before a large upgrade, repository migration, or dependency repair.
Do not close Synaptic, log out, or power off while an APT transaction is in progress.
Do not run Synaptic concurrently with another package tool.

Graphical tasks and APT equivalents

Synaptic task	Typical terminal equivalent	Notes
Install Synaptic	`sudo apt-get install synaptic`	Requires working repositories and administrator privileges.
Refresh package lists	`sudo apt update`	Corresponds to Reload.
Install a package	`sudo apt install <package-name>`	Use the exact package name identified in Synaptic.
Upgrade packages	`sudo apt upgrade`	Review additions, removals, and held packages.
Remove a package	`sudo apt remove <package-name>`	Normally leaves system configuration files.
Purge a package	`sudo apt purge <package-name>`	Removes package files and system-level configuration.
Repair unfinished or broken configuration	`sudo dpkg --configure -a` `sudo apt --fix-broken install`	Use only after confirming no other package process is active.

Summary

Synaptic gives APT a visual interface, but it does not remove the underlying dependency and repository risks. Reload metadata before searching, inspect package details and origins, mark changes deliberately, review the entire transaction, and apply it only when additions and removals are understood. For serious dependency problems, Synaptic can help diagnose and repair the state, while APT and dpkg provide useful recovery tools.

For related command-line concepts, see Linux, showing the full path of shell commands, and the Linux file structure.