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

Here too systray is broken. Manjaro KDE - Qt v5.15.2

broken here too( the systray and copypaste)

@liviu.daniel I can confirm. System tray icon is broken for me as well on Manjaro KDE - QT v5.15.1

It breaks the system tray icon on Manjaro KDE flavor. QT version is 5.15.1.

Hi,

I am using teamviewer 15.11.6-1 and am facing the same issue as Ataraxy: https://aur.archlinux.org/packages/teamviewer/?O=10&PP=10#comment-756785

Nov 14 07:30:59 user 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.

Additionally, I receive:

Nov 14 07:31:52 hostname systemd[1]: Starting TeamViewer remote control daemon...
Nov 14 07:31:52 hostname systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: Operation not permitted
Nov 14 07:31:52 hostname systemd[1]: Starting TeamViewer remote control daemon...

I checked that .pid file and though it is owned by root:root it has read rights for every user, so should be fine in my opinion:

-rw-r--r--  1 root root    4 14. Nov 07:31 teamviewerd.ipc
-rw-r--r--  1 root root    3 14. Nov 07:31 teamviewerd.pid

My problem is:

If I manually start the TeamViewer daemon (sudo systemctl start teamviewerd.service) after a reboot, I can regularly start and use TeamViewer. If I permanently enable the TeamViewer daemon (sudo systemctl enable teamviewerd.service) however, I can only start TeamViewer but it will never show me an ID.

In both cases, the daemon goes to active state and shows the exact same error messages. I have no clue why TeamViewer only generates the ID when the daemon is started manually (in both cases the TeamViewer HMI shows Ready to connect with a green circle next to it). Anyone else facing that issue?

/tmp/teamviewerTARLibCheck can be deleted at the end of the prepare step.

@praut Thanks a lot, your solution works for me too! Like @crisco, I'd also like to know more about potential implications of setting type=X11 in /etc/pam.d/system-login.

Downgrade to qt5-base 5.15.0-4 allowed me to copy and paste, however after lastest major manjaro upgrade, my system crashed and I realized that upgrading to the latest qt5 fixed this system crash. Any other solution for TeamViewer? thanks

@praut changing the session-type like this worked for me, although I'm uneasy about the ramifications of setting the session type to x11 globally. Does anyone know what affects this may have long-term?

For people was installed Teamviewer with yay.

Need to start the Teamviewer service with: sudo systemctl start teamviewerd

And stop the service with: sudo systemctl stop teamviewerd