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

broken since today on archlinux

Thx to huupoke12 DNSSEC=false in /etc/systemd/resolved.conf resolves the connection issues

@siyia No, it's because of bad DNSSEC record, not DNSOverTLS. See my previous comment. No need to disable systemd-resolved and DNS Over TLS, setting DNSSEC=false in the config will make it work again.

DNSOverTLS causes network errors with teamviewer, temporarily stop systemd-resolved service if you need to use it

hmm.... Teamviewer - previous versions of this package I'm using now "aur/teamviewer 15.5.6-1" has been working for years, but now things from 15.5.6-1 just stopped working, just after upgrading my system... It just says:

$ teamviewer 
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...

And nothing happens...

"systemctl status teamviewerd" says "teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet..". I recently switched to sway (wayland) - but I also tried gnome... I also found that the "~/.local/share/teamviewer15/logfiles/TeamViewer15_Logfile.log" contains some info, several errors - among these:

2020/05/27 21:40:11.092 24033 139947291594048 G!! MonitorInfo: WorkingArea: Property error 14 (0), Errorcode=13
2020/05/27 21:40:11.095 24033 139947291594048 G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=13
2020/05/27 21:40:11.098 24033 139947291594048 G!! StorageTextfile: Unable to open configuration file '/opt/teamviewer/config/global.conf' (RO), Errorcode=13
2020/05/27 21:40:11.101 24033 139947291594048 G!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version () is not matching with application version (15.5.6)

Pretty annoying; By the way, I discovered that as root you probably need to edit /usr/lib/systemd/system/teamviewerd.service (change /var/run/teamviewerd.pid → /run/teamviewerd.pid). But I couldn't make it work (the /var/run just fixes one of several issues I think)... Damn! I think the conclusion is that the file "/opt/teamviewer/tv_bin/resources/TVResource_en.so" has a wrong version. If anyone know the solution, that would be greatly appreciated, thanks!

UPDATE: Annoying problem solved with "systemctl enable gdm" and rebooting (for some reason doesn't work with startx).

The PKGBUILD should source from dl.teamviewer.com instead of dl.tvcdn.de since teamviewer.com is the canonical TeamViewer domain and would allow to directly verify the authenticity of the Debian packages.

If you want to update the package before it's updated in AUR, you can use this script:

#!/bin/bash

# Set this to updated version
# and run the script.
_newver=15.5.3

_oldver=$(grep "pkgver=" PKGBUILD | grep -o '[0-9.]*')

if [[ "$_oldver" == "$_newver" ]]; then 
    echo "Nothing to do."
    exit 0
fi

echo "Updating..."
sed -i "s|^pkgver=.*$|pkgver=${_newver}|" PKGBUILD
updpkgsums
makepkg --printsrcinfo > .SRCINFO

The package installation does say:

The Teamviewer daemon must be running for Teamviewer to work.
Execute 'sudo systemctl enable teamviewerd' in a terminal.

But nobody seems to read it. I suggested a fix for it earlier, among automatic update script and other improvements, here is the updated patch: https://pastebin.com/UgHp4u3S

Hi all, just a heads up. If you're having trouble with starting team viewer (connections unavailable), just start the daemon first

$ sudo systemctl start teamviewerd

Make sure to enable on start.

Hello to all follow xsession guys. I have the same problem using ly session manager and sway WM. Some additional details: logs are available in ~/.local/share/teamviewer15/logfiles/. Most relevant one is TeamViewer15_Logfile.log which contains a bunch of the following errors:

2020/04/26 21:36:28.840 52749 140543546674496 G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11

I thought it might be related to SESSION_MANAGER env variable and tried to run it from under xsm which does set that variable, but it did not change anything.

TeamViewer 12 works for me, but it does not support newer protocol version.