How to Install TeamViewer on Fedora 44

Remote support on Fedora works best when the desktop client, background daemon, and update source all come from the same vendor package. To install TeamViewer on Fedora, use TeamViewer’s official RPM, verify its signature, and let the package add the DNF repository it needs for future updates.

The current TeamViewer RPM installs cleanly on Fedora 44 with DNF5, but TeamViewer’s vendor support matrix can lag Fedora’s fast release cadence. Check TeamViewer’s supported operating systems page if you need vendor-backed support for business-critical incoming access, especially on Wayland desktops.

Install TeamViewer on Fedora Linux

Confirm the TeamViewer RPM Source on Fedora

TeamViewer publishes Fedora-compatible RPM downloads from its Linux download page. The RPM is the bootstrap package: after installation, it places the TeamViewer repository file under /etc/yum.repos.d/ so DNF can manage updates on supported architectures.

Package Path	Status	Update Behavior
Official x86_64 RPM	Recommended for most Fedora desktop systems	Adds the TeamViewer DNF repository and updates with DNF
Official aarch64 RPM	Available from TeamViewer’s download endpoint	Use the direct RPM workflow; current aarch64 repository metadata may return 403
Flatpak or Flathub	No official TeamViewer Flathub app was found during review	Use the official RPM instead of unofficial wrappers

Use TeamViewer’s Linux download page to confirm current package availability before deploying the client at scale.

Update Fedora Before Installing TeamViewer

Refresh Fedora’s package metadata and apply pending updates before installing the vendor RPM:

sudo dnf upgrade --refresh

Review the transaction before confirming. If the update includes a new kernel or graphics stack, reboot first so TeamViewer starts against the same desktop session and libraries you will actually use.

Import the TeamViewer RPM Signing Key

Import TeamViewer’s public signing key before checking the downloaded RPM. This lets rpm --checksig verify the package instead of reporting an unknown key:

sudo rpm --import https://linux.teamviewer.com/pubkey/currentkey.asc

Download the TeamViewer RPM on Fedora

Check your Fedora architecture before downloading the RPM:

uname -m

Most Fedora desktop systems return x86_64. ARM64 systems return aarch64:

x86_64

Download the matching RPM. The -f flag makes curl fail on HTTP errors, while -L follows TeamViewer’s redirect to the current versioned RPM:

arch=$(uname -m)
case "$arch" in
  x86_64|aarch64)
    curl -fL -o teamviewer.rpm "https://download.teamviewer.com/download/linux/teamviewer.${arch}.rpm"
    ;;
  *)
    printf 'TeamViewer RPM is not available for %s\n' "$arch" >&2
    exit 1
    ;;
esac

Verify and Install the TeamViewer RPM

Verify the downloaded RPM signature before installing it:

rpm --checksig teamviewer.rpm

A valid package returns:

teamviewer.rpm: digests signatures OK

Install the RPM with DNF so Fedora resolves package dependencies from enabled repositories:

sudo dnf install ./teamviewer.rpm

DNF5 may still print a warning that OpenPGP checks were skipped for the local @commandline package. The earlier rpm --checksig command is the signature proof for the downloaded RPM.

Verify TeamViewer Installation on Fedora

Confirm the package, repository file, and background daemon are present:

rpm -q --queryformat '%{NAME}\n' teamviewer
test -f /etc/yum.repos.d/teamviewer.repo && echo "TeamViewer DNF repository installed"
systemctl is-active teamviewerd

Expected output:

teamviewer
TeamViewer DNF repository installed
active

Remove the downloaded installer after the package is installed:

rm -f teamviewer.rpm

Launch TeamViewer on Fedora Linux

Launch TeamViewer from Fedora Activities

Open Activities, search for TeamViewer, and select the TeamViewer launcher. The first launch displays your TeamViewer ID and temporary password for attended support, plus sign-in and unattended access options for managed devices.

Launch TeamViewer from Terminal

Terminal launch is useful when you want to see startup messages while troubleshooting:

teamviewer

The command starts the graphical client in your active desktop session. A normal SSH-only shell is not a substitute for a local graphical session.

Manage TeamViewer on Fedora Linux

Update TeamViewer on Fedora

On x86_64 Fedora systems, the RPM installs the TeamViewer repository, so DNF can update the client with the rest of your packages:

sudo dnf upgrade --refresh teamviewer

If you installed the aarch64 RPM and DNF reports a repository metadata error, repeat the download, signature check, and install workflow to update manually until TeamViewer publishes working aarch64 repository metadata.

Check the TeamViewer Daemon on Fedora

TeamViewer uses the teamviewerd systemd service for connection readiness and unattended access. Check both active and enabled state:

systemctl is-active teamviewerd
systemctl is-enabled teamviewerd

A normal installed state returns:

active
enabled

Start and enable the daemon if it is inactive or disabled:

sudo systemctl enable --now teamviewerd

Remove TeamViewer from Fedora Linux

Remove the TeamViewer Package on Fedora

Uninstall the TeamViewer RPM with DNF:

sudo dnf remove teamviewer

DNF removes the TeamViewer package, the service unit, the repository file, and unused dependencies from the same transaction. A separate dnf autoremove step is not needed for the normal TeamViewer removal path.

Verify the package and repository file are gone:

rpm -q teamviewer || echo "teamviewer removed"
test ! -e /etc/yum.repos.d/teamviewer.repo && echo "TeamViewer repository file removed"

Expected output:

package teamviewer is not installed
teamviewer removed
TeamViewer repository file removed

Remove Leftover TeamViewer Configuration and Logs

The RPM removal leaves system configuration and log directories behind. Check them before deciding whether you need a full local cleanup:

ls -ld /etc/teamviewer /var/log/teamviewer15 2>/dev/null || echo "No TeamViewer system leftovers found"

The next command permanently deletes TeamViewer’s system configuration and logs. Save any diagnostics or deployment settings you still need before running it.

sudo rm -rf /etc/teamviewer /var/log/teamviewer15

If you launched the graphical client and want to remove per-user TeamViewer state, delete only paths that exist in your account:

The next command removes local TeamViewer settings for your Linux user account. Do not run it if you want to keep saved connections or local client preferences.

for path in "$HOME/.config/teamviewer" "$HOME/.cache/teamviewer" "$HOME/.local/share/teamviewer"; do
  [ -e "$path" ] && rm -rf "$path"
done

Troubleshoot TeamViewer on Fedora Linux

TeamViewer Shows “Not Ready” on Fedora

If TeamViewer opens but reports that it is not ready, check the daemon first:

systemctl is-active teamviewerd

An inactive daemon returns:

inactive

Start the daemon, then reopen TeamViewer:

sudo systemctl enable --now teamviewerd
systemctl is-active teamviewerd

The second command should return:

active

DNF Reports a TeamViewer Repository 403 Error

The aarch64 RPM currently installs the same repository profile as x86_64, but TeamViewer’s aarch64 repository metadata may return a 403 error during DNF refreshes. Relevant output includes:

Status code: 403 for https://linux.teamviewer.com/yum/stable/main/binary-aarch64/repodata/repomd.xml

If that happens, disable the TeamViewer repository and update by re-downloading the aarch64 RPM from TeamViewer’s download endpoint:

sudo dnf config-manager setopt teamviewer.enabled=0

DNF5 stores this change as a repository override, so the package-owned /etc/yum.repos.d/teamviewer.repo file may still show enabled=1. DNF will use the override.

If config-manager is missing while the broken TeamViewer repository is still enabled, install the DNF5 plugin package with that repository disabled for this transaction:

sudo dnf --disablerepo=teamviewer install dnf5-plugins

Then rerun the dnf config-manager setopt command and use the manual RPM download workflow for future aarch64 updates until TeamViewer publishes working aarch64 repository metadata.

Incoming Connections Fail on Fedora Wayland

Fedora GNOME uses Wayland by default, and TeamViewer’s support page still treats Wayland incoming connections as experimental. If incoming control or screen sharing fails while outgoing sessions work, first confirm your session type:

echo "$XDG_SESSION_TYPE"

On Wayland sessions, check TeamViewer’s current in-app prompts and Fedora’s desktop privacy settings before changing system packages. If your desktop environment still offers an X11 session, using that session can be more reliable for incoming unattended access until TeamViewer marks Wayland support as fully supported.

Conclusion

TeamViewer is installed on Fedora with the official RPM, verified package signatures, the background daemon, and DNF-managed updates where TeamViewer publishes repository metadata. If you need RDP or VNC alongside TeamViewer sessions, install Remmina on Fedora; if you want another vendor remote-support client, install AnyDesk on Fedora.