Arch Linux User Repository

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

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

I have an issue with the login into my account. When I try to login, I get an timeout and the error-message, that the server did not reply. I've found the following lines in teamviewers logfile: 2015/05/20 22:30:21.737 33 39 G1 Account::TryAutoLogin: enabled: 0 2015/05/20 22:30:26.868 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.869 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.869 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.870 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.870 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.870 33 46 G1 Timeout for master message. 2015/05/20 22:30:26.870 33 46 G1 Timeout for master message. 2015/05/20 22:30:37.039 33 34 G1 Account::SetNewLoginState: 3 2015/05/20 22:30:37.073 33 34 G1 AccountLogin::Start: Trying account authentication 2015/05/20 22:30:57.051 33 34 G1!! BuddyList: SignIn failed. (SignIn Timeout), Errorcode=5 2015/05/20 22:30:57.059 33 34 G1!! BuddyPageList.OnDestroy: RemoveMessageFilter failed 2015/05/20 22:31:07.087 33 34 G1!! AccountLogin::Error: Authentication failed with error 2 2015/05/20 22:31:07.088 33 34 G1 Account::SetNewLoginState: 2 Nevertheless, the program works when I try to connect to a diffrent machine with its id and password. Teamviewer used to work fine before, but I cannot say which system- or teamviewer-update caused the problems. I have a second machine (same DE: cinnamon 2.4 and gnome 3.16) with nearly identical setup, just different hardware where teanviewer is still running fine. Is there anybody who has a similar issue? Thanks. All the best, unclesam

I am getting the "PID file /var/run/teamviewerd.pid not readable (yet?) after start." other folks have had in the past - unfortunately, none of the fixes in this thread have worked out. I tried changing the permissions on the folder where the PID lives, and pointing the unit file to another directory. Any ideas?

Hi, I installed the latest version, I added the systemctl service but the app doesn't work for me. [isti@istiLaptop ~]$ systemctl --all | grep teamv teamviewerd.service loaded active running TeamViewer remote control daemon [isti@istiLaptop ~]$ teamviewer -h Init... Checking setup... Launching TeamViewer ... [isti@istiLaptop ~]$

Updated. Now all work perfect :)

new md5sum teamviewer_linux_x64-10.0.37742.deb fdbc27543e0955e217097810a7983507

Disabling wayland in GDM didnt work for me, but simply not using gdm did. I started my awesomewm with startx and teamviewer suddenly works again. Goddamn Gnome, not only breaks its own addons with every version but now it also breaks everything else..

Not working with GDM unless wayland is disabled in /etc/gdm/custom.conf

Report from TeamViewer support: "We got some news from our developers that this is unfortunately a known problem. But please note that the problem is related to Gnome itself. Our developers are already working on a solution and this will be fixed as soon as possible. We are really sorry about the inconvenience."

I have filed a bug with TeamViewer support. I will let you all know if this case gets resolved.

Anyone know what need to do? I have same problem with the new Gnome (3.16).