Package Details: teamviewer 12.0.76279-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: 1204
Popularity: 14.088601
First Submitted: 2010-04-15 10:29
Last Updated: 2017-04-13 01:48

Latest Comments

izznogooood commented on 2017-08-15 15:03

systemctl daemon-reload should be added to installer script.

Its not possible to start Teamviewer without the daemon and not possible to start the daemon with out a reload.

CybeX commented on 2017-08-02 19:45

Also have black screen when client connects. Arch x64 + Gnome XWayland.

`GNOME Shell 3.24.3`

Anyone have info on cause?

VenomAUR commented on 2017-06-21 16:29

Disregard my previous comment, they obviously statically compiled Qt into their executable.

VenomAUR commented on 2017-06-21 16:16

What are the GUI dependencies? I don't see any, at least not on the top level. TeamViewer for Linux was built using Qt, if I'm not mistaken?

bellissimo commented on 2017-06-19 17:13

Thank you for the pakage!

Black screen between two Lenovo X230 with current arch linux stable and gnome wayland. Gnome with Xorg works fine.

vromanch commented on 2017-06-16 01:24

Tried to connect to my machine from windows got black screen

cubethethird commented on 2017-06-06 01:16

Hadn't used this in a little while, but it now seems to work without issue while running Wayland on Gnome. Hopefully it stays that way.

napa3um commented on 2017-05-25 10:52

Bug: Ubuntu/Windows TeamViewer client connect to Arch TeamViewer server and see black screen.

maofree commented on 2017-05-24 14:29

I've the same problem of connection
and to use it I need to stop the service and then reactive it with
#systemctl stop teamviewerd.service
#systemctl start teamviewerd.service

the problem is present on my pc instead on my laptop it is ok

num1champ commented on 2017-05-18 07:30

@msifland it is weird that you have to do that, but i manually ran those cmds after login and that solves one of my issues. Where exactly are you executing your script? during boot? after login?

All comments