Package Details: teamviewer 14.6.2452-1

Git Clone URL: (read-only)
Package Base: teamviewer
Description: All-In-One Software for Remote Support and Online Meetings
Upstream URL:
Licenses: custom
Conflicts: teamviewer-beta
Provides: teamviewer
Submitter: Hilinus
Maintainer: swiftgeek (nickoe, astronautlevel)
Last Packager: swiftgeek
Votes: 1336
Popularity: 6.53
First Submitted: 2010-04-15 10:29
Last Updated: 2019-10-01 11:09

Pinned Comments

swiftgeek commented on 2018-10-26 07:34

Go to teamviewer-beta for beta/preview releases

(unless teamviewer messes it up again like with 12->13, where 12 was abandoned)

seenxu commented on 2018-04-05 08:27

seenxu commented on 2018-04-05 07:26


teamviewer 13 requires a desktop environment or login with lightdm etc, with startx it won't work, the staff of teamviewer confirmed, startx feature won't come in this year, it seems reverting back to teamviewer 12 is the only option for startx folks.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

Elrondo46 commented on 2018-11-16 07:00

For auto service at start you can do that:

xnopasaranx commented on 2018-11-15 14:10

I was having massive problems with the package (I am using i3wm). It would install and update no problem but suddenly I was not able to log in anymore with our company account. The credentials fields were greyed out, but no connection problems were reported. Today I stumbled upon a stackoverflow that suggested installing libnss-resolver and that fixed my problem immediately after restarting the teamviewerd service. Could this be made a recommendation/dependency or maybe included as a troubleshooting tipp?

swiftgeek commented on 2018-10-26 07:34

Go to teamviewer-beta for beta/preview releases

(unless teamviewer messes it up again like with 12->13, where 12 was abandoned)

closingin commented on 2018-10-25 10:36

Hello, I don't understand why you recommend in the install script to enable the teamviewerd service at boot when it just has to be running for teamviewer to work. That's not really a problem as it's just a recommendation, but I think you should change the command to "sudo systemctl start teamviewerd.service" instead of "enable", to stay consistent with the associated message.

FFY00 commented on 2018-10-24 21:57

Please remove the conflicts with teamviewer-beta, that package should be the one conflicting with this one.

DuBistKomisch commented on 2018-10-18 00:12

+1 to xuanwo's comment, I don't have NetworkManager installed so I can't start the teamviewerd service at all without editing it

requiring lightdm was bad enough, hopefully we don't need to start installing NetworkMangler too!

z3ntu commented on 2018-10-17 20:38

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

swiftgeek commented on 2018-10-17 14:05

13.2.26559 is first nonpreview version

xuanwo commented on 2018-10-17 08:34

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] dbus.service

GeorgeRaven commented on 2018-10-15 15:41

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.