TeamViewer provides remote access and control software that lets you connect to computers and servers from anywhere in the world. Common use cases include providing IT support to colleagues or family members, accessing your home computer from work, transferring files between machines, and hosting online meetings. By the end of this guide, you will have TeamViewer installed on Ubuntu with automatic updates configured, ready to establish secure remote connections.
This guide covers two installation methods: the simplified extrepo approach that handles repository management automatically, and the manual setup for users who prefer direct control over their system configuration. Both methods connect to TeamViewer’s official repository, ensuring you receive updates alongside your regular system maintenance.
Choose Your TeamViewer Installation Method
Ubuntu provides two paths for installing TeamViewer from the official repository. The following table compares both approaches to help you decide which one fits your workflow.
| Method | Channel | Version | Updates | Best For |
|---|---|---|---|---|
| Extrepo | TeamViewer Repository | Latest stable | Automatic via APT | Most users who want quick setup with automatic cleanup |
| Manual Repository | TeamViewer Repository | Latest stable | Automatic via APT | Users who prefer explicit control over GPG keys and sources |
For most users, extrepo is recommended because it handles repository configuration, GPG key management, and cleanup automatically. The manual method provides identical software versions but requires more steps.
These steps cover Ubuntu 22.04 LTS, 24.04 LTS, and 26.04 LTS. The TeamViewer repository uses a universal package format that works across all current Ubuntu releases. Commands are identical across supported LTS versions.
Update Ubuntu Before TeamViewer Installation
Before installing any new software, start by updating your package lists and upgrading existing packages. This step ensures you have the latest security patches and helps prevent dependency conflicts during installation.
sudo apt update && sudo apt upgrade
Once the upgrade completes, you can proceed with either installation method below.
Method 1: Install TeamViewer via Extrepo (Recommended)
Extrepo is a tool that simplifies external repository management by handling GPG keys and source configuration automatically. As a result, this method requires fewer commands and provides clean removal when you no longer need the software.
Install Extrepo
To begin, install extrepo from Ubuntu’s Universe repository if it is not already present on your system:
sudo apt install extrepo
Enable Non-Free Policy
Because TeamViewer is proprietary software, you need to enable the non-free policy in extrepo’s configuration before adding the repository. You can do this manually or with a single command.
Option A: Automated command
Run this sed command to enable the non-free policy automatically:
sudo sed -i 's/^# - non-free$/- non-free/' /etc/extrepo/config.yaml
Option B: Manual editing
Alternatively, open the configuration file in a text editor:
sudo nano /etc/extrepo/config.yaml
Find the enabled_policies section and uncomment the non-free line by removing the # symbol. The section should look like this after editing:
enabled_policies:
- main
# - contrib
- non-free
Save the file and exit the editor (in nano, press Ctrl+O to save, then Ctrl+X to exit).
Enable TeamViewer Repository
With the non-free policy enabled, add the TeamViewer repository to your system:
sudo extrepo enable teamviewer_default
This command downloads the GPG key and creates a properly configured DEB822 sources file at /etc/apt/sources.list.d/extrepo_teamviewer_default.sources.
Install TeamViewer
Now update your package lists to include the new repository, then install TeamViewer:
sudo apt update
sudo apt install teamviewer
During installation, APT pulls in several dependencies required for the graphical interface. When prompted, confirm the installation to proceed.
Verify Installation
After installation, confirm TeamViewer installed correctly by checking the package status:
apt-cache policy teamviewer
Expected output showing the installed version:
teamviewer:
Installed: 15.73.5
Candidate: 15.73.5
Version table:
*** 15.73.5 500
500 http://linux.teamviewer.com/deb stable/main amd64 Packages
100 /var/lib/dpkg/status
A version number in the “Installed” field confirms TeamViewer is ready to use.
Method 2: Install TeamViewer via Manual Repository Setup
This method gives you explicit control over the GPG key location and repository configuration. While it requires more commands, the approach provides full transparency about exactly which files are added to your system.
Import TeamViewer GPG Key
First, download and convert the TeamViewer signing key to the binary format that APT expects. This key verifies that packages genuinely come from TeamViewer:
curl -fsSL https://linux.teamviewer.com/pubkey/currentkey.asc | sudo gpg --dearmor -o /usr/share/keyrings/teamviewer.gpg
This single command downloads the ASCII-armored key, converts it to binary format, and saves it directly to the keyrings directory with proper ownership.
Add TeamViewer Repository
Next, create a DEB822 format sources file that points to the TeamViewer repository. This modern format is more readable and less error-prone than the legacy one-line format:
cat <<EOF | sudo tee /etc/apt/sources.list.d/teamviewer.sources
Types: deb
URIs: http://linux.teamviewer.com/deb
Suites: stable
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/teamviewer.gpg
EOF
The Signed-By field links this repository to the GPG key you imported, ensuring only properly signed packages are accepted.
Install TeamViewer
Update your package lists to include the new repository, then install TeamViewer:
sudo apt update
sudo apt install teamviewer
The TeamViewer package automatically adds its own
teamviewer.listfile during installation, which duplicates your DEB822 configuration. To avoid conflicts, remove this legacy file after installation completes:
sudo rm /etc/apt/sources.list.d/teamviewer.list
This keeps only your modern DEB822 sources file and prevents APT from warning about duplicate repository entries.
Verify Installation
Finally, confirm TeamViewer installed correctly by checking the package status:
apt-cache policy teamviewer
The output should show an installed version from the TeamViewer repository, confirming the setup succeeded.
Launch TeamViewer
Once installation completes, you can launch TeamViewer through either the graphical interface or the terminal.
Launch from Applications Menu
For desktop users, the most convenient method is launching TeamViewer from the applications menu. Navigate to:
Activities → Show Applications → TeamViewer
When TeamViewer opens, it displays your ID and a temporary password that remote users need to connect to your machine.

Launch from Terminal
Alternatively, launch TeamViewer from any terminal by running:
teamviewer
This opens the same graphical interface. The terminal method is useful when you’re already working in a terminal session or need to launch TeamViewer from a script.
Manage TeamViewer from Terminal
In addition to the graphical interface, TeamViewer provides command-line tools for managing the daemon and configuring unattended access. These commands are particularly useful for headless servers or when configuring TeamViewer over SSH.
View Available Commands
To see all available TeamViewer command-line options, run:
teamviewer help
This lists commands for daemon management, password configuration, and account assignment.
Check TeamViewer Status
To view your TeamViewer ID and daemon status without opening the graphical interface, use:
teamviewer info
This command displays whether the daemon is running and shows the TeamViewer ID that remote users need to connect.
Configure Unattended Access
If you need to access servers or machines without someone physically present, you can set a permanent password:
sudo teamviewer passwd your-secure-password
Replace your-secure-password with a strong password. This password persists across reboots, unlike the temporary password shown in the GUI.
Manage the TeamViewer Daemon
You can control the background service that enables remote connections using these commands:
# Start the daemon
sudo teamviewer daemon start
# Stop the daemon
sudo teamviewer daemon stop
# Restart the daemon
sudo teamviewer daemon restart
The daemon must be running for remote users to connect to your machine.
Assign Device to TeamViewer Account
To link your machine to a TeamViewer account for easier management and access without remembering the ID, run:
teamviewer setup
Then follow the prompts to sign in to your TeamViewer account. Once assigned, you can access this machine from your account’s device list.
Update TeamViewer
Since the TeamViewer repository is now configured, updates arrive automatically when you run your regular system updates:
sudo apt update && sudo apt upgrade
If you want to update only TeamViewer without upgrading other packages, use the --only-upgrade flag:
sudo apt install --only-upgrade teamviewer
This command installs the latest TeamViewer version if one is available, while leaving other packages untouched.
Remove TeamViewer
If you no longer need TeamViewer, you can remove the package and clean up the repository configuration. Note that the removal steps differ slightly depending on which installation method you used.
Remove TeamViewer Package
To uninstall TeamViewer and remove its configuration files:
sudo apt remove --purge teamviewer
Afterwards, remove any orphaned dependencies that were installed alongside TeamViewer:
sudo apt autoremove
Remove Repository (Extrepo Method)
If you installed via extrepo, disable the repository:
sudo extrepo disable teamviewer_default
Extrepo marks the repository as disabled by adding Enabled: no to the sources file. For complete removal, delete the sources file and refresh your package cache:
sudo rm /etc/apt/sources.list.d/extrepo_teamviewer_default.sources
sudo apt update
Remove Repository (Manual Method)
If you installed via the manual method, remove the sources file:
sudo rm /etc/apt/sources.list.d/teamviewer.sources
Then remove the GPG key:
sudo rm /usr/share/keyrings/teamviewer.gpg
Finally, update your package lists to reflect the removed repository:
sudo apt update
Troubleshooting
This section covers common issues users encounter when installing or running TeamViewer on Ubuntu.
TeamViewer Daemon Not Starting
If remote connections fail, first check whether the daemon is running:
teamviewer info
If the daemon shows as stopped, start it manually:
sudo teamviewer daemon start
No TeamViewer ID Displayed
When TeamViewer opens but shows no ID, the daemon may need restarting:
sudo teamviewer daemon restart
Then wait a few seconds for the ID to populate. Network connectivity issues can also delay ID assignment.
Repository Conflict Errors
If you see errors about conflicting Signed-By values during apt update, you may have both extrepo and manual repository configurations present. Check for duplicate entries:
ls /etc/apt/sources.list.d/ | grep -i teamviewer
Remove the duplicate configuration you don’t want to keep, then run sudo apt update again.
Additional Resources
For related remote access and system management guides, see:
- Install AnyDesk on Ubuntu, an alternative remote desktop application with similar features
- Install Remmina on Ubuntu, an open-source remote desktop client supporting multiple protocols
- Install SSH on Ubuntu for secure shell access and terminal-based remote management
- Configure UFW Firewall on Ubuntu to set up firewall rules and secure remote connections
Conclusion
You now have TeamViewer installed on Ubuntu with the official repository configured for automatic updates. The extrepo method provides the simplest setup, while the manual approach offers transparency for users who prefer explicit control. With the daemon running, you can establish remote connections, provide technical support, or access your machines from anywhere.
No work on 6.1.60-antix.1-amd64 🙁 frozen field ID and login options :/
Hi jano,
I have not tested these installations methods on antiX Linux. Given the nature of that Distro, it could be due to dependencies missing.