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

Trying to connect to my host Wayland KDE desktop with the web Teamviewer on Firefox the process Teamviewer_Desktop on the host system just immediately segfaults while the GUI remains working. Are there any workarounds or am I missing something? Edit: Nvm, forgot to reboot my host pc after installing, now it works flawlessly.

Careful, the latest update broke my system. I solved it by booting from a live usb, chrooting into my system and installing dbus-daemon-units. Then you can remove this package and reinstall dbus-broker-units.

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.

For those on wayland with a core dump on GUI launch, try launching with setting QT_QPA_PLATFORM="" before starting. Worked for me.

From here: https://aur.archlinux.org/packages/teamviewer13#comment-827962

The original comment suggested, updating the PKGBUILD to include a sed that would automate this. Would that be an option?

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

The pinned comment https://aur.archlinux.org/packages/teamviewer?O=0#comment-640953 is outdated!

Someone please unpin it and pin this comment instead: https://aur.archlinux.org/packages/teamviewer?O=10#comment-868456

This fix makes it work without a graphical session manager (i.e. using only startx / xinitrc).

@gloomy that file is from upstream, and it's still compatible. Feel free to report at https://community.teamviewer.com/English/categories/linux

Minor issue but this package causes recurring warnings in the logs:

/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.

Maintainer can easily fix this by replacing PIDFile = /var/run/teamviewerd.pid with PIDFile = /run/teamviewerd.pid in the service file.

I wonder why https://download.teamviewer.com/download/linux/teamviewer_amd64.deb (the download link on their website), currently redirects us to the 15.37.3 release, instead of redirecting to 15.37.8, which is the latest one...

can you control your PC on wayland? Because I can on one PC but not on another...and I think that both are same configured...