To launch teamviewer one needs to start the teamviewer daemon by sudo systemctl enable --now teamviewerd before.
Works perfectly under KDE Plasma/Wayland.
| Git Clone URL: | https://aur.archlinux.org/teamviewer.git (read-only, click to copy) |
|---|---|
| Package Base: | teamviewer |
| Description: | All-In-One Software for Remote Support and Online Meetings |
| Upstream URL: | https://www.teamviewer.com/en/download/portal/linux/ |
| Licenses: | custom |
| Conflicts: | teamviewer-beta |
| Provides: | teamviewer |
| Submitter: | Hilinus |
| Maintainer: | swiftgeek (nickoe, astronautlevel) |
| Last Packager: | swiftgeek |
| Votes: | 1486 |
| Popularity: | 2.03 |
| First Submitted: | 2010-04-15 10:29 (UTC) |
| Last Updated: | 2025-11-11 19:03 (UTC) |
To launch teamviewer one needs to start the teamviewer daemon by sudo systemctl enable --now teamviewerd before.
Works perfectly under KDE Plasma/Wayland.
Thanks swiftgeek for him teamviewer 15.71.4-1 stable package!!!
When are we switching to the standard qt (QT6)? qt5-webengine is already only on AUR.
I installed it via paru (use your favorite helper or compile with makepkg), then I did this procedure and it worked (I use Wayland):
cp -av "/opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop" "$HOME/.local/share/applications/"
sed -i 's/Exec=/Exec=env QT_QPA_PLATFORM="" /' "$HOME/.local/share/applications/com.teamviewer.TeamViewer.desktop"
sudo systemctl start teamviewerd
sudo systemctl enable teamviewerd
systemctl status teamviewerd
What am I doing wrong with this every dang time I try to use it. teamviewerd daemon is running but 'teamviewer' only show this and nothing happens.
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
also checked that no process of 'teamviewer' exist, only teamviewerd. Tried this about a year ago and same thing so it gotta be me!!
Also tried @r7v trick-fix but nothing.
(again...uninstalled it)
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
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.
startxusers 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.confwithSource: https://community.teamviewer.com/English/discussion/95696/teamviewer-15-stopped-working-on-debian-buster#M4399