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

Removed libdepend on x86_64, report issues related to that if they happen

Please add a pid file to /var/run/teamviewerd.pid , without this file, the service may be not started.

i can confirm that it works without the lib32 packages (i have commented out the "depends_x86_64" block in the PKGBUILD)

Another hint: with wayland, teamviewer only supports outgoing connections - if you need an incoming connection you need to open a X11 session.

1) $ teamviewer daemon status

if disable

2) $ teamviewer daemon start

then start app

why do we need 32bits-libraries for version of x86_64? I use debian(stretch) firstly and download the deb package, and I found it does not depend on 32bits-libraries by ldd Teamviewer, then I download the tar package teamviewer_13.1.3026_amd64.tar.xz from offical website and extract it on ArchLinux without lib32-xxx, which doesn't depend on lib32-xxx also, verifing through ./tv-setup checklibs.

Need to start teamviewerd first, and then everything's fine : )

@Tids: actually, there are - me, for instance. I enable the service selectively when I need TV to remotely administer my parents PC. At all other times, I do not want that daemon to be running in the background.

@swiftgeek could you just run

systemctl enable --now teamviewerd.service

from the install script? Because why not enable it, so we can use it right away? I dont think there are many users who install TV and then dont use it, but many who are a bit upset that the service isnt running after installation.

@Pietro_Pizzi I noticed this too. The individual computer settings via GUI are no longer there (where you could change the default resolution, window size, etc. per computer). However, changing these options when connected to a remote computer via the pull down menu seem to stick when logging back in. I'm not sure if those settings are just handled differently in 13 or maybe they haven't been added back in on TV13 Linux yet.

I have upgraded from v12. I'm on KDE/Plasma/SDDM and I'm logged in.

Q: Is it normal that now I can't edit any settings for my stored connections with in the GUI? The only features v13 has right now is "connect to an already saved machine" and "open the management console online" (where you can edit the connections).