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

@seyn6gk regarding startx etc. not working, I'm pretty sure it's because TV looks for session type (loginctl session-status | grep Service:) and finds out its type is tty instead of x11 (or wayland).

Systemd v246 added support for changing session type "on the fly" (see how sway implements that), but I couldn't make it work with Activate -> TakeControl -> SetType using dbus-send and then startx (I always get only owner of the terminal can take control).

Feel free to try yourself as it should work.

  sudo dbus-send --system --print-reply --dest=org.freedesktop.login1 \
      /org/freedesktop/login1/session \
      org.freedesktop.DBus.Introspectable.Introspect |
      grep -E 'node name="_.*'

(use the session number in the subsequent dbus-send calls)

  dbus-send --system --print-reply --dest=org.freedesktop.login1 \
      /org/freedesktop/login1/session/_"$1" \
      org.freedesktop.login1.Session.Activate

  dbus-send --system --print-reply --dest=org.freedesktop.login1 \
      /org/freedesktop/login1/session/_"$1" \
      org.freedesktop.login1.Session.TakeControl boolean:true

  dbus-send --system --print-reply --dest=org.freedesktop.login1 \
      /org/freedesktop/login1/session/_"$1" \
      org.freedesktop.login1.Session.SetType string:x11

Don't worry guys I got fix for it.We are facing this issue due to lack of some dependencies in our system. they are: 1. 'python-shiboken2'
2. 'gtkglext'

Commands for installing them: "pacman -S python-shiboken2"
"pacman -S gtkglext"

Also set DNSSEC=false through this command "sudo nano /etc/systemd/resolved.conf"

Are you people enabling and starting the teamviewerd.service?

i have the same problem as Ataraxy. Teamviewer tells me the connection is not ready.

systemctl status teamviewerd says:

Jul 19 21:55:59 svelte systemd[1]: /usr/lib/systemd/system/teamviewerd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid; please update the unit file accordingly.

I have the same problems as newsboost. Putting DNSSEC=false and restart systemd-resolved didn't help at all :-( . When runnin teamviewer I just get Launching TeamViewer GUI ... as the last line and then nothing happens (and exits with non-zero code)

This doesn't work for x86, when installed via yay upon start it dumps the core.

It wasn't working until yesterday, but the next thing I did solved the problem. - Reenable sddm and teamviewer daemons. - Add firewall rule tcp/udp port 5938 I don't know why my issue solved, but I hope this helps you.

I have the same problem as Newsboost below. Does this crapware really require gdm to be running for it to actually work? Perhaps this needs to be specified in the dependencies...

Just updated and tested; teamviewer-15.6.7-1 works fine for me. No DNS shenanigans needed.