Package Details: teamviewer 15.76.5-1

Git Clone URL: https://aur.archlinux.org/teamviewer.git (read-only, click to copy)
Package Base: teamviewer
Description: All-In-One Software for Remote Support and Online Meetings
Upstream URL: https://www.teamviewer.com/en/download/portal/linux/
Licenses: custom
Conflicts: teamviewer-beta
Provides: teamviewer
Submitter: Hilinus
Maintainer: swiftgeek (nickoe, astronautlevel)
Last Packager: swiftgeek
Votes: 1484
Popularity: 1.44
First Submitted: 2010-04-15 10:29 (UTC)
Last Updated: 2026-05-11 17:35 (UTC)

Pinned Comments

swiftgeek commented on 2023-08-01 19:17 (UTC) (edited on 2023-08-01 19:21 (UTC) by swiftgeek)

As mentioned in @seyn6gk's comment

Without changing anything, since teamviewer 13 a desktop environment/login with display manager like lightdm/sddm/gdm is required.

startx users can follow workaround mentioned in @r7v s comment

r7v commented on 2022-06-07 14:49 (UTC)

Workaround for startx

Create drop-in /etc/systemd/system/getty@tty1.service.d/getty@tty1.service-drop-in.conf with

[Service]
Environment=XDG_SESSION_TYPE=x11

Source: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 129 Next › Last »

z3ntu commented on 2018-10-17 20:38 (UTC)

You should reset the pkgrel to 1 with the next pkgver bump

swiftgeek commented on 2018-10-17 14:05 (UTC)

https://community.teamviewer.com/t5/Linux/Update-13-2-13582-Summer-release/td-p/40607

13.2.26559 is first nonpreview version

xuanwo commented on 2018-10-17 08:34 (UTC) (edited on 2018-10-17 08:35 (UTC) by xuanwo)

teamviewerd's service will introduce NetworkManager-wait-online.service which results in systemd tried to start NetworkManager and netctl users had network issues after that.

In order to solve this problem, we should:

Firstly, mask network related service

systemctk mask NetworkManager-wait-online.service
systemctk mask NetworkManager-dispatcher.service
systemctk mask NetworkManager.service

Then edit the teamviewerd.service: systemctl edit teamviewerd.service

[Unit]
After=network.target network-online.target dbus.service
Wants=network-online.target

GeorgeRaven commented on 2018-10-15 15:41 (UTC)

I have found I require lib32-freetype2 archive package to start teamviewer on boot even after enabling teamviewd service using systemctl. The steps taken to get this to work on boot are those proposed by Telis80s answer. Although in the same thread it is suggested this is not necessary yet I have not found another working solution without these 32bit libs.

dschaefer79 commented on 2018-10-15 09:12 (UTC)

systemctl status teamviewerd.service

oct 15 09:17:58 revopc systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: No such file or directory

What can I do about this error ??

t0m5k1 commented on 2018-10-12 11:33 (UTC)

@Sven,

You don't have to enable the service just start it: systemctl start teamviewerd.service Then when you have finished run: systemctl stop teamviewerd.service

You only need to run the enable if you do want it running constantly in the background

svrmirac commented on 2018-10-12 09:36 (UTC)

Thanks @Sven!

Sven commented on 2018-10-12 01:00 (UTC) (edited on 2018-10-12 01:01 (UTC) by Sven)

Why do I have to enable teamviewerd.service? I don't want a teamviewer service running all the time. I want to use teamviewer solely as an app to remote control other machines. I want to use teamviewer as an app that I start and terminate whenever I please.

Currently, I download the official tgz, unpack it, and run the teamviewer executable. That's it. No systemd services, nothing running in the background.

swiftgeek commented on 2018-10-09 21:55 (UTC)

@tomacrisan while i apprieciate links i don't see a mention of it in https://community.teamviewer.com/t5/Linux/bd-p/Linux or download page

Perhaps teamviewer-beta would be better for such inside previews?

pezcurrel commented on 2018-10-08 15:19 (UTC) (edited on 2018-10-08 15:24 (UTC) by pezcurrel)

nx345 perhaps the window shows almost offscreen, with just the upper-left corner showing in the lower-right corner of the screen, like it happens to me on a notebook with hidpi screen - I have not this problem on a desktop pc with fhd screen. On the notebook I manage to bring the window to the center of screen by dragging the corner up and left to resize the window a bit and then grabbing the top bar and dragging the window to the center of the screen.