Package Details: teamviewer 12.0.71510-6

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: 1173
Popularity: 15.720305
First Submitted: 2010-04-15 10:29
Last Updated: 2016-12-06 22:07

Latest Comments

WFV commented on 2017-02-14 04:51

The GUI auto start option worked sometimes but mostly not, back to square one, can't get it to connect no matter what again after -Syu.

Rigoberto commented on 2017-02-10 01:48

en español: lo lamento no tengo tiempo para pensar en ingles:

la solución de emergencia es wine y describiré tal cual me funciono:
1) descargar teamviewer12.exe
2) instalarla con playonlinux
2.1) que playonlinux cree un nuevo disco virtual-wine (32 bit win10)
2.2) hacer la instalación propiamente tal, pero al finalizar, no colocar ningún enlace en el escritorio porque no servirá.
3) ir a ../.PlayOnLinux/wineprefix/teamviewer(nombre del disco virtual)/drive_c/Program Files/TeamViewer y abrir con wine TeamViewer.exe

tal vez lo que comento es tonto, pero lo intente instalar de 50 maneras distintas y puede que para alguien sea un menester de emergencia (indique la forma exacta en que lo hice pero tuve errores en varios intentos (versiones anteriores entorno xp 64 bits etc., tiene que ser teamviewer12 instalarlo en una arquitectura de 32 bits y para win 10). saludos muy cordiales.

shieldwed commented on 2017-02-08 21:18

@logion i tried creating a PKGBUILD from the tar ball. see

in this package the file "" is missing, but i think this might be ok due to the dependency to lib32-libpng12.

This PKGBUILD is not quite finished since starting teamviewer from a terminal window, it is faulting with:

/opt/teamviewer/tv_bin/script/tvw_exec: line 9: /opt/teamviewer/logfiles/startup.log: Permission denied

Error: LockStartup: internal error 1

maybe you got an idea?

logion commented on 2017-02-08 10:20

In regards to the "Not ready. Please check your connection" error in teamviewer. There is a thread on the TV forums detailing this issue (, some conclusions are as follows:
* Error shows up on wayland systems, but not an x server systems (I'm only running wayland, and also suffer from this issue under wayland; can't check with X server)
* Using the unsupported systems tar ball under wayland (, solves the connection issue. I can confirm this is the case and I can remote desktop to my Wintel machine at home from my arch wayland machine at the office.
* Under wayland remote users can not control the local machine, they see a black rectangle. Did not test this.

As for the PKGBUILD AUR file, for X server users there does not need to be any change. For those using wayland, I would suggest trying with the unsupported system tarball instead of the deb package files.

@nipsky: is the teamviewerd.service running (systemctl status teamviewerd.service)?

nipsky commented on 2017-02-08 08:26

Hi, teamviewer freezes on start for me before even showing any GUI, here’s the terminal output:

CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...

Am I the only one with this problem?

swiftgeek commented on 2017-02-07 00:46

@otrazhenije no one should try it, at most magically i386 build works better for you (x86_64 works very reliable here FYI)

Don't give ideas for bypassing package manager on AUR -.-

otrazhenije commented on 2017-02-06 09:38

Faced the same problem
Solved with:

1. Download
2. Extract
3. rsync to /opt/teamviewer, overwrite existing files

You should try

cubethethird commented on 2017-02-03 01:15

Link to relevant support thread:

Users with this issue describe 3 possible causes/solutions:
- Incorrect DNS lookups -> change DNS server/manual entries
- Error in service startup -> restart the service
- Usage of IPv6 -> disable IPv6 in router/modem settings

Sadly none of these solutions work for me, including the Remmina workaround recommended.

summonholmes commented on 2017-01-28 00:03

Regarding the connection errors of the previous comments, I've found a temporary workaround. Install Remmina, then install the TeamViewer plugin (AUR). If teamviewerd is active, Remmina will execute TeamViewer in a connected state. Hope this helps.

joanmanel commented on 2017-01-26 13:37

Hey purboo, what exactly did you do, because I executed that command, then open teamviewer, and I get the same error.

All comments