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
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: | http://www.teamviewer.com |
Licenses: | custom |
Conflicts: | teamviewer-beta |
Provides: | teamviewer |
Submitter: | Hilinus |
Maintainer: | swiftgeek (nickoe, astronautlevel) |
Last Packager: | swiftgeek |
Votes: | 1477 |
Popularity: | 3.41 |
First Submitted: | 2010-04-15 10:29 (UTC) |
Last Updated: | 2023-09-26 22:41 (UTC) |
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...
@TobFromme
Not really. The line
After = network.target network-online.target dbus.service
in the systemd unit should™ delay the start until networking is available already.
Anyone else have an issue where, if the service is configured for autostart (i.e. systemctl enable teamviewerd), the system is unavailable after a reboot, until the service is restarted again?
It appears it's because the network isn't quite ready. I've had to create a teamviewerd.timer file to delay the start.
I can provide that file, if the maintainers would like to use it.
For some reason teamviewer always renders the UI huge on my machine. I was finally able to solve it by changing the Exec
in /opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop
to the following.
Exec=/usr/bin/env QT_AUTO_SCREEN_SCALE_FACTOR=0 /opt/teamviewer/tv_bin/script/teamviewer
update please.
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