@skerit forcing teamviewer to run under xwayland works for me for outgoing connections (presumably not for incoming connections):
QT_QPA_PLATFORM=xcb teamviewer
Search Criteria
Package Details: teamviewer 15.32.3-1
Package Actions
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: | 1459 |
Popularity: | 2.49 |
First Submitted: | 2010-04-15 10:29 (UTC) |
Last Updated: | 2022-07-26 20:15 (UTC) |
Dependencies (5)
Required by (4)
Sources (4)
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.32.3_amd64.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.32.3_arm64.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.32.3_armhf.deb
- https://dl.teamviewer.com/download/linux/version_15x/teamviewer_15.32.3_i386.deb
Latest Comments
mauro2 commented on 2022-07-28 21:27 (UTC)
hron84 commented on 2022-07-25 17:59 (UTC)
@swiftgeek I have an updated PKGBUILD for 15.31.5. Should I upload the new file?
Also, I tuned the git repo to ignore files.
MarsSeed commented on 2022-06-11 23:38 (UTC)
Ping @2022-05-05: Please remove depends=qt5-webkit
. Thank you.
r7v 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
with
[Service]
Environment=XDG_SESSION_TYPE=x11
MajorMayer commented on 2022-05-31 20:54 (UTC)
It would be nice if this could be upgraded to 15.30.3 : https://www.teamviewer.com/en/download/linux/
MarsSeed commented on 2022-05-12 14:32 (UTC)
MarsSeed commented on 2022-05-12 12:45 (UTC) (edited on 2022-05-12 13:49 (UTC) by MarsSeed)
@skerit I don't think the AUR maintainers can do anything about it. TeamViewer comes as a prebuilt binary only. You'll have to report the issue upstream, e.g. on the TeamViewer support forums.
In the meantime you could give a try to teamviewer-quicksupport which is built from the same codebase as TeamViewer but has a slightly newer version (v15.30.2 at the moment).
skerit commented on 2022-05-12 12:00 (UTC)
Teamviewer crashes on my Gnome Shell with Wayland setup:
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
fish: Job 1, 'teamviewer' terminated by signal SIGABRT (Abort)
MarsSeed commented on 2022-05-05 02:07 (UTC)
qt5-webkit dependency is not needed anymore.
macxcool commented on 2022-04-09 12:28 (UTC)
@swiftgeek In the post_install function in the teamviewer.install you have the instructions "Execute 'sudo systemctl enable teamviewerd' in a terminal". This won't start the teamviewer daemon and so is a bit confusing, I think. Maybe "sudo systemctl enable teamviewerd --now" or "sudo systemctl start teamviewerd" would be better? Just a suggestion. Thanks for maintaining this package.
dakotta commented on 2022-03-17 15:42 (UTC)
Following up... according to TeamViewer technical support: "There have been some issues with the audio being enabled causing the connection to crash on some Linux devices as you described. In order to fix this try deactivating the 'play computer sounds and music' on the remote control section on the device you connect from."
This seems to have fixed the segfault for the time being. I am running fluxbox as a WM, sddm as a DM, and .xinitrc as a session. Cheers.
dakotta commented on 2022-03-10 00:23 (UTC)
I have been having trouble with segfaults since version 15.16.8 https://aur.archlinux.org/packages/teamviewer#comment-803796 https://bbs.archlinux.org/viewtopic.php?id=265752
Periodically an update will fix the problem, but after the next qt update, the segfaults return.
Can someone please suggest any combination of windows manager, file manager, and desktop environment that is working reliably for them (obviously, on a system that is kept up-to-date)?
I really need something that is stable so I can provide remote support.
Ataraxy commented on 2022-01-25 05:31 (UTC) (edited on 2022-01-25 05:31 (UTC) by Ataraxy)
To reproduce the output in ArthurBorsboom's comment:
% systemd-analyze verify teamviewerd.service
/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.
Perhaps a patch could fix this if upstream does't want to fix it?
xorangekiller commented on 2022-01-04 00:54 (UTC)
I would like to second Saeroshi's request to add aarch64 support to this package, please, except instead of using the more limited -host
build of TeamViewer that Saeroshi suggested, I would really like to have the full TeamViewer build that we have for i686 and x86_64.
I applied the patch below and tested it on my Pinebook Pro, and it works great! I was able to use TeamViewer to connect out and remote control a different computer just like on my x86_64 machines.
If you wouldn't mind applying the patch and adding aarch64 support next time you update the package, that would be great! Thank you!
diff --git a/PKGBUILD b/PKGBUILD
index 4de2191..8d1a061 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@ pkgname=teamviewer
pkgver=15.25.5
pkgrel=1
pkgdesc='All-In-One Software for Remote Support and Online Meetings'
-arch=('i686' 'x86_64' 'armv7h')
+arch=('i686' 'x86_64' 'armv7h' 'aarch64')
url='http://www.teamviewer.com'
license=('custom')
options=('!strip')
@@ -35,9 +35,11 @@ source_x86_64=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/
source_i686=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
source_armv7h=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer-host_${pkgver}_armhf.deb")
#source_armv7h=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer-host_13.2.13582_armhf.deb")
+source_aarch64=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer_${pkgver}_arm64.deb")
sha256sums_i686=('a6ffcd8b342cdbaa350a1c93f1bd2060e20436310c1a4377a0a8013797d97762')
sha256sums_x86_64=('2ed2133d2d1b2f2f3976fff374ea3c25cb04674660b5598cf8272081a609c570')
sha256sums_armv7h=('cb24786d5bfaed7b5d2d9e3e780c2b8070d6a47d761c21244a419fc8f1968d1c')
+sha256sums_aarch64=('12195adb466be74edc235fa9dbd00444e7b210fbb899bb627696f3a1ba301de8')
prepare() {
warning "If the install fails, you need to uninstall previous major version of Teamviewer"
Andresterix commented on 2021-12-16 17:08 (UTC)
15.5 is not out yet, you may have seen a past version marked 15.15.5 and gotten confused. This is the "Latest" official code release (Full Version). The website still has download links to 5.23, (last official release). Makes sense, and AUR is fully up to date from what I can tell, this flag is a false flag.
Please fix, thanks!
PS. I am signed up on AUR now, and I can help out with this package if you want, just linked my Github into your AUR repo... :)
Angus commented on 2021-12-16 12:09 (UTC)
What @sukanka says sounds reasonable. The bundled Qt does not come with Wayland support: /opt/teamviewer/tv_bin/RTlib/qt/plugins/platforms only contains libqxcb.so, but no libqwayland*.
By removing the bundled Qt (and setting QT_QPA_PLATFORM=wayland), we can use TeamViewer as a Wayland window for outgoing connections. Incoming still doesn’t work, but that’s a whole other story (see https://community.teamviewer.com/English/discussion/26340/state-of-wayland-teamviewer).
Saeroshi commented on 2021-12-14 19:34 (UTC)
Hello,
Can you add support for aarch64?
diff --git a/PKGBUILD b/PKGBUILD
index 0f060ec..df52926 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@ pkgname=teamviewer
pkgver=15.24.5
pkgrel=1
pkgdesc='All-In-One Software for Remote Support and Online Meetings'
-arch=('i686' 'x86_64' 'armv7h')
+arch=('i686' 'x86_64' 'armv7h' 'aarch64')
url='http://www.teamviewer.com'
license=('custom')
options=('!strip')
@@ -34,10 +34,12 @@ install=teamviewer.install
source_x86_64=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer_${pkgver}_amd64.deb")
source_i686=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
source_armv7h=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer-host_${pkgver}_armhf.deb")
+source_aarch64=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer-host_${pkgver}_arm64.deb")
#source_armv7h=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.*}x/teamviewer-host_13.2.13582_armhf.deb")
sha256sums_i686=('e9d62005281c18e96fdb06c6c487aeb3b9d219efa10e661a61aada27298d0a58')
sha256sums_x86_64=('bb86b3563c03e714dcd2f59ef2d0c4c78e2b05d6056658d93d5434ca296a791d')
sha256sums_armv7h=('c71760d9d0fdd1832f81a75bee0bcc518e6fe9e670665ac128161b623d766b55')
+sha256sums_aarch64=('59d6aade80c6ded96b6aa242e294a921f4475a895bd65d39cdab2d1ed765bccf')
prepare() {
warning "If the install fails, you need to uninstall previous major version of Teamviewer"
somepaulo commented on 2021-11-11 14:16 (UTC)
The application does not declare a WMClass properly. Because of this, icon themes cannot be applied properly, and the running application displays a generic icon in the taskbar/dash. Adding the following line to the com.teamviewer.TeamViewer.desktop file fixes this:
StartupWMClass=TeamViewer
Can this be done at the packaging level so we don't have to redo it manually every time or create a local copy of the .desktop file?
TiredExcitedAUR commented on 2021-10-27 07:44 (UTC) (edited on 2021-10-27 07:47 (UTC) by TiredExcitedAUR)
@mesmer
to solve the teamviewer gui problem just run the .desktop file gtk-launch /usr/share /applications/teamviewerapi.desktop or run /opt/teamviewer/tv_bin/script/teamviewer
or the last resort, open a gnome, and run the teamviewer
after the first open, you can use the bin teamviewer normaly
First two options started the process, but it still hangs on Launching TeamViewerGUI ... . Process does not exit in terminal, but no EULA window is spawned either. This is the output for both .desktop files from /usr/share and /opt:
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
I am using Qtile Window Manager with startx.
mesmer commented on 2021-10-14 18:30 (UTC)
just to make clear the problem, the teamviewer ask for a accept in terms, that dont show with the terminal bin without the command from .desktop
mesmer commented on 2021-10-14 18:23 (UTC)
to solve the teamviewer gui problem just run the .desktop file gtk-launch /usr/share/applications/teamviewerapi.desktop or run /opt/teamviewer/tv_bin/script/teamviewer
or the last resort, open a gnome, and run the teamviewer
after the first open, you can use the bin teamviewer normaly
Kritiqual commented on 2021-10-10 14:58 (UTC)
when I launch it from terminal, it didn't show any error and didn't run, why
ArthurBorsboom commented on 2021-10-04 17:07 (UTC)
systemd reports:
/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.
Maybe it is something that needs to be reported upstream?
sukanka commented on 2021-09-27 07:29 (UTC)
We can add this to package
function to force it to use system Qt5. It still works.
rm -rf "${pkgdir}"/opt/teamviewer/tv_bin/RTlib/qt
teamviewer git:(master) ✗ ldd /opt/teamviewer/tv_bin/TeamViewer | grep libQt
libQt5Quick.so.5 => /usr/lib/libQt5Quick.so.5 (0x00007f06b2690000)
libQt5X11Extras.so.5 => /usr/lib/libQt5X11Extras.so.5 (0x00007f06b2689000)
libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5 (0x00007f06b25f8000)
libQt5Qml.so.5 => /usr/lib/libQt5Qml.so.5 (0x00007f06b2175000)
libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f06b1a98000)
libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f06b153f000)
libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f06b0e8a000)
libQt5WebEngine.so.5 => /usr/lib/libQt5WebEngine.so.5 (0x00007f06b0e15000)
libQt5WebEngineCore.so.5 => /usr/lib/libQt5WebEngineCore.so.5 (0x00007f06a921e000)
libQt5QmlModels.so.5 => /usr/lib/libQt5QmlModels.so.5 (0x00007f06a8e63000)
libQt5Network.so.5 => /usr/lib/libQt5Network.so.5 (0x00007f06a8cbe000)
libQt5WebChannel.so.5 => /usr/lib/libQt5WebChannel.so.5 (0x00007f06a7f80000)
libQt5Positioning.so.5 => /usr/lib/libQt5Positioning.so.5 (0x00007f06a7ef0000)
jhossbach commented on 2021-08-29 19:46 (UTC)
@rafaelff: I see, thanks for the clearing up!
rafaelff commented on 2021-08-29 19:14 (UTC)
Oh, I see; latest PKGBUILD version has qt5-webengine as depends, so issue solved.
rafaelff commented on 2021-08-29 19:11 (UTC)
@jhossbach: actually your analysis is not correct.
lddtree
tool shows us that /opt/teamviewer/tv_bin/TeamViewer
is linked to libQt5WebEngineCore.so.5 from /opt/teamviewer/tv_bin/RTlib/qt/lib/libQt5WebEngineCore.so.5
, which is not the soname file provided by qt5-webengine
package; it is provided in the teamviewer package.
lddtree
also shows us that /opt/teamviewer/tv_bin/RTlib/qt/lib/libQt5WebEngineCore.so.5
is linked to libminizip.so.1 from /usr/lib/libminizip.so.1
, which is provided by the minizip package:
$ pacman -Qo /usr/lib/libminizip.so.1
/usr/lib/libminizip.so.1 pertence a minizip 1:1.2.11-4
Run pactree teamviewer | less
(pactree from pacman-contrib) to see that minizip is not in the package dependency tree.
If minizip is not listed in the package dependency tree neither provided in the package, it is a missing dependency.
jhossbach commented on 2021-08-29 18:36 (UTC)
'lddtree /opt/teamviewer/tv_bin/TeamViewershows that qt5-webengine depends on
/usr/lib/libminizip.so.1, and indeed
qt5-webenginehas
minizipas a dependency. So
minizipshould already be installed through
qt5-webengine`. I just want to clarify this for anyone interested
rafaelff commented on 2021-08-29 16:08 (UTC)
readelf
from binutils
is also a good option, and cleaner than ldd
:
readelf -d /opt/teamviewer/tv_bin/TeamViewer | grep NEEDED
swiftgeek commented on 2021-08-29 15:58 (UTC)
Use lddtree
from pax-utils
for more accurate representation of a dependency tree
jhossbach commented on 2021-08-29 15:28 (UTC)
minizip
is indeed needed as dependency, running ldd /opt/teamviewer/tv_bin/TeamViewer |grep minizip
gives /usr/lib/libminizip.so.1
.
0xb000bd commented on 2021-08-28 21:35 (UTC) (edited on 2021-08-28 21:36 (UTC) by 0xb000bd)
It took me too much time to make teamviewer launch successfully :)
Add minizip
to Dependencies. PLEASEEEEEE :(
quasigod commented on 2021-08-25 05:11 (UTC)
Please add minizip as a dependency, it will not launch the gui without it.
iohzrd commented on 2021-08-16 18:51 (UTC)
can confirm, not working after most recent update.
~ >>> sudo systemctl status teamviewerd
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; disabled; vendor preset: disabled)
Active: active (running) since Mon 2021-08-16 11:51:05 PDT; 963ms ago
Process: 22905 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 22907 (teamviewerd)
Tasks: 28 (limit: 38438)
Memory: 3.0M
CPU: 12ms
CGroup: /system.slice/teamviewerd.service
└─22907 /opt/teamviewer/tv_bin/teamviewerd -d
Aug 16 11:51:05 systemd[1]: Starting TeamViewer remote control daemon...
Aug 16 11:51:05 systemd[1]: teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: Operation not permitted
Aug 16 11:51:05 systemd[1]: Started TeamViewer remote control daemon.
carsten87 commented on 2021-08-13 12:43 (UTC)
Here in AUR, the version is said to be 15.20.6-1. When I build the package and run TeamViewer, however, the application (Help -> About TeamViewer) says it's version 15.14.3.
Which is true?
Nevuly commented on 2021-08-07 14:39 (UTC)
viktors commented on 2021-08-01 11:53 (UTC)
I had the no-gui problem described here on reddit
strace
pointed out libminizip
, installing which resolved it. Can you add minizip
package as a dependency?
rafaelff commented on 2021-07-30 19:34 (UTC)
The teamviewer_setup checklibs
step reported "not found" for all libraries. Still, the package built and the software is working just fine. I built it in clean chroot. Is this result expected?
IstBarP commented on 2021-07-23 23:07 (UTC) (edited on 2021-07-30 21:44 (UTC) by IstBarP)
Had issues with initialzing display parameters after upgrading. I think it has to do with libminizip or something. Not sure.
Downgrading to 15.18.5 fixed my issues.
I'm using a virtual display.
Retried latest update, after updating by accident. Installing minizip as comment below says fixes the problem with "initializing display"
ogulcancelik commented on 2021-07-14 12:15 (UTC)
GUI is working after installing 'minizip' package, can you add it as a dependency? @swiftgeek
cipanzhi commented on 2021-07-06 19:47 (UTC)
@swiftgeek you need to add 'minizip' package as a dependencies. Otherwise it will not run.
amdgoodez commented on 2021-07-02 19:58 (UTC) (edited on 2021-07-08 18:20 (UTC) by amdgoodez)
@tioguda Nope, I've tried -Rncs and reinstalling the app again and its truly borked. Nothing pops up at all, No GUI. I reverted to the previous version, and the GUI comes up but says that the teamviewer daemon is not running. I enabled ad started the teamviewerd service again and even that still wouldn't work.
Thanks to @cipanzhi, after installing minizip package, Teamviewer is working again! Thank you.
tioguda commented on 2021-07-02 17:34 (UTC)
@amdgoodez it doesn't work even after restarting the system?
amdgoodez commented on 2021-07-02 16:55 (UTC)
After updating to latest release, Teamviewer is no longer working.
adrian5 commented on 2021-06-15 14:04 (UTC)
Small detail, but the teamviewer.desktop file points its Icon to "teamviewer.png" which doesn't exist by name. I thought to just symlink to the desktop file, but maybe it's meant to be copied and the icon size selected according to personal use case?
ArthurBorsboom commented on 2021-05-24 16:56 (UTC)
teamviewerd.service
/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.
Needs to go upstream ?
bittin commented on 2021-05-03 11:25 (UTC)
Updated Teamviewer PKGBUILD: https://pastebin.com/xNNEzEHT
flo.lm commented on 2021-05-03 11:14 (UTC)
Also having the segfault after a few seconds.
Version 15.9.5 seems to work fine, as reported in other comments.
I used the tar from TeramViewer Host (available from them at https://download.teamviewer.com/download/linux/version_15x/teamviewer-host_15.9.5_amd64.tar.xz ).
The non-Host version 15.9.5 is also available there
scarecrow commented on 2021-04-30 19:43 (UTC) (edited on 2021-04-30 20:51 (UTC) by scarecrow)
I can confirm the segfault dakota is mentioning. Running kernel 5.12 and LightDM with nvidia binary driver. I upgraded to the last version (15.17.6) and it still segfaults. 15.9.5 works without issues.
dakotta commented on 2021-04-25 16:37 (UTC)
@abyss02 - I was afraid you would say that.
I'm running x11, with an SDDM display manager, an xinitrc session, and the nouveau video driver with early KMS start.
Additionally, the HP machine uses xorg-xrandr for multihead.
I'll be back onsite this week, so I can check the pacman log to see what exactly was updated. There may be some clues there.
Unless you read the stack trace? Is there anything there that suggests a direction to pursue?
I created a thread in the forum to discuss this: https://bbs.archlinux.org/viewtopic.php?id=265752 if you'd rather discuss there.
Cheers,
commented on 2021-04-24 08:26 (UTC)
@dakotta: not here, teamviewer is very stable, cannnot reproduce your issue. are you running x11 or wayland?
dakotta commented on 2021-04-23 20:38 (UTC)
version 15.16.8 segfaults within 10 seconds of receiving incoming connections. [Outgoing connections seem to work okay.]
I have tested this on 2 different machines running 5.11.16-arch1-1 (once on a VMware virtual machine, once on an HP server)
commented on 2021-03-25 22:51 (UTC)
There is a new version available - 15.16.8-1. I already updated your PKGBUILD locally and built the new package. I would like to support you to have this package updated in future. How to achieve that?
callmejoe commented on 2021-02-22 03:56 (UTC) (edited on 2021-02-22 04:01 (UTC) by callmejoe)
@leanhtai01 that used to happen to me (and many others) on earlier versions of ver 15. but seemed to be fixed with ver 15.13. at least for me.
leanhtai01 commented on 2021-02-22 03:06 (UTC)
@callmejoe Yes, I already enable teamviewerd using: systemctl enable teamviewerd
After reboot systemctl status teamviewerd
say teamviewerd is active (running) but I need to run systemctl restart teamviewerd
to make "Computers & Contacts" and "Chat" features working.
callmejoe commented on 2021-02-21 02:20 (UTC)
@leanhtai01 did you enable the service to start at boot?
systemctl enable teamviewerd
leanhtai01 commented on 2021-02-21 02:10 (UTC)
To make "Computers & Contacts" and "Chat" features working I must restart teamviewerd.service everytime I reboot my laptop.
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2021-02-21 08:42:09 +07; 27min ago
Process: 2118 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 2127 (teamviewerd)
Tasks: 20 (limit: 18828)
Memory: 14.6M
CGroup: /system.slice/teamviewerd.service
└─2127 /opt/teamviewer/tv_bin/teamviewerd -d
Feb 21 08:42:09 archlinux systemd[1]: Starting TeamViewer remote control daemon...
Feb 21 08:42:09 archlinux systemd[1]: teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: Operation not permitted
Feb 21 08:42:09 archlinux systemd[1]: Started TeamViewer remote control daemon.
max.bra commented on 2021-02-11 17:11 (UTC)
hi all, it's only me or when teamviewerd service is stopped it fails with abort signal?
sovanyio commented on 2021-02-08 19:18 (UTC)
The tmpfiles configuration needs to be updated to the new directory. /var/run
-> /run
titockmente commented on 2021-02-04 03:28 (UTC)
Same bug on Manjaro Xfce while launching Teamviewer
Delan commented on 2021-02-01 23:08 (UTC)
Similar bug as the one reported by @buzzra: on Manjaro Xfce, launching Teamviewer makes the taskbar icon list crash ("Greffon de barre d'état" in French). It is removed and has to be re-added to the panel after every launch.
mathijsh commented on 2021-01-26 11:22 (UTC)
@ferrvittorio
I got the same issue and solved it by running the following commands:
systemctl enable teamviewerd.service systemctl start teamviewerd.service
After that Teamviewer starts
ferrvittorio commented on 2021-01-07 05:43 (UTC)
@callmejoe Hi, I have ExecStart=/usr/bin/lightdm
And for other previous versions (found around in AUR) teamviewer worked
Now previous versions dont work because remote client, windows, rejects me as newer version found.
callmejoe commented on 2021-01-06 14:52 (UTC)
@ferrvittorio are you using a Display Manager? Teamviewer will only work if you have one
ferrvittorio commented on 2021-01-06 09:24 (UTC)
I restarted via menu shortcut, and program asked again for daemon. Like in a loop
callmejoe commented on 2021-01-05 21:38 (UTC)
@ferrvittorio what did you after issuing command 'teamviewer --daemon start'?
ferrvittorio commented on 2021-01-05 16:41 (UTC)
Hi, asks for 'teamviewer --daemon start' and wont start
ilovesusu commented on 2021-01-03 13:19 (UTC)
why no tray icon?
buzzra commented on 2020-12-31 22:13 (UTC)
tray icon not showing up on Manjaro KDE. latest version of TV and Plasma updates. The space is there, and when I click TV comes up. Just no icon showing in tray.
WFV commented on 2020-12-29 03:26 (UTC) (edited on 2020-12-30 15:16 (UTC) by WFV)
@callmejoe
5.15.2-2
here also. switched to LXDE/openbox for now, no issues there
callmejoe commented on 2020-12-29 00:55 (UTC)
@WFV. interesting rolling back xfce4-panel works for me and not you. what version of qt5-base are you running? i am on 5.15.2-2
WFV commented on 2020-12-28 22:43 (UTC) (edited on 2020-12-28 22:47 (UTC) by WFV)
Rollback Xfce doesn't work in my case. Xfce4-4.16 now has Status Tray Plugin add to panel however, it core-dumps when teamviewerd is active. I can can add the plugin to a panel and no core-dump until teamviewerd is started. libglib-2.0.so.0 is indicated in the core-dump. Noting that it appears to be an Xfce4 problem, not Teamviewer - possibly Xfce4 and qt5. Similar problem with hplip-plugin hp-systray(qt5): error: No system tray detected on this system. Unable to start, exiting.
callmejoe commented on 2020-12-24 20:48 (UTC)
system tray icon (plugin) stopped working with xfce4 updates today for me too. i downgraded xfce4-panel to 4.14.1-1. sys tray plugin works now
WFV commented on 2020-12-24 19:48 (UTC)
system tray icon (plugin) stopped working with xfce4 updates today, but everything else is functional, this happens time and again, no big deal here thanks for the package swiftgeek! https://community.teamviewer.com/English/kb/articles/30653-system-tray-statusnotifier-and-teamviewer-for-linux
blablubb1234 commented on 2020-12-24 00:06 (UTC) (edited on 2020-12-28 00:45 (UTC) by blablubb1234)
Hi,
I just upgraded to version 15.13.6-1 and my issue is gone. TeamViewer receives an id when the system.d service is enabled permanently.
BR
Andrea993 commented on 2020-12-20 18:46 (UTC)
md5 validity fails
bittin commented on 2020-12-16 10:10 (UTC)
Updated PKGBUILD with todays update: https://pastebin.com/vUj11Qry
manjaro_loover commented on 2020-12-09 12:53 (UTC)
System try issue as well. Manjaro 20.2. KDE Plasma 5.20.4
raowillkillu commented on 2020-12-02 09:00 (UTC)
Here too systray is broken. Manjaro KDE - Qt v5.15.2
usuariopolivalen commented on 2020-11-30 21:40 (UTC)
broken here too( the systray and copypaste)
Natetronn commented on 2020-11-26 00:32 (UTC)
@liviu.daniel I can confirm. System tray icon is broken for me as well on Manjaro KDE - QT v5.15.1
liviu.daniel commented on 2020-11-19 20:22 (UTC)
It breaks the system tray icon on Manjaro KDE flavor. QT version is 5.15.1.
blablubb1234 commented on 2020-11-14 06:51 (UTC) (edited on 2020-11-14 07:06 (UTC) by blablubb1234)
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?
zadkiel commented on 2020-11-08 09:02 (UTC)
/tmp/teamviewerTARLibCheck can be deleted at the end of the prepare step.
dakush commented on 2020-10-28 20:04 (UTC)
@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.
damico commented on 2020-10-12 10:00 (UTC)
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
crisco commented on 2020-10-11 18:16 (UTC)
@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?
jiahuiz commented on 2020-09-29 12:49 (UTC) (edited on 2020-09-29 12:51 (UTC) by jiahuiz)
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
magicwindow commented on 2020-09-22 20:02 (UTC)
@damico
it's related to the regression introduced in versions of qt5-base after 5.15.0-4, which also breaks the system tray icon. if you downgrade the qt5-base package to that version, copy+paste and the tray icon should work normally again.
damico commented on 2020-09-22 17:06 (UTC)
Why can't I copy and paste inside TeamViewer? Like someone send me a ID and password, I can't control+c and control+v inside the application.
ahmubashshir commented on 2020-09-14 15:55 (UTC) (edited on 2020-09-14 15:56 (UTC) by ahmubashshir)
qt5-base 5.15.0-5 seems to break the system tray icon for me on KDE. Works fine on qt5-base 5.15.0-4.
happened on xfce too.
magicwindow commented on 2020-09-08 18:19 (UTC)
qt5-base 5.15.0-5 seems to break the system tray icon for me on KDE. Works fine on qt5-base 5.15.0-4.
praut commented on 2020-09-06 16:45 (UTC)
tnx @dumblob, yes, it's all about session type.
You cannot change it from dbus, but, you can set it type initially. From PAM config.
Add "type=x11" to /etc/pam.d/system-login:
-session optional pam_systemd.so type=x11
And that crapware will run without DM afterwards. And don't forget to add your user to video group (usermod -a -G video username) for /dev/fb access.
dumblob commented on 2020-08-31 06:56 (UTC)
@seyn6gk regarding startx etc. not working, I'm pretty sure it's because TV looks for session type (loginctl session-status | grep Service:
) and finds out its type is tty
instead of x11
(or wayland
).
Systemd v246 added support for changing session type "on the fly" (see how sway implements that), but I couldn't make it work with Activate -> TakeControl -> SetType using dbus-send
and then startx
(I always get only owner of the terminal can take control
).
Feel free to try yourself as it should work.
sudo dbus-send --system --print-reply --dest=org.freedesktop.login1 \
/org/freedesktop/login1/session \
org.freedesktop.DBus.Introspectable.Introspect |
grep -E 'node name="_.*'
(use the session number in the subsequent dbus-send calls)
dbus-send --system --print-reply --dest=org.freedesktop.login1 \
/org/freedesktop/login1/session/_"$1" \
org.freedesktop.login1.Session.Activate
dbus-send --system --print-reply --dest=org.freedesktop.login1 \
/org/freedesktop/login1/session/_"$1" \
org.freedesktop.login1.Session.TakeControl boolean:true
dbus-send --system --print-reply --dest=org.freedesktop.login1 \
/org/freedesktop/login1/session/_"$1" \
org.freedesktop.login1.Session.SetType string:x11
himanshu0498 commented on 2020-08-07 14:20 (UTC) (edited on 2020-08-07 14:27 (UTC) by himanshu0498)
Don't worry guys I got fix for it.We are facing this issue due to lack of some dependencies in our system.
they are:
1. 'python-shiboken2'
2. 'gtkglext'
Commands for installing them:
"pacman -S python-shiboken2"
"pacman -S gtkglext"
Also set DNSSEC=false through this command "sudo nano /etc/systemd/resolved.conf"
lucasrizzini commented on 2020-08-03 11:38 (UTC)
Are you people enabling and starting the teamviewerd.service?
mxmlnznr commented on 2020-08-03 11:02 (UTC)
i have the same problem as Ataraxy. Teamviewer tells me the connection is not ready.
Ataraxy commented on 2020-07-19 14:59 (UTC)
systemctl status teamviewerd says:
Jul 19 21:55:59 svelte 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.
kotrfa commented on 2020-07-04 09:29 (UTC)
I have the same problems as newsboost. Putting DNSSEC=false and restart systemd-resolved didn't help at all :-( . When runnin teamviewer I just get Launching TeamViewer GUI ...
as the last line and then nothing happens (and exits with non-zero code)
kirk commented on 2020-06-15 10:13 (UTC)
This doesn't work for x86, when installed via yay upon start it dumps the core.
nixir commented on 2020-06-08 08:26 (UTC)
It wasn't working until yesterday, but the next thing I did solved the problem. - Reenable sddm and teamviewer daemons. - Add firewall rule tcp/udp port 5938 I don't know why my issue solved, but I hope this helps you.
fuan_k commented on 2020-06-06 15:49 (UTC)
I have the same problem as Newsboost below. Does this crapware really require gdm to be running for it to actually work? Perhaps this needs to be specified in the dependencies...
direc85 commented on 2020-06-05 17:42 (UTC)
Just updated and tested; teamviewer-15.6.7-1 works fine for me. No DNS shenanigans needed.
siyia commented on 2020-06-05 12:29 (UTC)
broken since today on archlinux
siyia commented on 2020-06-04 00:47 (UTC)
Thx to huupoke12 DNSSEC=false in /etc/systemd/resolved.conf resolves the connection issues
huupoke12 commented on 2020-06-02 13:45 (UTC) (edited on 2020-06-02 13:50 (UTC) by huupoke12)
@siyia No, it's because of bad DNSSEC record, not DNSOverTLS. See my previous comment. No need to disable systemd-resolved
and DNS Over TLS, setting DNSSEC=false
in the config will make it work again.
siyia commented on 2020-06-02 10:02 (UTC)
DNSOverTLS causes network errors with teamviewer, temporarily stop systemd-resolved service if you need to use it
newsboost commented on 2020-05-27 19:46 (UTC) (edited on 2020-05-31 18:17 (UTC) by newsboost)
hmm.... Teamviewer - previous versions of this package I'm using now "aur/teamviewer 15.5.6-1" has been working for years, but now things from 15.5.6-1 just stopped working, just after upgrading my system... It just says:
$ teamviewer
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
And nothing happens...
"systemctl status teamviewerd" says "teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet..". I recently switched to sway (wayland) - but I also tried gnome... I also found that the "~/.local/share/teamviewer15/logfiles/TeamViewer15_Logfile.log" contains some info, several errors - among these:
2020/05/27 21:40:11.092 24033 139947291594048 G!! MonitorInfo: WorkingArea: Property error 14 (0), Errorcode=13
2020/05/27 21:40:11.095 24033 139947291594048 G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=13
2020/05/27 21:40:11.098 24033 139947291594048 G!! StorageTextfile: Unable to open configuration file '/opt/teamviewer/config/global.conf' (RO), Errorcode=13
2020/05/27 21:40:11.101 24033 139947291594048 G!! ResourceLoader: loaded file '/opt/teamviewer/tv_bin/resources/TVResource_en.so' version () is not matching with application version (15.5.6)
Pretty annoying; By the way, I discovered that as root you probably need to edit /usr/lib/systemd/system/teamviewerd.service (change /var/run/teamviewerd.pid → /run/teamviewerd.pid). But I couldn't make it work (the /var/run just fixes one of several issues I think)... Damn! I think the conclusion is that the file "/opt/teamviewer/tv_bin/resources/TVResource_en.so" has a wrong version. If anyone know the solution, that would be greatly appreciated, thanks!
UPDATE: Annoying problem solved with "systemctl enable gdm" and rebooting (for some reason doesn't work with startx).
Ovex commented on 2020-05-22 09:01 (UTC)
The PKGBUILD should source from dl.teamviewer.com
instead of dl.tvcdn.de
since teamviewer.com
is the canonical TeamViewer domain and would allow to directly verify the authenticity of the Debian packages.
direc85 commented on 2020-05-05 05:15 (UTC)
If you want to update the package before it's updated in AUR, you can use this script:
#!/bin/bash
# Set this to updated version
# and run the script.
_newver=15.5.3
_oldver=$(grep "pkgver=" PKGBUILD | grep -o '[0-9.]*')
if [[ "$_oldver" == "$_newver" ]]; then
echo "Nothing to do."
exit 0
fi
echo "Updating..."
sed -i "s|^pkgver=.*$|pkgver=${_newver}|" PKGBUILD
updpkgsums
makepkg --printsrcinfo > .SRCINFO
The package installation does say:
The Teamviewer daemon must be running for Teamviewer to work.
Execute 'sudo systemctl enable teamviewerd' in a terminal.
But nobody seems to read it. I suggested a fix for it earlier, among automatic update script and other improvements, here is the updated patch: https://pastebin.com/UgHp4u3S
a5pire commented on 2020-05-04 20:38 (UTC) (edited on 2020-05-05 05:31 (UTC) by a5pire)
Hi all, just a heads up. If you're having trouble with starting team viewer (connections unavailable), just start the daemon first
$ sudo systemctl start teamviewerd
Make sure to enable on start.
marsoft commented on 2020-04-26 18:42 (UTC) (edited on 2020-04-26 18:43 (UTC) by marsoft)
Hello to all follow xsession guys. I have the same problem using ly
session manager and sway
WM. Some additional details: logs are available in ~/.local/share/teamviewer15/logfiles/
. Most relevant one is TeamViewer15_Logfile.log
which contains a bunch of the following errors:
2020/04/26 21:36:28.840 52749 140543546674496 G!! SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11
I thought it might be related to SESSION_MANAGER
env variable and tried to run it from under xsm
which does set that variable, but it did not change anything.
TeamViewer 12 works for me, but it does not support newer protocol version.
zehph commented on 2020-04-21 00:56 (UTC)
I'm a startx guy, not able to start the GUI either, no error message, same as txtsd.
huupoke12 commented on 2020-04-15 08:23 (UTC) (edited on 2020-04-15 12:44 (UTC) by huupoke12)
It seems that DNSSEC checks fail for router*.teamviewer.com because of bogus CNAME. Disabling DNSSEC will resolve the network error.
$ drill -DT router9.teamviewer.com @1.1.1.1
...
[B] Unable to verify denial of existence for router9.teamviewer.com., because of BOGUS CNAME
FrederickZh commented on 2020-04-07 10:19 (UTC)
Just want to share a weird issue (and solution) I had. If you've ever launched the GUI without starting the daemon first, you may want to remove /etc/teamviewer/global.conf
before relaunching the GUI otherwise it won't allow you to type in email/password fields sometimes.
maciex commented on 2020-04-05 08:21 (UTC)
Why it is sourced to tvcdn.de and not directly to teamviewer.com if it is deb from Microsoft?
maciex commented on 2020-04-05 08:21 (UTC)
Why it is sourced to tvcdn.de and not directly to teamviewer.com if it is deb from Microsoft?
lucasrizzini commented on 2020-04-04 12:51 (UTC)
Change the $pkgver to 15.4.4445.
kahgha commented on 2020-04-02 15:36 (UTC) (edited on 2020-04-02 15:42 (UTC) by kahgha)
Teamviewer ver 12 was not able to connect to computers with a newer version. I tried many different ways to install a fresh version, finally finding a solution (currently ver 15.3.2682):
- clone teamviewer repository: git clone https://aur.archlinux.org/teamviewer.git
- to enable Multilib package repository, uncomment the following two lines in pacman configuration file /etc/pacman.conf:
#[multilib]
#Include = /etc/pacman.d/mirrorlist
- cd teamviewer
- makepkg -si
- download older version of lib32-freetype2: curl -L -O https://archive.archlinux.org/packages/l/lib32-freetype2/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
- sudo pacman -U lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
- add lib32-freetype2 to IgnorePkgs in /etc/pacman.conf to make it not get updated during system update
- sudo systemctl enable gdm
- reboot
- restart teamviewer daemon: sudo systemctl restart teamviewerd
- sudo systemctl enable teamviewerd to make the daemon start at every boot
txtsd commented on 2020-03-31 13:21 (UTC)
@francoism90 Looks like it's the startx
issue. I'll just use teamviewer12.
francoism90 commented on 2020-03-31 12:44 (UTC)
@txtsd It works for me when first starting the service and launching using the terminal:
$ teamviewer
txtsd commented on 2020-03-31 11:32 (UTC)
I enabled the service and rebooted, but I'm still getting this:
λ teamviewer
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
And nothing happens.
francoism90 commented on 2020-03-29 14:58 (UTC)
Any idea why the launcher isn't working?
joseluisq commented on 2020-03-20 14:06 (UTC)
For newcomers, it is necessary to start the daemon process like @babaliaris said https://aur.archlinux.org/packages/teamviewer/#comment-734607
babaliaris commented on 2020-03-19 19:02 (UTC) (edited on 2020-03-19 19:04 (UTC) by babaliaris)
YOU NEED to enable the teamviewerd.service and then reboot your computer!!! Starting the service won't work for some reason, you must enable it and reboot. This is important!!!
sudo systemctl enable teamviewerd #end then reboot
emiliobadillio commented on 2020-03-17 13:44 (UTC)
Teamviewer said not ready until I logged into the website and added my machine as a trusted device. Then it allowed me to login to the application which made me add my device again as a trusted device. It took a while to figure this out so created an account here to help anyone who have this issue.
WFV commented on 2020-03-15 04:47 (UTC) (edited on 2020-03-16 14:04 (UTC) by WFV)
@ ArthurBorsboom repackage it with patch to correct teamviewerd.service
diff --unified --recursive --text package.orig/data/opt/teamviewer/tv_bin/script/teamviewerd.service package.new/data/opt/teamviewer/tv_bin/script/teamviewerd.service
--- package.orig/data/opt/teamviewer/tv_bin/script/teamviewerd.service 2020-02-14 17:03:22.000000000 -0800
+++ package.new/data/opt/teamviewer/tv_bin/script/teamviewerd.service 2020-03-14 19:57:00.038517745 -0700
@@ -6,7 +6,7 @@
[Service]
Type = forking
-PIDFile = /var/run/teamviewerd.pid
+PIDFile = /run/teamviewerd.pid
ExecStart = /opt/teamviewer/tv_bin/teamviewerd -d
Restart = on-abort
StartLimitInterval = 60
See Patching packages Wiki for details.
ferrvittorio commented on 2020-03-13 11:32 (UTC)
Hi, gui launches ok but cannot focus on any text field / button. Program running but cant do much. Thanks
ArthurBorsboom commented on 2020-03-10 12:54 (UTC)
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.
ijann commented on 2020-03-07 03:46 (UTC) (edited on 2020-03-07 04:42 (UTC) by ijann)
Hi, install this version teamviewer 15.3.2682-1, but when you want to select the text box to login I can't do it, it doesn't allow me to enter the focus of the text box, what is this about?
Solved, it was the service that didn't start it before: V
zangoku commented on 2020-02-29 21:04 (UTC)
Stuck on "teamviewer is starting please wait...". It used to work properly.
direc85 commented on 2020-02-26 20:46 (UTC)
@swiftgeek I created a patch:
https://direc.kapsi.fi/owncloud/s/xKFLyXa5UpRX6jT
It contains update for 15.3, update script for easier maintenance, better handling of teamviewerd.service and other, minor changes. Please have a look. Thanks!
vault commented on 2020-02-13 07:43 (UTC)
If Teamviewr write to you "Not ready. Please check your connection" close it, go to terminal and write this: sudo teamviewer --daemon enable And then run teamviewer. It will be work.
direc85 commented on 2020-02-06 20:28 (UTC)
For me at least, a simple version bump was needed for 15.2.2756 (with only amd64 tested, but all .deb files download OK at least). I could push the changes, but I'm not a maintainer. Would you like to perhaps add me? Thanks.
callmejoe commented on 2020-01-26 17:04 (UTC)
@annoyingduck, pw for sudo. i see. i forgot i edited my sudoers file so no pw needed for sudo. yes we do need a fix for this i agree
annoyingduck commented on 2020-01-26 16:15 (UTC)
@callmejoe the startup command you wrote to initiate at boot would require your root password to be entered. Has nothing to do with teamviewer itself. Hence, not a viable option if attempting to reboot via teamviewer. I'll still have no access because the daemon needs to be manually restarted via sudo. We need a solution for why the daemon needs a manual refire on every boot.
callmejoe commented on 2020-01-26 16:01 (UTC) (edited on 2020-01-26 16:02 (UTC) by callmejoe)
@annoyingduck, manual password? i dont ever have to enter one. i assigned all my devices to my TV account. i have all devices set up with the grant easy access option checked.
also, i've noticed checking "start tv with system" causes problems for me. probably more of a Windows option.
annoyingduck commented on 2020-01-26 13:33 (UTC)
@callmejoe, good thought, but that still invokes a manual password which can't be entered remotely because teamviewer cannot be accessed.
callmejoe commented on 2020-01-26 00:30 (UTC)
@annoyingduck i have xfce installed too. i just added sudo systemctl restart teamviewerd to the autostart apps.
annoyingduck commented on 2020-01-25 23:29 (UTC)
I've given up. I did the recommended permission change, removed every aspect of teamviewer and reinstalled. No matter what, after every boot I have to restart the daemon to get teamviewer to autostart and show credentials, stays stuck on starting teamviewer. Frustrating, because its a computer I update remotely, and if teamviewer needs to manually be triggered everytime, I can never remotely reboot. Running XFCE if that helps on all machines.
nurunet commented on 2020-01-25 11:30 (UTC)
The current Linux version (teamviewer 15.1.3937-1) will not connect to TeamViewer QuickSupport on Android devices - and does not give any helpful error message either. It works with the last Windows versions though. Very annoying.
I believe this used to work with TeamViewer 12...
FloatingRain commented on 2020-01-22 03:48 (UTC)
Maintainer should fix file access about /etc/teamviewer long time ago, why hasn't it been repaired until now?
el.Quero commented on 2020-01-09 18:09 (UTC)
Installed today, still says "Not Ready, Please check your connection".
Resolution is setting "/etc/teamviewer" and its subdirectories permissions to 775 with "chmod 2775 -R /etc/teamviewer.
Obviously the service must be restarted after this modification with "systemctl restart teamviewerd" or any equivalent command.
Please fix the package.
OvelixMax commented on 2019-12-25 07:45 (UTC)
Hi, may you fix the links? This three links give me error: 403 Forbidden.
<https://dl.tvcdn.de/download/linux/version_15x/teamviewer-host_15.1.3937_armhf.deb> (armv7h)
<https://dl.tvcdn.de/download/linux/version_15x/teamviewer_15.1.3937_amd64.deb> (x86_64)
<https://dl.tvcdn.de/download/linux/version_15x/teamviewer_15.1.3937_i386.deb> (i686)
j.taala commented on 2019-12-22 05:40 (UTC)
Hey swiftgeek, let me know if you could a hand keeping this up to date. Happy to be a contributor if it would help. Jay.
djb commented on 2019-12-19 12:19 (UTC)
fresh install of teamviewer_15, using i3wm.
starting teamviewer: Launching TeamViewer GUI ... no GUI is started, ID is 0
teamviewer info: Try restarting the TeamViewer daemon (e.g. teamviewer --daemon restart)
did sudo systemctl enable teamviewerd and start and restart a few times, nothing. teamviewerd is active and running but teamviewer doesn't recognize it. did not change the permissons yet, this should be done by the package?
Furthermore:
"ngoonee 2019-11-08 08:11
This package generates a broken symlink /usr/share/licenses/teamviewer/LICENSE which points to /opt/teamviewer/License.txt (which doesn't exist). Please fix"
for me still "broken"
"ferda 2019-11-09 15:13 Line 9 in /usr/lib/systemd/system/teamviewerd.service should be changed to PIDFile = /run/teamviewerd.pid in order to stop systemd from complaining about the PIDFile path."
for me PIDFile = /var/run/teamviewerd.pid and /var/run points to /run so should be ok?
Can you please adress this in a small package update? Thanks
serdarsaglam commented on 2019-12-16 16:11 (UTC) (edited on 2019-12-16 16:11 (UTC) by serdarsaglam)
Hi
Permanent solution: sudo systemctl enable teamviewerd
reboot
rhysperry111 commented on 2019-12-07 14:16 (UTC)
@callmejoe
I can confirm that restarting teamviewerd worked. I think that tip should be pinned @swiftgeek
afx commented on 2019-12-05 17:13 (UTC)
@steineklopfer
the permissions solved the issue for me. Thanks.
steineklopfer commented on 2019-12-04 10:37 (UTC)
@afx I used the permissions from buzo's comment (buzo commented on 2019-08-23 12:00) and also applied the same permissions to the file inside that folder.
A "systemctl restart teamviewerd" might also help
boustanihani commented on 2019-12-03 12:45 (UTC)
Teamviewer shows ready, but no ID and no password is generated :(
mdphoto commented on 2019-12-02 16:07 (UTC)
I have I3-wm I have a problem with the inactive field of login/psw i found à solution in terminal make sudo teamviewer setup and follow the instruction, next start teamviewer.
afx commented on 2019-11-27 22:43 (UTC)
Can confirm the same problem as PhotonX: "Not Ready, Please check your connection"
Also, regarding steineklopfer comment, what are the required permissions on /etc/teamviewer dir?
callmejoe commented on 2019-11-26 14:54 (UTC)
teamviewer15 client will not issue user id unless i restart teamviewerd.service even though that service does start at boot and is active (running).
titockmente commented on 2019-11-22 12:11 (UTC)
Tested patch suggested by operating for TeamViewer 15.0.8397 PKGBUILD file here:
operating commented on 2019-11-21 19:23 (UTC)
For version 15 to work, you have to alter PKGBUILD as so:
--- PKGBUILD 2019-11-21 20:11:40.300113773 +0100 +++ PKGBUILD.orig 2019-11-21 20:22:20.692722980 +0100 @@ -1,10 +1,10 @@ # Maintainer: Alex Taber <aft dot pokemon at gmail dot com>
pkgname=teamviewer -pkgver=15.0.8397 +pkgver=14.6.2452 pkgrel=1 pkgdesc='All-In-One Software for Remote Support and Online Meetings' -arch=('i686' 'x86_64') +arch=('i686' 'x86_64' 'armv7h') url='http://www.teamviewer.com' license=('custom') options=('!strip') @@ -29,13 +29,13 @@ #depends_i686=() #depends_armv7h=() install=teamviewer.install -source_x86_64=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.}x/teamviewer_${pkgver}_amd64.deb") -source_i686=("https://dl.teamviewer.com/download/linux/version_${pkgver%%.}x/teamviewer_${pkgver}i386.deb") -#source_armv7h=("https://dl.tvcdn.de/download/linux/version_${pkgver%%.}x/teamviewer-host_${pkgver}_armhf.deb") +source_x86_64=("https://dl.tvcdn.de/download/linux/version_${pkgver%%.}x/teamviewer${pkgver}amd64.deb") +source_i686=("https://dl.tvcdn.de/download/linux/version_${pkgver%%.}x/teamviewer_${pkgver}_i386.deb") +source_armv7h=("https://dl.tvcdn.de/download/linux/version_${pkgver%%.}x/teamviewer-host${pkgver}_armhf.deb") #source_armv7h=("https://dl.tvcdn.de/download/linux/version_${pkgver%%.*}x/teamviewer-host_13.2.13582_armhf.deb") -sha256sums_i686=('8a6cd9e685c18487d3238fd307042f5b551c71797af4353443d7a90ff4801390') -sha256sums_x86_64=('da98c868256613b082a4fa126cdd83088cbb11a85ab90f5852ebe27f29a72d2e') -#sha256sums_armv7h=('cc68e495598ea27a41e2d56bd01709468eec65777486fb1fb8aae58abc0acfb1') +sha256sums_i686=('d7d8cf4e5a3a9273c7b00c4d9be057e243643a0d1fc116ffd7c97e2859c4e97c') +sha256sums_x86_64=('1c2a70a6ad16c2c1b4da20b3ed7715ab59f5dac55ee99a945c9fd1cdf13ac748') +sha256sums_armv7h=('cc68e495598ea27a41e2d56bd01709468eec65777486fb1fb8aae58abc0acfb1')
prepare() { warning "If the install fails, you need to uninstall previous major version of Teamviewer"
test0 commented on 2019-11-21 08:33 (UTC)
Version 15.0.8397 has been released.
ferda commented on 2019-11-09 15:13 (UTC)
Line 9 in /usr/lib/systemd/system/teamviewerd.service should be changed to PIDFile = /run/teamviewerd.pid in order to stop systemd from complaining about the PIDFile path.
ngoonee commented on 2019-11-08 08:11 (UTC)
This package generates a broken symlink /usr/share/licenses/teamviewer/LICENSE which points to /opt/teamviewer/License.txt (which doesn't exist). Please fix
PhotonX commented on 2019-10-26 07:15 (UTC)
In my case it helped to set the DNS server to 1.1.1.1 rather than my router's local ip.
PhotonX commented on 2019-10-24 19:07 (UTC)
Same problem as supdroid here. Sounds like this issue: https://community.teamviewer.com/t5/Linux/teamviewer-14-no-connection-error-reason-2/td-p/60429
steineklopfer commented on 2019-10-24 09:16 (UTC)
Thanks for the tip with the permissions on the /etc/teamviewer dir! For me it started working again after I also changed permissions on the conf file inside.
johncrist1988 commented on 2019-08-23 14:20 (UTC)
Should it be able to run without root? In an ideal world, yes. But there's more going on that the daemon does (including what you've changed) and that's more of an upstream issue than an AUR issue.
buzo commented on 2019-08-23 12:03 (UTC)
bernd_b: Thanks, I didn't know that. But shouldn't it be possible to use it without a daemon running as root?
buzo commented on 2019-08-23 12:00 (UTC)
Oh well, I found it myself with a bit of strace-Debugging: Teamviewer needs write-access to the directory /etc/teamviewer. It writes a file global.conf there as well as some volatile files like teamviewerd.pid.
So I did sudo chgrp video /etc/teamviewer
and sudo chmod 2775 /etc/teamviewer
, and now it works. Could you please add some fix to the package?
bernd_b commented on 2019-08-23 11:56 (UTC)
Did you start the deamon first: systemctl start teamviewerd
buzo commented on 2019-08-23 11:31 (UTC) (edited on 2019-08-23 11:31 (UTC) by buzo)
I cannot get Teamviewer working. I added myself to the video group and rebooted already. The console output is:
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Starting network process (no daemon)
Network process already started (or error)
Launching TeamViewer GUI ...
… and the GUI contains the message: “Not ready. Please check your connection.”
But my Internet connection is working fine. Any ideas?
invidian commented on 2019-08-18 14:30 (UTC)
For everyone who don't wont to bloat their system with things like gdm, it seems that "nodm" https://wiki.archlinux.org/index.php/Nodm is a compact and non-intrusive way for getting latest version of Teamviewer to work.
itarill commented on 2019-08-02 06:53 (UTC)
I know it is not arch but Manjaro, nevertheless. After a clean Manjaro 18.0.4 install and update, installing this package via yay will result in the following messages and very slow boot:
"Started Network Manager Wait online" "Started TLP system startup/shutdown"
As well as networks unavailable on boot until suspend-wake.
Removing teamviewer solves the issue.
saitodisse commented on 2019-07-29 14:43 (UTC)
@pcfreak30 thank you very much. Same error here.
"Just a heads up. After a lot of troubleshooting, I found that I could not get a connection due to no access to framebuffer 0 at /dev/fb0. Adding my user to the video group and reloggging in fixed it.
If anyone is curious, I used strace -f on the standalone teamviewer package from their site and saw permission denied from a program loop running (a polling code likely).
Hope this helps anyone else save an hour or two :)."
fgk commented on 2019-07-28 18:32 (UTC) (edited on 2019-07-28 18:33 (UTC) by fgk)
"All-In-One Software for Remote Support and Online Meetings"
Online Meetings still not part of the Linux version of TeamViewer 14, so the description is misleading.
jonathon commented on 2019-06-22 23:50 (UTC)
@fabish fakeroot
is in both [core]
and base-devel
so shouldn't be added to depends
or makedepends
.
pcfreak30 commented on 2019-06-10 12:25 (UTC)
Just a heads up. After a lot of troubleshooting, I found that I could not get a connection due to no access to framebuffer 0 at /dev/fb0. Adding my user to the video group and reloggging in fixed it.
If anyone is curious, I used strace -f on the standalone teamviewer package from their site and saw permission denied from a program loop running (a polling code likely).
Hope this helps anyone else save an hour or two :).
fabiscafe commented on 2019-06-07 08:54 (UTC)
you're missing
makedepends=('fakeroot')
and it would be nice if you would check for the the teamviewer service at uninstallation time. Because they always leave something behind in the system that is really annoying.
and remove it post remove.
Also
echo "Execute 'sudo systemctl enable teamviewerd' in a terminal."
would maybe better with
echo "Execute 'systemctl enable --now teamviewerd' in a terminal."
because sudo is optional in arch, systemctl makes use of polkit by default (thats not optional, because systemd). also --now, so the service is started, not just enabled.
So in Short
post_install() {
echo "The Teamviewer service must be running for Teamviewer to work."
echo "Execute 'systemctl enable --now teamviewerd' in a terminal."
}
post_upgrade() {
post_install
}
pre_remove() {
# Check for active teamviewer services and stop them
if systemctl is-active --quiet teamviewerd.service ; then {
systemctl stop teamviewerd.service
}
fi
# Check for enabled teamviewer services and disable them
if systemctl is-enabled --quiet teamviewerd.service ; then {
systemctl disable teamviewerd.service
}
fi
}
post_remove() {
if [ -d '/opt/teamviewer' ]; then {
rm -rf '/opt/teamviewer'
}
fi
}
# vim: ts=2 sw=2 et:
Lttlwing16 commented on 2019-06-05 00:54 (UTC)
Having an issue on the latest build where if the resolution is set to the native resolution of the host (1366 x768), the inputs from the client register on the host, but the screen doesn't refresh on the client. The client screen remains static, except for a couple flickers in the banner of the teamviewer card. This issue is remedied by lowering the resolution 1280 x 720 on the client settings.
I have uninstalled, rebooted, re-installed, disabled, enabled etc etc.
dhameoin commented on 2019-05-27 12:17 (UTC)
Where is Teamviewer 13 ?
jose1711 commented on 2019-05-15 10:36 (UTC)
@samyc
since when is KDE a light-weight DE? :-) i was thinking iceWM, i3 or the-likes..
samyc commented on 2019-05-15 10:30 (UTC)
Working perfectly on Antergos kernel 5.0.10-arch1-1-ARCH with KDE Plasma 5.15.4 Just make sure the teamviewer daemon is running before launching the GUI with /usr/bin/teamviewer
Check it with sudo systemctl status teamviewerd dubbelcheck with ps aux | grep teamviewerd
Start it with sudo systemctl start teamviewerd or with /opt/teamviewer/tv_bin/teamviewerd -d
jose1711 commented on 2019-05-14 18:29 (UTC)
if you're on a light-weight window manager consider using google-chrome + teamviewer app as an alternative to this
magenbrot commented on 2019-05-06 13:07 (UTC)
Systemd complains about an deprecated path, can you update the unit file? Here's the message:
systemd[1]: /usr/lib/systemd/system/teamviewerd.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid; please update the unit file accordingly.
skerit commented on 2019-04-27 13:43 (UTC) (edited on 2019-04-27 13:46 (UTC) by skerit)
I was unable to login using Teamviewer 14: the actual "e-mail" and "password" input fields aren't focusable, you can't even tab to them.
Turns out it was because I still had to enable & start the "teamviewerd" systemd service. After I did that, it started working.
Hubro commented on 2019-04-24 10:02 (UTC)
I'm on a relatively fresh Arch install (a week old maybe) and teamviewer crashes immediately when I try to run it. No GUI shows up. I'm using xinit and i3, kernel 5.0.8-arch1-1-ARCH. I have started the teamviewer daemon. I have tried both teamviewer and teamviewer-beta.
Anybody else experience this?
$ teamviewer
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
Aborted (core dumped)
t0m5k1 commented on 2019-04-19 09:30 (UTC)
@keybreak Try a different wrapper! Yaourt is old, unmaintained and depreciated.
keybreak commented on 2019-04-18 08:46 (UTC) (edited on 2019-04-18 08:52 (UTC) by keybreak)
Please fix it, something is wrong while accessing your package:
yaourt -Si "teamviewer"
/dev/fd/63: line 4: unexpected EOF while looking for matching `)'
Wonder what the hell it have to do with /dev/fd though)
dylanmtaylor commented on 2019-04-14 18:57 (UTC)
This is still out of date more than a month later. 14.2.2558 is the latest as seen on https://www.teamviewer.com/en/download/linux/ - is there a repo on GitHub or something that takes pull requests? I'd be willing to do the work to try to bring this up to date.
wookietreiber commented on 2019-04-01 16:33 (UTC)
I get this message after starting the service:
/usr/lib/systemd/system/teamviewerd.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/teamviewerd.pid → /run/teamviewerd.pid; please update the unit file accordingly.
Please patch the service file.
ivanx006 commented on 2019-03-04 09:31 (UTC)
teamviewer 14 close on random with the following error running kde plasma
write(2, "The X11 connection broke (error "..., 60) = 60 futex(0x7fd7bc000020, FUTEX_WAIT_PRIVATE, 2, NULL) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} --- +++ killed by SIGALRM +++ Alarm clock
ragouel commented on 2019-02-16 04:02 (UTC)
Every version of TeamViewer in here, either won't start at all or fails to install. Does anyone use TeamViewer anymore ?
sikmir commented on 2019-02-14 21:14 (UTC)
Trying to run teamviewer, but nothing happens (no GUI):
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
teamviewerd service is up and running.
PhiLosove commented on 2019-02-08 20:39 (UTC)
After AUR-install teamviewer, you have to type "sudo systemctl enable teamviewerd" and then "sudo systemctl start teamviewerd". You can check always teamviewer status with "sudo systemctl status teamviewerd".
Taijian commented on 2019-01-27 16:57 (UTC)
@pete910: Well, this is Arch, so of course .service files do not get auto-enabled/started by AUR-packages. They really shouldn't be, that's for the user to decide! Also, the install script literally tells you this post install!
pete910 commented on 2019-01-27 15:22 (UTC)
teamviewer.service requires manual activation after install. Wont connect to servers until started.
This also stops the ID and pass assignment for non commercial users
severach commented on 2019-01-15 02:44 (UTC)
Download them then look in your download history for where they come from. download.teamviewer.com redirects to tvcdn.de.
doctorzeus commented on 2019-01-14 22:32 (UTC)
Why is this grabbing the bins from tvcdn.de and not download.teamviewer.com?
evilside commented on 2019-01-13 16:38 (UTC) (edited on 2019-01-13 16:45 (UTC) by evilside)
I have Corporate license of Teamviewer with mobile devices support. From Arch I can't connect to Android/Apple devices, the connection is closed immediately and not show anything. From Ubuntu it working correctly.
Note: It occur the same with the 13 version. I did hope with the new version is resolved, but not.
WFV commented on 2019-01-12 21:27 (UTC)
I edited /usr/lib/systemd/system/teamviewerd.service PID= to clear systemctl complaints about having to symlink /var/run/... to /run/... but still get this "teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: No such file or directory" even though TeamViewer (14) loads without issue. Just curious, is it just a timing thing, e.g.(yet?)? Thanks
severach commented on 2019-01-12 05:41 (UTC)
I had that happen a few versions ago. Switch from deb to rpm usually fixed it. Try teamviewer-beta where it's easy to switch.
szsong commented on 2019-01-12 04:49 (UTC)
Yes EULA pops out every single time. To make it worse, the GUI says "Not ready. Please check your connection"
thisischrys commented on 2019-01-08 11:51 (UTC)
Anyone else having issues with the EULA popping up asking for agreeing every single time?
amitavmohanty01 commented on 2019-01-05 19:11 (UTC)
When I start teamviewer, I get the following error.
CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Starting network process (no daemon) Network process already started (or error)
TV gets stuck with a message about checking the network. The process also does not close properly. It coredumps.
Stack trace of thread 7136:
#0 0x00000000f7ed9dd9 __kernel_vsyscall (linux-gate.so.1)
#1 0x00000000f7b90082 raise (libc.so.6)
#2 0x00000000f7b7a364 abort (libc.so.6)
#3 0x00000000086d7755 n/a (teamviewerd)
#4 0x00000000086cc0e3 n/a (teamviewerd)
#5 0x00000000086cc13d n/a (teamviewerd)
#6 0x00000000080ad400 n/a (teamviewerd)
#7 0x0000000008419e08 n/a (teamviewerd)
#8 0x0000000008419e41 n/a (teamviewerd)
#9 0x0000000008419ebc n/a (teamviewerd)
#10 0x00000000f7b927e0 __run_exit_handlers (libc.so.6)
#11 0x00000000f7b92901 exit (libc.so.6)
#12 0x00000000f7b7bb4d __libc_start_main (libc.so.6)
#13 0x00000000080a4ffd n/a (teamviewerd)
maximbaz commented on 2019-01-04 10:17 (UTC)
swiftgeek: remember to reset pkgrel
every time you update the version (now is too late, but do this next time pkgver
changes).
gyurman commented on 2018-12-12 18:19 (UTC)
teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid
taifunbrowser commented on 2018-12-07 22:14 (UTC)
As mentioned before by ask6155 and m1cr0man, libnss-resolver should be marked by a dependency, or at least we need a pinned comment mentioning that such a resolver must be installed to allow it to get a green light and connect.
t0m5k1 commented on 2018-11-23 14:40 (UTC)
@dschaefer79
This is not a teamviewer issue but a yaourt one. Post in the relevant place.
dbermond commented on 2018-11-23 10:51 (UTC)
@swiftgeek You are keeping pkgrel at 9 in each new release version. It should be reseted to 1 when a new version is released.
dschaefer79 commented on 2018-11-16 09:10 (UTC)
at the end of install I have this.
/usr/lib/yaourt/aur.sh: line 211: cd: /root: Permission denied
Can someone help me ?
Thanks
Elrondo46 commented on 2018-11-16 07:00 (UTC)
For auto service at start you can do that:
- Shell script: https://pastebin.com/JwiWXsH5 (for pkexec)
- Modify the PKGBUILD and add this: https://pastebin.com/uDV1q3xq (in end of PKGBUILD after the condition)
xnopasaranx commented on 2018-11-15 14:10 (UTC)
I was having massive problems with the package (I am using i3wm). It would install and update no problem but suddenly I was not able to log in anymore with our company account. The credentials fields were greyed out, but no connection problems were reported. Today I stumbled upon a stackoverflow that suggested installing libnss-resolver and that fixed my problem immediately after restarting the teamviewerd service. Could this be made a recommendation/dependency or maybe included as a troubleshooting tipp?
swiftgeek commented on 2018-10-26 07:34 (UTC) (edited on 2020-06-23 14:30 (UTC) by swiftgeek)
Go to teamviewer-beta for beta/preview releases
closingin commented on 2018-10-25 10:36 (UTC)
Hello, I don't understand why you recommend in the install script to enable the teamviewerd service at boot when it just has to be running for teamviewer to work. That's not really a problem as it's just a recommendation, but I think you should change the command to "sudo systemctl start teamviewerd.service" instead of "enable", to stay consistent with the associated message.
FFY00 commented on 2018-10-24 21:57 (UTC)
Please remove the conflicts with teamviewer-beta, that package should be the one conflicting with this one.
DuBistKomisch commented on 2018-10-18 00:12 (UTC)
+1 to xuanwo's comment, I don't have NetworkManager installed so I can't start the teamviewerd service at all without editing it
requiring lightdm was bad enough, hopefully we don't need to start installing NetworkMangler too!
z3ntu commented on 2018-10-17 20:38 (UTC)
You should reset the pkgrel to 1 with the next pkgver bump
swiftgeek commented on 2018-10-17 14:05 (UTC)
https://community.teamviewer.com/t5/Linux/Update-13-2-13582-Summer-release/td-p/40607
13.2.26559 is first nonpreview version
xuanwo commented on 2018-10-17 08:34 (UTC) (edited on 2018-10-17 08:35 (UTC) by xuanwo)
teamviewerd's service will introduce NetworkManager-wait-online.service
which results in systemd tried to start NetworkManager and netctl
users had network issues after that.
In order to solve this problem, we should:
Firstly, mask network related service
systemctk mask NetworkManager-wait-online.service
systemctk mask NetworkManager-dispatcher.service
systemctk mask NetworkManager.service
Then edit the teamviewerd.service: systemctl edit teamviewerd.service
[Unit]
After=network.target network-online.target dbus.service
Wants=network-online.target
GeorgeRaven commented on 2018-10-15 15:41 (UTC)
I have found I require lib32-freetype2 archive package to start teamviewer on boot even after enabling teamviewd service using systemctl. The steps taken to get this to work on boot are those proposed by Telis80s answer. Although in the same thread it is suggested this is not necessary yet I have not found another working solution without these 32bit libs.
dschaefer79 commented on 2018-10-15 09:12 (UTC)
systemctl status teamviewerd.service
oct 15 09:17:58 revopc systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: No such file or directory
What can I do about this error ??
t0m5k1 commented on 2018-10-12 11:33 (UTC)
@Sven,
You don't have to enable the service just start it: systemctl start teamviewerd.service Then when you have finished run: systemctl stop teamviewerd.service
You only need to run the enable if you do want it running constantly in the background
svrmirac commented on 2018-10-12 09:36 (UTC)
Thanks @Sven!
Sven commented on 2018-10-12 01:00 (UTC) (edited on 2018-10-12 01:01 (UTC) by Sven)
Why do I have to enable teamviewerd.service? I don't want a teamviewer service running all the time. I want to use teamviewer solely as an app to remote control other machines. I want to use teamviewer as an app that I start and terminate whenever I please.
Currently, I download the official tgz, unpack it, and run the teamviewer executable. That's it. No systemd services, nothing running in the background.
swiftgeek commented on 2018-10-09 21:55 (UTC)
@tomacrisan while i apprieciate links i don't see a mention of it in https://community.teamviewer.com/t5/Linux/bd-p/Linux or download page
Perhaps teamviewer-beta
would be better for such inside previews?
pezcurrel commented on 2018-10-08 15:19 (UTC) (edited on 2018-10-08 15:24 (UTC) by pezcurrel)
nx345 perhaps the window shows almost offscreen, with just the upper-left corner showing in the lower-right corner of the screen, like it happens to me on a notebook with hidpi screen - I have not this problem on a desktop pc with fhd screen. On the notebook I manage to bring the window to the center of screen by dragging the corner up and left to resize the window a bit and then grabbing the top bar and dragging the window to the center of the screen.
tomacrisan commented on 2018-10-08 14:31 (UTC) (edited on 2018-10-08 14:36 (UTC) by tomacrisan)
nx345 commented on 2018-09-27 21:09 (UTC)
When launching it I have this :
Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ...
Nothing shows up, so it is not working.
I have of course enabled systemctl enable teamviewerd.service
joaodalvi commented on 2018-09-11 18:45 (UTC)
For those with problems regarding not connecting on your teamviewer 13. No need for 32 bit libs. Problem is you have to enable and start teamviewerd.service with systemctl. Just run the following as root:
systemctl enable teamviewerd.service
systemctl start teamviewerd.service
And than start teamviewer again, you should be able to connect normally. Package sumbitter could maybe include this info in a fixed post as there probably are other people affected by the same issue.
erkexzcx commented on 2018-09-02 20:24 (UTC)
Getting core dumped. 99% sure it needs some lib32 libraries from multilib repo. teamviewer12 works just fine.
tomacrisan commented on 2018-08-11 18:44 (UTC)
Regarding a previous comment I made, it is a case of not thinking first before posting. This AUR version works fine; I just needed to enable the teamviewerd service.
tomacrisan commented on 2018-08-11 18:26 (UTC)
I have been having trouble getting both versions v13.1.8286 and 13.2.13582 to connect when I use the .deb files. I do have nss-mdns installed.
When installing manually from the tar.xz files, the default teamviewer connects immediately without issues.
https://dl.tvcdn.de/download/linux/version_13x/teamviewer-host_13.2.13582_armhf.tar.xz (armv7h) https://dl.tvcdn.de/download/linux/version_13x/teamviewer_13.2.13582_amd64.tar.xz (x86_64) https://dl.tvcdn.de/download/linux/version_13x/teamviewer_13.2.13582_i386.tar.xz (i686)
I haven't determined why this is but thought I would post the information in case it is useful to others.
swiftgeek commented on 2018-08-09 15:08 (UTC)
If you are flagging package out of date make sure it's actually available for download (eg. as of right now 8286 is the newest one)
https://dl.tvcdn.de/download/linux/version_13x/ is 403 forbidden so i can't just list all the versions available
m1cr0man commented on 2018-07-25 21:12 (UTC)
Same as ask6155 - had to install nss-mdns before the "Not Ready" message/red light went away.
ask6155 commented on 2018-07-24 11:34 (UTC)
Hey I installed Teamviewer and it booted properly but it said it cannot connect (Check the connection) after like 20 mins on forums I found out it requires libnss-resolver to work. can you add that to the dependencies?
NicoLiendo commented on 2018-07-23 20:31 (UTC)
No matter what I do, I get this message: Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ... Aborted (`core' dump)
severach commented on 2018-06-07 03:29 (UTC)
I was also unable to control a mobile device. I had to use Teamviewer Windows.
evilside commented on 2018-06-06 20:39 (UTC) (edited on 2018-06-06 20:43 (UTC) by evilside)
I use my licensed account and I can't connect to mobile devices for controlling them.
swiftgeek commented on 2018-06-06 12:17 (UTC)
Removed libdepend on x86_64, report issues related to that if they happen
kmahyyg commented on 2018-05-26 08:12 (UTC)
Please add a pid file to /var/run/teamviewerd.pid , without this file, the service may be not started.
stifi commented on 2018-05-23 11:16 (UTC)
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.
evgeniydoronin commented on 2018-05-01 14:18 (UTC) (edited on 2018-05-01 14:19 (UTC) by evgeniydoronin)
1) $ teamviewer daemon status
if disable
2) $ teamviewer daemon start
then start app
alpha0x00 commented on 2018-04-28 13:53 (UTC) (edited on 2018-04-28 13:54 (UTC) by alpha0x00)
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
.
Xiaomu commented on 2018-04-28 09:27 (UTC)
Need to start teamviewerd first, and then everything's fine : )
Taijian commented on 2018-04-22 07:36 (UTC)
@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.
fabiscafe commented on 2018-04-22 00:14 (UTC)
@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.
annoyingduck commented on 2018-04-16 15:18 (UTC)
@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.
Pietro_Pizzi commented on 2018-04-16 14:11 (UTC)
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).
tuva_men commented on 2018-04-12 15:54 (UTC)
TV13 works only with lightdm, in sddm it works "partially". Now I need to figure out how to undo the hell in TV12 with downgrading and installing lib32-freetype2 and lib32-dbus
the-k commented on 2018-04-09 07:44 (UTC)
Please, remove the 32 bit dependencies, it works just fine without them.
Utini commented on 2018-04-08 15:58 (UTC)
Problem for me is that as soon as I connect with my client, my servers user will log out of GNOME. And then teamviewer server will go offline.
Any ideas?
maximbaz commented on 2018-04-05 12:42 (UTC)
This is because the current PKGBUILD declares them in the dependencies section - when I installed teamviewer, I modified PKGBUILD and deleted all lib32-
entries from there.
annoyingduck commented on 2018-04-05 12:40 (UTC)
When I attempt to remove the multilib repo per the Arch Wiki I keep getting errors when executing the "pacman -R $(paclist multilib | cut -f1 -d' ')" command stating that Teamviewer still requires all these packages, which is where my original confusion came from.
maximbaz commented on 2018-04-05 12:25 (UTC)
It works without 32bit dependencies just fine, for me it was the whole point of updating to teamviewer 13 to finally get rid of 32bit repo.
annoyingduck commented on 2018-04-05 12:21 (UTC)
I've updated 3 machines from 12 to 13 here and everything is working fine for me (I use a display manager). I'm just a bit unclear on whether or not I can remove my 32bit dependencies at this time or if they still need to be there. I only added in the Arch 32bit repo for this program specifically. Is it now safe to remove the 32bit repo if it was only used for Teamviewer?
swiftgeek commented on 2018-04-05 09:01 (UTC) (edited on 2018-04-05 09:12 (UTC) by swiftgeek)
They are there for /opt/teamviewer/tv_bin/script/libdepend, I'm not sure whether it could be safely removed. Best to be reported to teamviewer as it indeed looks like some kind of leftover from tv12.
at least teamviewer_setup checklibs
seems to work fine without libdepend
maximbaz commented on 2018-04-05 08:45 (UTC)
@swiftgeek lib32 dependencies seem to be useless, and teamviewer works without them just fine.
seyn6gk commented on 2018-04-05 08:27 (UTC)
shmakky commented on 2018-04-05 08:13 (UTC)
Hello, can you create teamviewer12 package with latest 12 version, please, or how can I roll back to version 12? Licence between 12 and 13 version are not compatible. :-(
seyn6gk commented on 2018-04-05 08:00 (UTC)
All 32/64 bit dependencies are satisfied. but it still won't work with teamviewer 13 if X started with startx.
swiftgeek commented on 2018-04-05 07:42 (UTC) (edited on 2018-04-05 08:26 (UTC) by swiftgeek)
This could come handy. It seems to list dependencies per TV component (TV_DMN, TV_DESK, TV_GUI)
/opt/teamviewer/tv_bin/script/teamviewer_setup checklibs
QuickControls detection should rely on /usr/lib/qt/qml/QtQuick/Controls/qmldir
in archlinux
EDIT: Added it to prepare(), to be double sure that all dependencies are satisfied
seyn6gk commented on 2018-04-05 07:26 (UTC)
WARNING!
teamviewer 13 requires a desktop environment or login with lightdm etc, with startx it won't work, the staff of teamviewer confirmed, startx feature won't come in this year, it seems reverting back to teamviewer 12 is the only option for startx folks.
swiftgeek commented on 2018-04-05 06:19 (UTC) (edited on 2018-04-05 06:20 (UTC) by swiftgeek)
Start from removing your settings (like ~/.config/teamview ~/.local/share/teamview /etc/teamviewer), as i cannot reproduce this here
severach commented on 2018-04-05 02:51 (UTC) (edited on 2018-04-05 02:52 (UTC) by severach)
The "license agreement" problem is because the deb version is no good. Switch to the RPM version with my script.
I also had to downgrade to 13.0.9865. 13.1.3026 hangs after about a half hour of use.
yochananmarqos commented on 2018-04-05 02:28 (UTC)
I have to accept the license agreement every time I open it. Also, it says, "Not ready. Please check your internet connection." There's nothing wrong with my connection. I never had this issue on v12.
DuBistKomisch commented on 2018-04-05 02:21 (UTC)
Package doesn't work.
Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Starting network process (no daemon) Network process already started (or error) Launching TeamViewer GUI ...
And then the process silently exits. This was also what happened on the beta package, I've never had 13 work. 12 worked fine though. What's going on?
vdemin commented on 2018-04-04 19:23 (UTC)
@swiftgeek Thanks for the support! Please reset the pkgrel to 1 when you upgrade to a new version: https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel
Elrondo46 commented on 2018-04-04 12:11 (UTC)
Dependency problem, forgot: qt5-quickcontrols
scorpionzezz commented on 2018-04-04 11:56 (UTC)
I even not able to run it after update it. How to downgrade it?
blackhole commented on 2018-04-04 10:20 (UTC)
I already switched back to v12 since this is not working with free license
ArthurBorsboom commented on 2018-04-04 10:19 (UTC)
lib32-qt4 ??
xsmile commented on 2018-04-04 09:44 (UTC) (edited on 2018-04-04 09:46 (UTC) by xsmile)
32-bit libraries are not a requirement, see the package teamviewer-beta.
In my opinion you should keep it at v12 as long as the Linux version is marked as a preview.
swiftgeek commented on 2018-04-04 09:22 (UTC) (edited on 2018-04-04 09:32 (UTC) by swiftgeek)
Elrondo46: edit button exists, and never forget to state architecture. Added for loop to deal with the differences between source files
Elrondo46 commented on 2018-04-04 09:16 (UTC)
data.tar.bz2 does not exist in the deb package. Please remove reference to and and it's full functionnal
Elrondo46 commented on 2018-04-04 09:14 (UTC)
Your package is BROKEN
swiftgeek commented on 2018-04-04 08:58 (UTC)
Due to recent issues and lack of updates on 12.x for linux (windows still gets them) I have bumped it to 13.1.x, and since armv7h is just released only partially i included -host version for it - it will be replaced by full teamviewer as soon as it's available.
t0m5k1 commented on 2018-03-31 14:10 (UTC)
@annoyingduck Same issue here in Awesomewm, i3, elementary too.
If I try to close the main window it is just minimized and also no systray icon & the close to tray option in advanced is not functional.
TV13 FYI:
Latest teamviewer13: https://aur.archlinux.org/packages/teamviewer13/
teamviewerbeta: https://aur.archlinux.org/packages/teamviewer-beta/
t0m5k1 commented on 2018-03-31 14:00 (UTC)
@cereberus: Pacman will not remove configurations that the application itself creates (for example "dotfiles" in the home folder).
cereberus commented on 2018-03-31 10:55 (UTC) (edited on 2018-03-31 10:58 (UTC) by cereberus)
Teamviewer v. 12 wouldn't start on my Arch (lightdm and openbox). "Launching TeamViewer GUI ..." appeared in terminal but nothing happened (no window was opened).
Then I installed the beta version (i.e., v. 13; https://community.teamviewer.com/t5/Linux/teamviewer-12-for-linux-antergos-no-opening/m-p/23711#M1090 -- not concerning Arch per se, but it inspired me to give v. 13 a try):
yaourt -S --force teamviewer-beta (https://aur.archlinux.org/packages/teamviewer-beta/)
I used --force
to overwrite teamviewer files as simple pacman -R teamviewer
didn't remove these files, I don't know why.
Afterwards I enabled and started teamviewerd (https://bbs.archlinux.org/viewtopic.php?id=154171) with these two commands:
systemctl enable teamviewerd
systemctl start teamviewerd
Now verything works like a charm (maybe except from displaying password but it's a minor issue: https://imgur.com/a/cKS8p).
annoyingduck commented on 2018-03-28 21:13 (UTC)
On one of my machines I had a small amount of updates. These are all of the packages that got updated, so it's one of these packages that breaks the tray icon in Teamviewer12: git, lib32-fontconfig, lib32-glib2, libwacom, lightdm, lightdm-gtk-greeter, python2-dateutil, tzdata, vala.
Again here I'm running XFCE. Result is the exact same on another one of my machines running Cinnamon. Before I mess with downgrading individual packages, I figured I'd share here to get some advice first on where to start. I gotta say, this open window over the tray icon is very annoying!
Cxpher commented on 2018-03-26 07:25 (UTC)
@annoyingduck
I have the exact same issue on GNOME 3.28 (worked fine with GNOME 3.26).
I suspect some updates unrelated to the DE caused the issue. Probably some python multilib packages.
annoyingduck commented on 2018-03-25 20:05 (UTC) (edited on 2018-03-25 20:12 (UTC) by annoyingduck)
Just did a system upgrade, and now the Teamviewer panel icon no longer appears in my notification area and the full running application window appears (which it did not before unless I called upon it). I can only minimize the window, but cannot remove it the window without fully shutting down the service. Running XFCE. Did this happen to anyone else? All settings are correct (aka minimize to panel/etc).
Update: "Close To Tray Menu" is no longer clickable in Advanced Settings. Option is enabled, but I cannot click it or interact with that setting.
severach commented on 2018-03-19 17:31 (UTC)
Teamviewer Host is updated to 13.1.1548 but Teamviewer is still at 13.0.9865 preview.
bernd_b commented on 2018-03-19 16:34 (UTC)
The latest version of Teamviever 12 is 12.0.90041, so why do people flag this package out of date?
bernd_b commented on 2018-03-19 16:31 (UTC)
Teamviewer 13 for Linux (current version 13.0.9865) definitely still lacks some features, e.g. video/audio call. So it may not be beta, but it is still a preview.
JannF commented on 2018-03-19 08:12 (UTC)
according to the changelog: https://www.teamviewer.com/en/download/changelog/
Teamviewer 13 is not beta anymore, seems rather to be an outdated download website. I also think that the preview tag rather refers to the ability to preview the new UI.
Latest version number is 13.1.1548
rc0r commented on 2018-03-07 07:56 (UTC)
Patch for PKGBUILD to install Teamviewer 13.0.9865:
https://gist.github.com/rc0r/09845303662931420da6bb78799a0ef7
Enjoy!
rc0r
t0m5k1 commented on 2018-02-15 18:30 (UTC)
@Swiftgeek
Just wanted to thank you for providing this package on the AUR. I know sometimes it is a thankless task but you're doing a great job.
swiftgeek commented on 2018-02-15 15:54 (UTC)
@scan thanks
scan commented on 2018-02-15 14:42 (UTC)
Release: v12.0.90041
Angel_Caido commented on 2018-02-11 01:39 (UTC)
My bad. I stand corrected. I spoke too soon. ^_^
severach commented on 2018-02-09 05:53 (UTC)
There are no download links and 5693 is older than the preview 6634
xgdgsc commented on 2018-02-09 05:48 (UTC)
https://www.teamviewer.com/en/download/changelog/ click linux on this page and Version 13.0.5693 is the latest.
Strit commented on 2018-02-08 05:14 (UTC)
@Angel_Caido Nope. Still preview: https://www.teamviewer.com/en/download/linux/
Angel_Caido commented on 2018-02-08 02:59 (UTC)
Teamviewer has upgraded its Linux version to 13.
pschichtel commented on 2018-02-04 02:35 (UTC)
The lib32-dbus dependency would be great
t0m5k1 commented on 2018-01-17 12:46 (UTC) (edited on 2018-01-17 12:47 (UTC) by t0m5k1)
@gibbz
It's here: https://aur.archlinux.org/packages/teamviewer-beta/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gibbz commented on 2018-01-16 23:59 (UTC)
any eta on when this will be switch to version 13?
swiftgeek commented on 2018-01-10 12:24 (UTC) (edited on 2018-01-10 12:26 (UTC) by swiftgeek)
@ido or you could simply use https://aur.archlinux.org/packages/teamviewer-beta/ Last changelog entry for linux mentions fixed security issues, so feel free to test it :)
ido commented on 2018-01-10 10:45 (UTC)
@swiftgeek Maybe you should update to the Preview v13 anyway? There are interoperability issues with v13 on Windows/Mac (which is not preview on those platforms). You could rename this to a "teamviewer12" package.
t0m5k1 commented on 2018-01-02 11:35 (UTC) (edited on 2018-01-02 11:37 (UTC) by t0m5k1)
Is this the first port of call for TV lol
v13 is here: https://aur.archlinux.org/packages/teamviewer-beta/
When TV themselves call it stable you will probably see this one updated or a new aur page started as many have not moved to v13 and some still want older versions for their own reasons.
Also check the stickied post up top.
francoism90 commented on 2018-01-02 10:59 (UTC)
@square252: https://www.teamviewer.com/en/download/linux/ - still states preview.
square252 commented on 2018-01-02 07:18 (UTC)
Well, time to update the package. The stable Linux reached V. 13.0.5693 meanwhile... (Stable 13 for Linux is out for some time now)
aptx commented on 2017-12-30 15:40 (UTC)
Is there a way to use the package without running a proprietary binary as root? In older versions (manually installed from the home page) it was possible to just execute teamviewer as unprivileged user. Is this no longer possible or is that only a problem with this package?
francoism90 commented on 2017-12-16 15:54 (UTC)
@t0m5k1 Yeah, but it isn't a warning, you're unable to connect when using TV12.
If you want to upgrade, there is already a package called teamviewer-beta. ;)
t0m5k1 commented on 2017-12-16 15:39 (UTC)
@francoism90
I get the warning too that's why I don't understand why people are pushing for TV13.
This page is still for TV12, I'd say if you want TV13 whilst it is beta/preview for linux make your own aur for it.
francoism90 commented on 2017-12-15 10:13 (UTC) (edited on 2017-12-15 10:14 (UTC) by francoism90)
@all Don't upgrade/install TV 13 on a Window-machine, you'll be unable to login from your Linux box if this runs v12. :/
.. Or is it just me getting the incompatible warning?
Strit commented on 2017-12-12 11:34 (UTC)
@pauldotknopf No it's not. It's in Preview state still. Windows got version 13. Linux, not yet.
pauldotknopf commented on 2017-12-11 05:20 (UTC)
TeamViewer 13 is here! Let's get this package updated!
beliys commented on 2017-12-09 10:45 (UTC)
pls update package
commented on 2017-12-06 20:41 (UTC)
@jacobtey: you must start teamviewer with "/opt/teamviewer/teamviewer_helper"
this script copy teamviewer to your homefolder to excute it from there.
t0m5k1 commented on 2017-12-06 18:55 (UTC) (edited on 2017-12-06 18:58 (UTC) by t0m5k1)
I take it this version is still having issues with lib32-freetype2 and requires lib32-dbus?
Or is this now a discussion board for version TV13 ?
jacobtey commented on 2017-12-06 11:51 (UTC) (edited on 2017-12-06 12:07 (UTC) by jacobtey)
john.smith wrote: "Here is a PKGBUILD for 13.0.5494, 64-bit that does not need root or a running service: https://ghostbin.com/paste/d6nm2 Can someone create this new package for the AUR?"
Init...
CheckCPU: SSE2 support: yes
Checking setup...
chmod: changing permissions of '/opt/teamviewer/config': Operation not permitted
chmod: changing permissions of '/opt/teamviewer/logfiles': Operation not permitted
/opt/teamviewer/tv_bin/script/tvw_profile: line 48: /opt/teamviewer/teamviewer.desktop: Permission denied
Error: InitProfile failed. Please check '/opt/teamviewer/logfiles/startup.log'
neeko commented on 2017-12-06 09:59 (UTC)
Somehow v13 just does not launch the GUI. Anyone else got it working?
gbcbooks commented on 2017-12-06 09:27 (UTC)
it is depend on lib32-dbus too , if you are on 64bit , dont forget yaourt -S lib32-dbus
then you can start teamveiwer
commented on 2017-12-05 21:07 (UTC)
Here is a PKGBUILD for 13.0.5494, 64-bit that does not need root or a running service: https://ghostbin.com/paste/d6nm2 Can someone create this new package for the AUR?
xsmile commented on 2017-12-05 13:49 (UTC) (edited on 2017-12-05 13:50 (UTC) by xsmile)
PKGBUILD for 13.0.5494, 64-bit: https://ghostbin.com/paste/dpy5y.
I don't understand the release status descriptions - is this a final version of the preview?
jeyhunn commented on 2017-12-05 08:44 (UTC)
@swiftgeek, Teamviewer 13 also has severe release notes:
- Native client, no more Wine (QT5 application now)
- Native 64 bit packages, no more 32 bit dependencies
You have to have a look dependencies: https://community.teamviewer.com/t5/Linux/Update-TeamViewer-13/td-p/24537
shizonic commented on 2017-12-05 06:33 (UTC)
@swiftgeek
now version 13 is really available for linux - not only the host-only preview !
have look at this: https://www.teamviewer.com/de/download/linux/
Xaekai commented on 2017-12-04 19:45 (UTC) (edited on 2017-12-04 20:07 (UTC) by Xaekai)
Seems to be out as stable now. Version 13.0.5494.
https://dl.tvcdn.de/download/linux/version_13x/teamviewer_13.0.5494_amd64.deb
The URL scheme seems to have changed. The have added /linux to the path. They also seem to have added auto latest version string insertion to the redirect. If you curl -I https://download.teamviewer.com/download/linux/version_13x/teamviewer_13.0.5494_amd64.deb you'll see it redirect to https://dl.tvcdn.de/download/linux/version_13x/teamviewer_13.0.5494_13.0.5494_amd64.deb Which, ofc, is 404.
I imagine there is also probably quite a few changes needed to the package since they switched from Wine to QT5
zfkerr commented on 2017-12-04 19:41 (UTC) (edited on 2017-12-04 19:46 (UTC) by zfkerr)
TeamViewer 13 Now Available For GNU/Linux As A Native 64-bit Port. https://www.phoronix.com/scan.php?page=news_item&px=TeamViewer-13-For-Linux
The latest version of the TeamViewer remote control/desktop sharing/web conferencing software is now available for GNU/Linux with a number of improvements. TeamViewer 13 is now available for GNU/Linux, currently in preview form. Besides the iOS screen sharing with remote support, better file transfer abilities, and other key improvements, there are also a number of GNU/Linux-specific improvements too. This GNU/Linux build of TeamViewer 13 is now "native" for GNU/Linux in that it no longer depends upon Wine. TeamViewer 13 for Linux is also now a native 64-bit package without requiring 32-bit dependencies. Additionally, TeamViewer for GNU/Linux is now available in DEB and RPM package form. This native GNU/Linux build makes use of a native Qt-based user-interface compared to its older code relying upon Wine. TeamViewer 13 for GNU/Linux also has initial Wayland support but for now only with outgoing remote control and incoming file transfer support. More details on TeamViewer 13 for GNU/Linux via https://community.teamviewer.com/t5/Linux/Update-TeamViewer-13/td-p/24537
swiftgeek commented on 2017-12-02 12:12 (UTC)
dano5 commented on 2017-12-02 11:55 (UTC)
3rn3st0 commented on 2017-12-01 16:32 (UTC)
vlamnire0 commented on 2017-11-29 01:46 (UTC)
dotvezz commented on 2017-11-28 20:11 (UTC)
woyzeck commented on 2017-11-28 11:35 (UTC)
Triodes commented on 2017-11-27 14:06 (UTC)
francoism90 commented on 2017-11-27 08:02 (UTC)
farwayer commented on 2017-11-26 19:31 (UTC)
Phry commented on 2017-11-26 08:42 (UTC)
abdullatif commented on 2017-11-26 01:55 (UTC)
francoism90 commented on 2017-11-25 12:12 (UTC) (edited on 2017-11-25 12:15 (UTC) by francoism90)
Phry commented on 2017-11-25 11:41 (UTC)
sindria commented on 2017-11-22 12:09 (UTC) (edited on 2017-11-22 12:14 (UTC) by sindria)
jeffreylin commented on 2017-11-22 02:38 (UTC)
francoism90 commented on 2017-11-21 13:25 (UTC)
PhotonX commented on 2017-11-21 13:23 (UTC)
jeffreylin commented on 2017-11-21 13:12 (UTC)
shyokou commented on 2017-11-20 03:00 (UTC)
shyokou commented on 2017-11-20 02:41 (UTC)
netpumber commented on 2017-11-18 17:15 (UTC)
jmontano commented on 2017-11-17 15:48 (UTC)
PhotonX commented on 2017-11-16 20:05 (UTC)
Nowaker commented on 2017-11-15 18:09 (UTC)
Utini commented on 2017-11-15 10:00 (UTC) (edited on 2017-11-15 10:01 (UTC) by Utini)
aaronm-cloudtek commented on 2017-11-15 05:57 (UTC)
Utini commented on 2017-11-14 22:07 (UTC)
aaronm-cloudtek commented on 2017-11-14 21:18 (UTC)
Utini commented on 2017-11-14 21:16 (UTC)
Caiosama205 commented on 2017-11-14 19:24 (UTC)
bubbles commented on 2017-11-12 04:19 (UTC) (edited on 2017-11-12 04:19 (UTC) by bubbles)
benjarobin commented on 2017-11-11 21:16 (UTC)
cm_song commented on 2017-11-11 04:55 (UTC)
jmontano commented on 2017-11-10 19:18 (UTC)
loscsol commented on 2017-11-06 13:09 (UTC)
jollyroberts commented on 2017-11-05 04:15 (UTC)
gun26 commented on 2017-11-04 21:58 (UTC)
mareke commented on 2017-11-04 17:28 (UTC)
butler360 commented on 2017-11-02 18:47 (UTC)
Utini commented on 2017-11-02 18:37 (UTC)
P_wandelwall commented on 2017-11-02 13:00 (UTC)
npfeiler commented on 2017-11-01 12:09 (UTC)
d1wepn commented on 2017-10-31 23:34 (UTC)
tembleking commented on 2017-10-31 15:07 (UTC)
airv_zxf commented on 2017-10-29 22:10 (UTC)
somepaulo commented on 2017-10-27 20:23 (UTC)
shieldwed commented on 2017-10-27 20:12 (UTC)
steadfasterX commented on 2017-10-27 07:04 (UTC)
dschense commented on 2017-10-27 04:14 (UTC)
giostark commented on 2017-10-26 07:55 (UTC) (edited on 2017-10-26 08:02 (UTC) by giostark)
HarlemSquirrel commented on 2017-10-24 17:39 (UTC)
max.bra commented on 2017-10-23 10:34 (UTC)
PhotonX commented on 2017-10-23 10:28 (UTC)
max.bra commented on 2017-10-23 10:21 (UTC)
cimarronline commented on 2017-10-23 01:26 (UTC) (edited on 2017-10-23 03:55 (UTC) by cimarronline)
pschichtel commented on 2017-10-21 20:31 (UTC)
PhotonX commented on 2017-10-21 19:26 (UTC)
dark-saber commented on 2017-10-21 18:20 (UTC)
pschichtel commented on 2017-10-21 17:26 (UTC)
WFV commented on 2017-10-21 17:16 (UTC) (edited on 2017-10-28 22:32 (UTC) by WFV)
jackarc commented on 2017-10-21 13:04 (UTC)
hleuckanet commented on 2017-10-20 22:19 (UTC)
CarlosCunha commented on 2017-10-20 11:49 (UTC)
Cysioland commented on 2017-10-20 10:27 (UTC)
tavuntu commented on 2017-10-18 18:26 (UTC)
boerde commented on 2017-10-18 18:21 (UTC)
z3ntu commented on 2017-10-17 19:47 (UTC)
gerladeno commented on 2017-10-16 07:20 (UTC)
valnelde commented on 2017-10-15 13:05 (UTC)
jerome2016 commented on 2017-10-13 13:02 (UTC)
annoyingduck commented on 2017-10-12 20:11 (UTC) (edited on 2017-10-12 20:17 (UTC) by annoyingduck)
jimmy00784 commented on 2017-10-12 15:07 (UTC)
netpumber commented on 2017-10-12 14:32 (UTC)
gerladeno commented on 2017-10-12 11:16 (UTC)
tuva_men commented on 2017-10-12 04:40 (UTC)
abhinav.gaur13 commented on 2017-10-10 17:48 (UTC)
RIscRIpt commented on 2017-10-10 15:19 (UTC)
dml commented on 2017-10-10 09:15 (UTC)
darkprof commented on 2017-10-09 15:59 (UTC)
insonifi commented on 2017-10-09 08:12 (UTC)
yu.development commented on 2017-10-09 03:06 (UTC)
kolewu commented on 2017-10-07 20:01 (UTC) (edited on 2017-10-07 20:22 (UTC) by kolewu)
figue commented on 2017-10-07 19:25 (UTC) (edited on 2017-10-07 19:28 (UTC) by figue)
cimarronline commented on 2017-10-07 18:39 (UTC) (edited on 2017-10-07 20:03 (UTC) by cimarronline)
TechDesk commented on 2017-10-07 13:51 (UTC)
KgOfHedgehogs commented on 2017-10-07 13:21 (UTC)
lukeniu666 commented on 2017-10-07 09:14 (UTC) (edited on 2017-10-07 12:17 (UTC) by lukeniu666)
marcopus commented on 2017-10-07 08:34 (UTC)
mozo commented on 2017-10-05 23:14 (UTC)
kang commented on 2017-10-05 21:48 (UTC)
zurajm commented on 2017-10-05 18:31 (UTC)
mozo commented on 2017-10-05 18:12 (UTC)
Utini commented on 2017-10-05 14:37 (UTC)
commented on 2017-10-01 21:46 (UTC)
severach commented on 2017-09-29 17:05 (UTC)
figue commented on 2017-09-29 15:05 (UTC)
irvin700 commented on 2017-09-29 14:31 (UTC) (edited on 2017-09-30 01:22 (UTC) by irvin700)
Strit commented on 2017-09-29 14:22 (UTC)
ndandanov commented on 2017-09-29 06:57 (UTC)
irvin700 commented on 2017-09-29 01:39 (UTC) (edited on 2017-09-29 01:40 (UTC) by irvin700)
ndandanov commented on 2017-09-28 14:49 (UTC)
swiftgeek commented on 2017-09-28 10:59 (UTC) (edited on 2017-12-11 05:30 (UTC) by swiftgeek)
!!!!! THIS PACKAGE IS NOT FOR BETA/PRELEASE VERSION OF TEAMVIEWER !!!!!
Changelog: https://www.teamviewer.com/en/download/changelog/
Old freetype packages https://wiki.archlinux.org/index.php/Arch_Linux_Archive (x86_64) https://archive.archlinux.org/packages/l/lib32-freetype2/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz (i686) https://archive.archlinux.org/packages/f/freetype2/freetype2-2.8-2-i686.pkg.tar.xz
Teamviewer v13.x for linux is not available yet (only as beta/preview so far). host-only preview package is available on site but this aur package is not for that.
I can't have branch other than master on AUR for beta/preview releases so use teamviewer-beta etc for that
armv7h is only available as teamviewer_host for time being (hopefully it will appear before preview/beta ends)
https://tv-static.net/2b57eb6e7f2e456a863b39f5640a2734/resources/images/badges/preview-rotated.svg
!!!!! THIS PACKAGE IS NOT FOR BETA/PRELEASE VERSION OF TEAMVIEWER !!!!!
Pinned Comments
swiftgeek commented on 2018-10-26 07:34 (UTC) (edited on 2020-06-23 14:30 (UTC) by swiftgeek)
Go to teamviewer-beta for beta/preview releases
seyn6gk commented on 2018-04-05 07:26 (UTC)
https://community.teamviewer.com/t5/Linux/uninstalled-tar-package-running-without-display-manager/m-p/32597/highlight/true#M2034
WARNING!
teamviewer 13 requires a desktop environment or login with lightdm etc, with startx it won't work, the staff of teamviewer confirmed, startx feature won't come in this year, it seems reverting back to teamviewer 12 is the only option for startx folks.