Teamviewer service no longer starts and will tell you that the TeamViewer Daemon is not running.
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled; preset: disabled)
Active: active (running) since Sat 2023-11-25 11:53:35 AEST; 11h ago
Main PID: 1451 (teamviewerd)
Tasks: 29 (limit: 38398)
Memory: 19.7M
CPU: 17.644s
CGroup: /system.slice/teamviewerd.service
└─1451 /opt/teamviewer/tv_bin/teamviewerd -d
Nov 25 11:53:35 Corey-PC systemd[1]: Starting TeamViewer remote control daemon...
Nov 25 11:53:35 Corey-PC systemd[1]: teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: No such file or directory
Nov 25 11:53:35 Corey-PC systemd[1]: Started TeamViewer remote control daemon.
Nov 25 11:55:20 Corey-PC 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.
Pinned Comments
swiftgeek commented on 2023-08-01 19:17 (UTC) (edited on 2023-08-01 19:21 (UTC) by swiftgeek)
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 commentr7v commented on 2022-06-07 14:49 (UTC)
Workaround for startx
Create drop-in
/etc/systemd/system/getty@tty1.service.d/getty@tty1.service-drop-in.conf
withSource: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399