@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: | 1458 |
| Popularity: | 2.05 |
| 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 indeedqt5-webenginehasminizipas a dependency. Sominizipshould already be installed throughqt5-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 = 60ferrvittorio 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)
@dano and here you have beta package https://aur.archlinux.org/packages/teamviewer-beta/
dano5 commented on 2017-12-02 11:55 (UTC)
tw13 is now available as a beta:
https://community.teamviewer.com/t5/Linux/Update-TeamViewer-13/m-p/24537#M1131
3rn3st0 commented on 2017-12-01 16:32 (UTC)
Hello people, greetings from Venezuela.
I need help to make a downgrade from version 12.0 to version 10.x. Where I can found the package for this version?
Sorry for my bad english.
vlamnire0 commented on 2017-11-29 01:46 (UTC)
If lib32-dbus is not installed I receive this error when starting the teamviewer daemon.
> systemctl status teamviewerd.service
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-11-28 19:43:17 CST; 29s ago
Process: 2960 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=127)
Nov 28 19:43:17 laptop systemd[1]: Starting TeamViewer remote control daemon...
Nov 28 19:43:17 laptop teamviewerd[2960]: /opt/teamviewer/tv_bin/teamviewerd: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file
Nov 28 19:43:17 laptop systemd[1]: teamviewerd.service: Control process exited, code=exited status=127
Nov 28 19:43:17 laptop systemd[1]: teamviewerd.service: Failed with result 'exit-code'.
Nov 28 19:43:17 laptop systemd[1]: Failed to start TeamViewer remote control daemon.
After install lib32-dbus from the repository it starts just fine.
dotvezz commented on 2017-11-28 20:11 (UTC)
This does need lib32-dbus as a dependency.
woyzeck commented on 2017-11-28 11:35 (UTC)
Consider including lib32-dbus as a dependency.
Triodes commented on 2017-11-27 14:06 (UTC)
I too can confirm that this package will not work on my system without lib32-dbus installed.
So adding it to the deps would probably be a good idea
francoism90 commented on 2017-11-27 08:02 (UTC)
@Phry This also fixed my issue! :)
@swiftgeek Would it be a nice addition to patchout NetworkManager on teamviewered.service?
farwayer commented on 2017-11-26 19:31 (UTC)
lib32-dbus should be added to deps
Phry commented on 2017-11-26 08:42 (UTC)
@francoism90
Thanks, this has solved the problem, hadn't thought about it.
abdullatif commented on 2017-11-26 01:55 (UTC)
Hi, @swiftgeek
I have got some trouble with systemd when trying to start Teamviewer : "error while loading shared libraries: libdbus-1.so.3" , so I installed 'lib32-dbus' and everything was OK.
So maybe you should add lib32-dbus to the list of dependencies.
francoism90 commented on 2017-11-25 12:12 (UTC) (edited on 2017-11-25 12:15 (UTC) by francoism90)
@Phry: For some reason starting TV resets the (active) interface.
Are you sure it's the wpa_supplicant service or the interface losing settings?
Maybe you can edit the systemd service:
[Unit]
Description = TeamViewer remote control daemon
After = NetworkManager-wait-online.service network.target network-online.target dbus.service
Wants = NetworkManager-wait-online.service network-online.target
Requires = dbus.service
Phry commented on 2017-11-25 11:41 (UTC)
After I haven't been able to use teamviewer because of the lib issue, it now works again, thanks!
Now I had another odd problem, though: Whenever I started the teamviewer daemon, my wifi stopped working, dmesg:
wlp2s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
Turned out that the teamviewer daemon seems to start the wpa_supplicant service that interferes with my already running netctl. Stopping wpa_supplicant solves this problem, but of course I have to do it manually every time, which is a bit annoying.
But it never happened before and why would/should teamviewer start wpa_supplicant in the first place? Has anyone had a similar issue?
sindria commented on 2017-11-22 12:09 (UTC) (edited on 2017-11-22 12:14 (UTC) by sindria)
(pts/2):{4}% uname -a
Linux Anything-Laptop 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux
after install teamviewer with all dependencies with yaourt -S teamviewer, i get this:
(pts/2):{2}% teamviewer
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
/opt/teamviewer/tv_bin/wine/bin/wine: error while loading shared libraries: cannot create cache for search path: Cannot allocate memory
Seems that all shared library there are...i don't understand
i tried with the quick support version and i get the same output
Anyone else have this issue ?
jeffreylin commented on 2017-11-22 02:38 (UTC)
Thanks guys - sorry I'm new to this. :)
francoism90 commented on 2017-11-21 13:25 (UTC)
@jeffreylin enable multilib.
PhotonX commented on 2017-11-21 13:23 (UTC)
Did you try clicking on the dependencies in the dependency list just above this comment section? :)
jeffreylin commented on 2017-11-21 13:12 (UTC)
Getting this error:
error: target not found: lib32-freetype2
error: target not found: lib32-libjpeg6-turbo
error: target not found: lib32-libxinerama
error: target not found: lib32-libxrender
error: target not found: lib32-fontconfig
error: target not found: lib32-libsm
error: target not found: lib32-libxtst
error: target not found: lib32-libpng12
I know how to get the freetype one, but where do I go install the rest of the dependencies?
shyokou commented on 2017-11-20 03:00 (UTC)
Since teamviewer 12 is of pure 32-bit, it depends upon 'lib32-libxtst' rather than 'libxtst' directly on an x86_64 box, although 'lib32-libxtst' does depend upon 'libxtst' ...
Either teamviewer 12 wants 'dbus' or 'lib32-dbus' on i686 or x86_64 box, such that dependencies for x86_64 are all 'lib32-' initials versus those for i686, see ...
shyokou commented on 2017-11-20 02:41 (UTC)
@netpumber: I guess that umask 077 in your '/etc/profile' has something to do with those 'filesystem: 755 package: 700' ...
netpumber commented on 2017-11-18 17:15 (UTC)
Hey guyz.
I'm trying to install it and that's what I'm getting back:
:: Processing package changes...
(1/1) installing teamviewer
[########################################################################################] 100%
warning: directory permissions differ on /etc/
filesystem: 755 package: 700
warning: directory permissions differ on /etc/teamviewer/
filesystem: 755 package: 700
warning: directory permissions differ on /opt/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/bin/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/share/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/share/icons/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/share/icons/hicolor/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/share/icons/hicolor/48x48/
filesystem: 755 package: 700
warning: directory permissions differ on /usr/share/icons/hicolor/48x48/apps/
filesystem: 755 package: 700
warning: directory permissions differ on /var/
filesystem: 755 package: 700
warning: directory permissions differ on /var/log/
filesystem: 755 package: 700
warning: directory permissions differ on /var/log/teamviewer12/
filesystem: 755 package: 700
The Teamviewer daemon must be running for Teamviewer to work.
Execute 'sudo systemctl enable teamviewerd' in a terminal.
:: Running post-transaction hooks...
(1/3) Updating icon theme caches...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Updating the desktop file MIME type cache...
Anyone else have this issue ?
I'm having umask 077 in the /etc/profile. Is that a problem ?
jmontano commented on 2017-11-17 15:48 (UTC)
@Nowaker you must install lib32-dbus it's a dependency but no installed
PhotonX commented on 2017-11-16 20:05 (UTC)
Updated to -7 on one machine, seems to work without manual intervention now, thanks for the update!
Nowaker commented on 2017-11-15 18:09 (UTC)
I'm getting this when starting it:
/opt/teamviewer/tv_bin/script/tvw_exec: line 40: 6160 Aborted (core dumped) "$TV_BIN_DIR/teamviewerd" -n -f
Anyone else had the same?
Utini commented on 2017-11-15 10:00 (UTC) (edited on 2017-11-15 10:01 (UTC) by Utini)
@swiftgeek
@nickoe
@astronautlevel
Please include this change to easily fix this package for all people:
cp libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/wine/lib/libfreetype.so.6
Also please add "lib32-dbus" as dependency.
Thanks !
aaronm-cloudtek commented on 2017-11-15 05:57 (UTC)
That fixed it, thanks!
Utini commented on 2017-11-14 22:07 (UTC)
It needs lib32-dbus as dependency. Install it manually from the official repo and it will work again.
aaronm-cloudtek commented on 2017-11-14 21:18 (UTC)
I'm getting the same libdbus error as @Utini
Utini commented on 2017-11-14 21:16 (UTC)
Shouldn't it be like this:
cp libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/wine/lib/libfreetype.so.6-14.0
instead of:
cp libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/wine/lib/libfreetype.so.6
?
Also I am getting this error when starting teamviewerd.service:
teamviewerd[4828]: /opt/teamviewer/tv_bin/teamviewerd: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file or directory
Caiosama205 commented on 2017-11-14 19:24 (UTC)
@bubbles, thank you! that works
bubbles commented on 2017-11-12 04:19 (UTC) (edited on 2017-11-12 04:19 (UTC) by bubbles)
@benjarobin
`A much better fix, it to simply do, from the extracted package lib32-freetype2-2.8-2-x86_64.pkg.tar.xz :
cp libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/wine/lib/libfreetype.so.6`
Working Fine.
Thanks.
benjarobin commented on 2017-11-11 21:16 (UTC)
A much better fix, it to simply do, from the extracted package lib32-freetype2-2.8-2-x86_64.pkg.tar.xz :
cp libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/wine/lib/libfreetype.so.6
cm_song commented on 2017-11-11 04:55 (UTC)
We can do the following:
$ cp /var/cache/pacman/pkg/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz /tmp
$ cd /tmp
$ tar -xvJf lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
$ sudo cp -r ./usr/lib32/* /usr/lib32
$ reboot
It's working now.
jmontano commented on 2017-11-10 19:18 (UTC)
@jackarc's proposed solution worked for me
"
sudo downgrade lib32-freetype2
but only lib32-freetype2-2.7.* is working
with lib32-freetype2-2.8.* gui wont show up
"
Thanks
loscsol commented on 2017-11-06 13:09 (UTC)
@max.bra 's PKGBUILD works fine, thanks!
jollyroberts commented on 2017-11-05 04:15 (UTC)
@TheGoliath: I had to install lib32-dbus to get around that issue. Looks like teamviewer wants the 32 bit version of that libdbus file.
gun26 commented on 2017-11-04 21:58 (UTC)
@mareke On my own box (x86_64, testing repos enabled) /usr/lib/libdbus-so is a symlink to libdbus-1.so.3.19.3 in the same directory, which is provided by dbus 1.12.0-1 in core. Are both dbus and the symlink not in place in your system?
mareke commented on 2017-11-04 17:28 (UTC)
New error for me.
systemctl start teamviewerd gives this error!
/opt/teamviewer/tv_bin/teamviewerd: error while loading shared libraries: libdbus-1.so.3: cannot open shared object file: No such file
butler360 commented on 2017-11-02 18:47 (UTC)
Nomachine is the best alternative, but not as easy to set up for "clients" and the like.
Utini commented on 2017-11-02 18:37 (UTC)
Hmm still doesn't work for me :/
Is there any good backup/alternative for teamviewer?
P_wandelwall commented on 2017-11-02 13:00 (UTC)
@cimarronline Thanks, that works just fine.
npfeiler commented on 2017-11-01 12:09 (UTC)
please bump the pkgrel if you make changes to dependencies, and reset to 1 when you upgrade to a new version
d1wepn commented on 2017-10-31 23:34 (UTC)
Same error as @tembleking. Freetype2<2.8.1 and lib32-freetype2<2.8.1 could not be resolved.
tembleking commented on 2017-10-31 15:07 (UTC)
I cannot install it, freetype2<2.8.1 and lib32-freetype2<2.8.1 could not be resolved.
airv_zxf commented on 2017-10-29 22:10 (UTC)
@max.bra | I tried this and it works. Thanks bro!
In fact it's a smart solution.
Is it the best solution @swiftgeek (@nickoe, @astronautlevel)?
somepaulo commented on 2017-10-27 20:23 (UTC)
@max.bra Thank you for the PKGBUILD. Works great.
@swiftgeek Any chance you'll revise your PKBUILD to include @max.bra's solution?
shieldwed commented on 2017-10-27 20:12 (UTC)
@max.bra PKGBUILD working for me too. Keeps it simple to update arch. Thanks.
steadfasterX commented on 2017-10-27 07:04 (UTC)
> tuva_men commented on 2017-10-12 04:40
> @yu.development, me also thanking you. I have to reboot just restarting daemon wasn't enough.
same here. this here was *NOT* enough:
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-freetype2/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
sudo systemctl daemon-reload
sudo systemctl restart teamviewerd
Teamviewer does not start.
reboot was required and afterwards the TV GUI started to work for me again.
dschense commented on 2017-10-27 04:14 (UTC)
@max.bra PKGBUILD working fine!
giostark commented on 2017-10-26 07:55 (UTC) (edited on 2017-10-26 08:02 (UTC) by giostark)
+1 @max.bra ! Grande Massimo ! your PKGBUILD worked for me too.
ps: Ebbravo Massimo , il senso della community ancora una volta bene espresso , grazie ;-)
HarlemSquirrel commented on 2017-10-24 17:39 (UTC)
@max.bra your PKGBUILD worked for me! Thanks!
max.bra commented on 2017-10-23 10:34 (UTC)
@PhotonX
> (if that's not exactly what @max.bra did in his -7 snapshot)
yes, it is
PhotonX commented on 2017-10-23 10:28 (UTC)
@cimarronline, @swiftgeek: Maybe it is possible to include the necessary freetype2 files into the teamviewer package if they don't conflict with the new freetype2 version (if that's not exactly what @max.bra did in his -7 snapshot)?
max.bra commented on 2017-10-23 10:21 (UTC)
@cimarronline
totally agreed. if a simply and possible solution is doable, it's not possible for an AUR package to block system updates.
for those interested, this is a snapshot of a theoretical teamviewer 12.0.85001-7:
https://www.dropbox.com/s/kglzs69adnq80hd/teamviewer-12.0.85001-7.zip?dl=0
cimarronline commented on 2017-10-23 01:26 (UTC) (edited on 2017-10-23 03:55 (UTC) by cimarronline)
Perhaps a more "proper" solution would be to download the lib32-freetype2 2.8 package, unpack, and place the three files/links from /usr/lib32 into /opt/teamviewer/tv_bin/wine/lib. Then no other packages need to be downgraded or held back.
pschichtel commented on 2017-10-21 20:31 (UTC)
You could trick teamviewer into using latest wine (requires wine + wine-mono installed) by symlinking /opt/teamviewer/tv_bin/wine/bin/{wine,wineserver,wine-preloader} to the system binaries (/usr/bin/{wine,wineserver,wine-preloader}).
Doing this allowed me to connect to remote systems, but clients were unable to properly connect to my system.
PhotonX commented on 2017-10-21 19:26 (UTC)
Is there any proper solution (not involving holding back package updates) for this?
dark-saber commented on 2017-10-21 18:20 (UTC)
Do we really need fontconfig<2.8.1 (it's so old that it's not even on Arch Linux Archive), or is this requirement actually on freetype2?
pschichtel commented on 2017-10-21 17:26 (UTC)
The reason it works with infinality-patched freetype, is that the package has not been updated to freetype 2.8.1. It worked for me after downgrading to normal 2.8.0 *and restarting my system* (Removing a library from disk doesn't remove it from memory).
The issue is probably the same that affected gnome 2.0: https://bugs.winehq.org/show_bug.cgi?id=43715 (fixed in 2.0.3).
WFV commented on 2017-10-21 17:16 (UTC) (edited on 2017-10-28 22:32 (UTC) by WFV)
Does this mean it's compiled against lib32-freetype2-infinality-ultimate and freetype2-infinality-ultimate from the aur instead the freetype2 packages in the official repos? They're not listed in the dependencies in the pkgbuild. Thanks.
EDIT: The service restarts for me w/o reboot however, had to add an auto-start in Xfce Session and Startup for TeamViewer as the GUI otherwise doesn't auto-start (since after 11.0.67687-4) even though within the app it is set to "start with system".
jackarc commented on 2017-10-21 13:04 (UTC)
sudo downgrade lib32-freetype2
but only lib32-freetype2-2.7.* is working
with lib32-freetype2-2.8.* gui wont show up
hleuckanet commented on 2017-10-20 22:19 (UTC)
"yaourt -s lib32-freetype2-infinality-ultimate"
Works for me. Thanks
CarlosCunha commented on 2017-10-20 11:49 (UTC)
Equal a @boerde
"yaourt -s lib32-freetype2-infinality-ultimate"
Thanks.....
Cysioland commented on 2017-10-20 10:27 (UTC)
For me it worked three
tavuntu commented on 2017-10-18 18:26 (UTC)
Downgrading lib32-freetype2 worked for me too!
boerde commented on 2017-10-18 18:21 (UTC)
For me it is only working by installing "lib32-freetype2-infinality-ultimate".
z3ntu commented on 2017-10-17 19:47 (UTC)
Downgrading lib32-freetype2 worked for me too.
gerladeno commented on 2017-10-16 07:20 (UTC)
@valnelde, thank you, mate, that worked for me!
valnelde commented on 2017-10-15 13:05 (UTC)
I have just tried all the tips here without success. In the end, I got teamviewer then with lib32-freetype2-infinality-ultimate to run
jerome2016 commented on 2017-10-13 13:02 (UTC)
@annoyingduck, thank you man, you are the best.
annoyingduck commented on 2017-10-12 20:11 (UTC) (edited on 2017-10-12 20:17 (UTC) by annoyingduck)
You guys are great here. Will we be notified if we can eventually release freetype2 from the ignore pkg list here? Steps to install & run (thanks to awesome comments):
gpg --keyserver pgp.mit.edu --recv-keys C1A60EACE707FDA5
(for ttfautohint package dependency)
yaourt -S teamviewer
sudo pacman -U https://archive.archlinux.org/packages/l/lib32-freetype2/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
OR:
sudo downgrade lib32-freetype2 (if downgrade installed)
Then add to pacman ignore pkg list in your preferred way.
sudo systemctl start teamviewerd.service
sudo systemctl enable teamviewerd.service
Now you can run teamviewer
jimmy00784 commented on 2017-10-12 15:07 (UTC)
I can confirm that Teamviewer works with lib32-freetype2-2.8-2
netpumber commented on 2017-10-12 14:32 (UTC)
@gerladeno : I'm having the same issue since yesterday and I couldn't find any solution.
gerladeno commented on 2017-10-12 11:16 (UTC)
Folks, help me out please!
I have following issue:
[pavel@pavel-pc ~]$ teamviewer
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
[pavel@pavel-pc ~]$
meaning nothing happens after that. Does anyone have the same issue? Any ideas on how to solve this?
Thank you!
tuva_men commented on 2017-10-12 04:40 (UTC)
@yu.development, me also thanking you. I have to reboot just restarting daemon wasn't enough.
abhinav.gaur13 commented on 2017-10-10 17:48 (UTC)
@yu.development , thanks.. Downgrading lib32-freetype2 from verison 2.8.1-1 to 2.8.2 worked for me too. After downgrading, reboot of system not required. Just restart the teamviewerd.service
RIscRIpt commented on 2017-10-10 15:19 (UTC)
@figue, you should add this to your instruction,
And for those who fails on step 3 `makepkg -s` because of signature verification failure:
You can get signature from mit's servers:
$ gpg --keyserver pgp.mit.edu --recv-keys C1A60EACE707FDA5
(taken from pinned comment of ttfautohint AUR package)
dml commented on 2017-10-10 09:15 (UTC)
@yu.development
thank you, it's work for me too
darkprof commented on 2017-10-09 15:59 (UTC)
now refuses to run x86_64
insonifi commented on 2017-10-09 08:12 (UTC)
You can also downgrade just like that:
> pacman -U https://archive.archlinux.org/packages/l/lib32-freetype2/lib32-freetype2-2.8-2-x86_64.pkg.tar.xz
Seems to work but required reboot. Restarting teamviewerd.service wasn't enough for me.
yu.development commented on 2017-10-09 03:06 (UTC)
install downgrade then install lib32-freetype2-2.8-2-x86_64.pkg.tar.xz with:
downgrade lib32-freetype2
then restart teamviewer service, it's work for me
kolewu commented on 2017-10-07 20:01 (UTC) (edited on 2017-10-07 20:22 (UTC) by kolewu)
EDIT: have seen the newer comments and can confirm, that using the normal freetype-2.8 version cures teamviewer.
I can confirm that the current teamviewer 12.0.85001-6 (and the former version 12.0.76279-6) has a problem that can be fixed by installing the AUR package lib32-freetype2-old-hinting-2.8-2. You unfortunately have to use an older version of this AUR package because the current version 2.8.1-1 doesn't work. You can get the older version by using git to get the former commit of the AUR package.
Doing this makes teamviewer working again.
figue commented on 2017-10-07 19:25 (UTC) (edited on 2017-10-07 19:28 (UTC) by figue)
EDIT: I saw now what @cimarronline said... Consider my post like a "how-to" you can do manually...
New workaround for GUI issues caused by lib32-freetype:
1. clone lib32-freetype:
$ asp checkout lib32-freetype2
$ cd lib32-freetype2/trunk
2: checkout last 2.8 revision:
$ git checkout 3746440f041493db9cb4ada7f328412da9880322
3. build:
$ makepkg -s
3. copy library to Teamviewer's library path:
$ sudo cp pkg/lib32-freetype2/usr/lib32/libfreetype.so.6.14.0 /opt/teamviewer/tv_bin/RTlib/libfreetype.so.6
cimarronline commented on 2017-10-07 18:39 (UTC) (edited on 2017-10-07 20:03 (UTC) by cimarronline)
Wine 2.18 has been fixed for the freetype2 version 2.8.1, but Teamviewer uses its own old wine version. So if you update lib32-freetype2 to 2.8.1, you have to provide teamviewer with the older lib32-freetype2 (2.8).
I just downloaded the lib32-freetype2 version 2.8 libs and put them in a directory, then start teamviewer with a script that includes “export LD_LIBRARY_PATH=” with the directory that has the libs. Maybe this process could be written into the PKGBUILD?
TechDesk commented on 2017-10-07 13:51 (UTC)
i have a problem with teamviewer --daemon-start
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Starting network process (no daemon)
terminate called without an active exception
/opt/teamviewer/tv_bin/script/tvw_exec : ligne 40 : 7426 Abandon (core dumped)"$TV_BIN_DIR/teamviewerd" -n -f
Network process already started (or error)
Launching TeamViewer GUI ...
but don't start
KgOfHedgehogs commented on 2017-10-07 13:21 (UTC)
@lukeniu666, same problem
lukeniu666 commented on 2017-10-07 09:14 (UTC) (edited on 2017-10-07 12:17 (UTC) by lukeniu666)
Teamviewer 12.0.85001-6
It was working till yeasterday. Today lib32-freetype2-old-hinting was updated in AUR to 2.8.1-1 version (yesterday it was 2.8-2) and it stopped working. I cannot find lib32-freetype2-old-hinting 2.8-2 version in aur anymore. Any help please?
marcopus commented on 2017-10-07 08:34 (UTC)
teamviewer 12.0.85001-6 here
The gui doesn't show up. Installed lib32-freetype2-old-hinting already, but it didn't fix. I couldn't seem to be able to find aur/lib32-freetype2-old-hinting-2.8-2 as suggested. Where should I look for exactly?
mozo commented on 2017-10-05 23:14 (UTC)
Yes, it works now. Thank you!
kang commented on 2017-10-05 21:48 (UTC)
@swiftgeek lib32-freetype2-old-hinting needs to be added to the runtime deps in this PKGBUILD
zurajm commented on 2017-10-05 18:31 (UTC)
Hi,
I had the same issue (TeamViewer GUI not starting), I fixed it by installing aur/lib32-freetype2-old-hinting-2.8-2.
Thanks for hints!
mozo commented on 2017-10-05 18:12 (UTC)
Same here:
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
And nothing happens...
Utini commented on 2017-10-05 14:37 (UTC)
I dont have wine installed on my system and teamviewer still doesnt start:
teamviewer
Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
commented on 2017-10-01 21:46 (UTC)
Regarding the non start problem. In my case i was able to start teamviewer by setting WINEARCH=win32 in my profile.
I haven't looked into the exact cause, but seems like the teamviewer embedded wine is conflicting with system installed wine.
severach commented on 2017-09-29 17:05 (UTC)
Teamviewer 12 is working fine in my teamviewer9 package. lib32-freetype2 2.8.1-1 is in testing. You should be running 2.8-2.
wine 2.17-1, lib32-freetype2 2.8-2
figue commented on 2017-09-29 15:05 (UTC)
@irvin700 @Strit thanks. I finally have a workaround... I installed multilib/lib32-freetype2 (which is 2.8, in multilib-testing it's in 2.8.1) and install multilib/wine-staging-nine (which is 2.16 for now). Let's see if upstream fix it soon.
irvin700 commented on 2017-09-29 14:31 (UTC) (edited on 2017-09-30 01:22 (UTC) by irvin700)
Strit you fixed it!! Both the AUR and all-in-one tar versions work now.
This is what what I did:
[2017-09-29 10:28] [ALPM] downgraded lib32-freetype2 (2.8.1-1 -> 2.7.1-2)
[2017-09-29 10:28] [ALPM] downgraded wine (2.17-1 -> 2.16-1)
EDIT: I went ahead and upgraded wine to 2.18 and it seems to be working so far. lib32-freetype2 is the only version I retained at 2.7.1-2
Strit commented on 2017-09-29 14:22 (UTC)
I've heard that freetype2 2.8.1 results in teamviewer not launching.
Did you guys try downgrading that one to 2.8?
Wine 2.17 has the same issue.
ndandanov commented on 2017-09-29 06:57 (UTC)
irvin700, I did a similar thing to you regarding the dependencies and still no GUI.
Before that everything seemed to work correctly.
I do not think it is display manager related as I have a standard xfce4 installation with xfwm.
irvin700 commented on 2017-09-29 01:39 (UTC) (edited on 2017-09-29 01:40 (UTC) by irvin700)
This no longer starts up, no GUI. I tried downgrading all the dependencies but to no avail. Maybe I didn't get them all?
Also, I also downloaded the all-in-one tar file from the official website, same thing! I wonder if it's display manager related, I use sddm.
ndandanov commented on 2017-09-28 14:49 (UTC)
I have the same issue as dml.
I thought it would be because of an update in fontconfig and lib32-fontconfig, but rolling them back from 2.12.6-1 to 2.12.5-1 did not solve the issue.
How are we about to proceed?
Which logs/other information would be needed to debug the issues?
Thanks!
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 !!!!!
dml commented on 2017-09-28 09:45 (UTC)
Program does not start last week.
Daemon works, gui - not.
ps -e | grep -i team
426 ? 00:00:11 teamviewerd
968 ? 00:00:04 TeamViewer.exe <defunct>
I use this as alternative: https://aur.archlinux.org/packages/anydesk/
commented on 2017-09-26 10:41 (UTC)
Updated PKGBUILD
# Maintainer: Alex Taber <aft dot pokemon at gmail dot com>
pkgname=teamviewer
pkgver=12.0.85001
pkgrel=6
pkgdesc='All-In-One Software for Remote Support and Online Meetings'
arch=('i686' 'x86_64')
url='http://www.teamviewer.com'
license=('custom')
options=('!strip')
provides=('teamviewer')
conflicts=('teamviewer-beta')
depends_x86_64=(
'lib32-fontconfig'
'lib32-libpng12'
'lib32-libsm'
'lib32-libxinerama'
'lib32-libxrender'
'lib32-libjpeg6-turbo'
'lib32-libxtst'
'libxtst')
depends_i686=(
'fontconfig'
'libpng12'
'libsm'
'libxinerama'
'libxrender'
'libjpeg6-turbo'
'libxtst')
install=teamviewer.install
source_x86_64=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_amd64.deb")
source_i686=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
md5sums_i686=('ba50068bd0944ac00332e0a8d3d411cb')
md5sums_x86_64=('6a53fe98cbf31c32f17833e9425ac004')
prepare() {
warning "If the install fails, you need to uninstall previous major version of Teamviewer"
tar -xf data.tar.bz2
}
package() {
# Install
warning "If the install fails, you need to uninstall previous major version of Teamviewer"
cp -dr --no-preserve=ownership {etc,opt,usr,var} "${pkgdir}"/
# Additional files
rm "${pkgdir}"/opt/teamviewer/tv_bin/xdg-utils/xdg-email
install -D -m0644 "${pkgdir}"/opt/teamviewer/tv_bin/script/teamviewerd.service \
"${pkgdir}"/usr/lib/systemd/system/teamviewerd.service
install -d -m0755 "${pkgdir}"/usr/{share/applications,share/licenses/teamviewer}
ln -s /opt/teamviewer/License.txt \
"${pkgdir}"/usr/share/licenses/teamviewer/LICENSE
}
beliys commented on 2017-09-24 15:33 (UTC)
@pschichtel But it's not correct for users than want stop daemon after using. Something like as:
systemctl status teamviewerd
running=$?
if [[ $running != 0 ]]
then
sudo systemctl start teamviewerd && /opt/teamviewer/tv_bin/script/teamviewer && sudo systemctl stop teamviewerd
else
/opt/teamviewer/tv_bin/script/teamviewer
fi
pschichtel commented on 2017-09-23 19:55 (UTC)
@beliy You exec command will probably fail, if someone decided to use the systemd service (e.g. for permanent remote access). It will also not stop the service in case the UI crashes.
I'm thinking about something like the following:
systemctl status teamviewerd
running=$?
if [[ $running != 0 ]]
then
systemctl start teamviewerd
fi
/opt/teamviewer/tv_bin/script/teamviewer
if [[ $running != 0 ]]
then
systemctl stop teamviewerd
fi
beliys commented on 2017-09-23 13:14 (UTC)
Why need make systemd service for 1 time exec? Always running is not secure. I think better way is change default exec command to my variant.
pschichtel commented on 2017-09-17 14:06 (UTC)
@beliy I think it would be better to have it start and stop the systemd service only if it is not already running.
beliys commented on 2017-09-16 17:27 (UTC)
please change run command in .desktop file to
/opt/teamviewer/tv_bin/script/teamviewer --daemon start && /opt/teamviewer/tv_bin/script/teamviewer && /opt/teamviewer/tv_bin/script/teamviewer --daemon stop
it's help autorun deamon before start and stop after work.
severach commented on 2017-09-16 05:12 (UTC)
Commenting in the packages won't do any good. There's nothing the packages can do to fix it. Sounds to me like multilib isn't enabled.
CPUnltd commented on 2017-09-16 04:11 (UTC)
@severach in doing such, that doesn't explain why none of the aur managers can't see them. None of the lib32 packages are installing anymore, this is just the first package I've decided to comment on, I've got about 30 more to go. I have yet to find anything on the forums in relation to this. If anyone knows a link I can follow to troubleshoot, please forward.
severach commented on 2017-09-16 00:11 (UTC)
Click on each lib32- above to verify that it exists.
CPUnltd commented on 2017-09-15 23:32 (UTC)
@pschichtel: none of the lib32 packages are installing for me. No matter my configuration,it says all the lib32 packages don't exist. It installed just fine prior to the announcement of 32bit being dropped, and won't run or install since roughly the time support was dropped.
pschichtel commented on 2017-09-15 22:20 (UTC)
@CPUnltd: since when is x86 support going away? Just the i686-only arch is going away, multilib stays.
CPUnltd commented on 2017-09-15 19:46 (UTC)
Completely unusable now that support for x86 is dropped. Please rebuild if possible.
nobyardor commented on 2017-09-15 04:14 (UTC)
kartongsaft.
Because teamviewer original binaries are static linked to wine 1.9.8 x86. In wine x86 teamviewer work better.
kartongsaft commented on 2017-09-07 16:56 (UTC)
Is there a reason why 32-bit libraries is used?
izznogooood commented on 2017-08-15 15:03 (UTC)
systemctl daemon-reload should be added to installer script.
Its not possible to start Teamviewer without the daemon and not possible to start the daemon with out a reload.
CybeX commented on 2017-08-02 19:45 (UTC) (edited on 2017-08-02 19:45 (UTC) by CybeX)
Also have black screen when client connects. Arch x64 + Gnome XWayland.
`GNOME Shell 3.24.3`
`4.12.3-1-ARCH`
Anyone have info on cause?
Venom1991 commented on 2017-06-21 16:29 (UTC) (edited on 2017-06-21 16:30 (UTC) by Venom1991)
Disregard my previous comment, they obviously statically compiled Qt into their executable.
Venom1991 commented on 2017-06-21 16:16 (UTC)
What are the GUI dependencies? I don't see any, at least not on the top level. TeamViewer for Linux was built using Qt, if I'm not mistaken?
commented on 2017-06-19 17:13 (UTC)
Thank you for the pakage!
Black screen between two Lenovo X230 with current arch linux stable and gnome wayland. Gnome with Xorg works fine.
vromanch commented on 2017-06-16 01:24 (UTC)
Tried to connect to my machine from windows got black screen
cubethethird commented on 2017-06-06 01:16 (UTC)
Hadn't used this in a little while, but it now seems to work without issue while running Wayland on Gnome. Hopefully it stays that way.
napa3um commented on 2017-05-25 10:52 (UTC)
Bug: Ubuntu/Windows TeamViewer client connect to Arch TeamViewer server and see black screen.
maofree commented on 2017-05-24 14:29 (UTC)
Hi
I've the same problem of connection
and to use it I need to stop the service and then reactive it with
#systemctl stop teamviewerd.service
#systemctl start teamviewerd.service
the problem is present on my pc instead on my laptop it is ok
bye
num1champ commented on 2017-05-18 07:30 (UTC)
@msifland it is weird that you have to do that, but i manually ran those cmds after login and that solves one of my issues. Where exactly are you executing your script? during boot? after login?
xgdgsc commented on 2017-04-23 16:10 (UTC)
pkgrel=1
mgd commented on 2017-04-16 14:46 (UTC)
Dear LA-MJ,
may I kindly asked you to read up on https://wiki.archlinux.org/index.php/PKGBUILD#Integrity?
You may consider to revise your smug remark afterwards.
Happy easter,
Michael
LA-MJ commented on 2017-04-15 05:56 (UTC)
The world is moving away from SHA1 and you are switching to MD5? :D
swiftgeek commented on 2017-04-13 01:47 (UTC) (edited on 2017-04-13 01:47 (UTC) by swiftgeek)
I can tell that there is an issue when you change tty and teamviewer is only allowed to work as client - tv app disconnects from tv when current tty is different. Sometimes it doesn't reconnect properly when you switch tty back
msifland commented on 2017-04-07 01:40 (UTC)
What I found that works for me is this:
Create a bash script and put it somewhere of your choosing. Then have the script run automatically at start up.
Code:
#!/bin/bash
echo "YOUR PASSWORD" | sudo -S systemctl stop teamviewerd.service
sleep 5
sudo systemctl start teamviewerd.service
teamviewer
End Code:
Seems kind of primitive, I know. But it works for me.
keoma commented on 2017-04-03 18:08 (UTC)
Every time I tried to open TeamViewer without start the teamviewerd service I got the "not ready. No connection" problem. I had to follow the steps 4, 5 and 7 of @erkexzcx tutorial to solve. So, I recommend you to enable the teamviewerd.service.
el.Quero commented on 2017-03-27 13:02 (UTC)
Hi, I'm using Manjaro 17 with Gnome on Wayland and I can use Teamviewer for connecting to other computers by downloading the generic distribution package and running it as normal user, without installing it.
I didn't tested if I can share my desktop but I found that the "installed version" of Teamviewer does not works.
Perhaps is an issue like is having Gparted on Wayland? https://bugzilla.redhat.com/show_bug.cgi?id=1274451#c67
num1champ commented on 2017-03-15 00:42 (UTC) (edited on 2017-03-15 00:43 (UTC) by num1champ)
i can confirm with @cubethethird and @disconnect3d that if you are getting "not ready", just logout of gnome and login again using setting "Gnome on X.org".
disconnect3d commented on 2017-03-09 09:13 (UTC)
Same here as @cubethethird. Simply logout and login into "Gnome on X.org" fixed the issue with "not ready" connection.
I have also tried other screen sharing tools before (e.g. chrome desktop share) - when someone connected to me the only thing they saw was a black screen.
Moving to xorg fixed this as well...
cubethethird commented on 2017-03-05 02:54 (UTC)
For myself, and I imagine for many others, the issue is related to the usage of Wayland (at least on Gnome). Running it through X.org works normally, and reinstalling the application does not seem to affect this.
erkexzcx commented on 2017-03-05 00:28 (UTC)
How to fix "not ready. No connection" issue for teamviewer12, which was not present in teamviewer11:
1. Quit your current teamviewer, running in the system.
2. Disable & stop "teamviewerd" service.
3. Uninstall teamviewer from your system. At this point should be no teamviewer services preinstalled and/or running in the system.
4. sudo rm -rf /etc/teamviewer*
5. rm -rf ~/.config/teamviewer*
6. Install teamviewer (this AUR package).
7. Enable & start "teamviewerd" service.
8. Open teamviewer - it should work by now.
Also, people in official teamviewer forum suggested to disable ipv6 in your router/network profile as this makes teamviewer v12 to work again. However, above steps solved the issue to me and it was not necesarry
Message to maintainer - please add post uninstall script (if possible) to delete content at least from /etc/teamviewer* and a note to delete manually ~/.config/teamviewer*
swiftgeek commented on 2017-03-01 10:30 (UTC)
That would be upstream bug then, please report it instead of quietly patching for it
severach commented on 2017-03-01 01:24 (UTC)
I solved the no connect problem years ago in my teamviewer9 package. It's caused by a missing .Xauthority file which teamviewer>=9.0 needs for no good reason. The supported distros always have this file but the others may not. My teamviewer9 package fixes this problem automatically. Editing the teamviewer9 PKGBUILD allows you to install any version 8 to 12.
Autostart has never fully worked, probably because I use startx. I don't even need it to. I only need Teamviewer as a client. Access to the Linux desktop isn't valuable. Anything I need from afar I can get through SSH.
Teamviewer will freeze if you've started it without the daemon loaded then later start it with the daemon loaded. You must kill all TV processes and delete the config files to switch between daemon and non daemon mode.
ata commented on 2017-02-28 23:41 (UTC)
WFV
sudo pacman -Rn teamviewer
yaourt -S teamviewer11
WFV commented on 2017-02-14 04:51 (UTC) (edited on 2017-02-22 20:55 (UTC) by WFV)
The GUI auto start option worked sometimes but mostly not, back to square one, can't get it to connect no matter what again after -Syu.
Rigoberto commented on 2017-02-10 01:48 (UTC)
en español: lo lamento no tengo tiempo para pensar en ingles:
la solución de emergencia es wine y describiré tal cual me funciono:
1) descargar teamviewer12.exe
2) instalarla con playonlinux
2.1) que playonlinux cree un nuevo disco virtual-wine (32 bit win10)
2.2) hacer la instalación propiamente tal, pero al finalizar, no colocar ningún enlace en el escritorio porque no servirá.
3) ir a ../.PlayOnLinux/wineprefix/teamviewer(nombre del disco virtual)/drive_c/Program Files/TeamViewer y abrir con wine TeamViewer.exe
tal vez lo que comento es tonto, pero lo intente instalar de 50 maneras distintas y puede que para alguien sea un menester de emergencia (indique la forma exacta en que lo hice pero tuve errores en varios intentos (versiones anteriores entorno xp 64 bits etc., tiene que ser teamviewer12 instalarlo en una arquitectura de 32 bits y para win 10). saludos muy cordiales.
shieldwed commented on 2017-02-08 21:18 (UTC)
@logion i tried creating a PKGBUILD from the tar ball. see https://gist.github.com/shieldwed/de48b0c74a240eeaf91e93b7b17ceaac
in this package the file "libpng12.so.0" is missing, but i think this might be ok due to the dependency to lib32-libpng12.
This PKGBUILD is not quite finished since starting teamviewer from a terminal window, it is faulting with:
/opt/teamviewer/tv_bin/script/tvw_exec: line 9: /opt/teamviewer/logfiles/startup.log: Permission denied
Error: LockStartup: internal error 1
maybe you got an idea?
logion commented on 2017-02-08 10:20 (UTC) (edited on 2017-02-08 10:25 (UTC) by logion)
In regards to the "Not ready. Please check your connection" error in teamviewer. There is a thread on the TV forums detailing this issue (https://community.teamviewer.com/t5/TeamViewer-11/No-connection-to-TeamViewer-server/td-p/720), some conclusions are as follows:
* Error shows up on wayland systems, but not an x server systems (I'm only running wayland, and also suffer from this issue under wayland; can't check with X server)
* Using the unsupported systems tar ball under wayland (https://download.teamviewer.com/download/teamviewer_i386.tar.xz), solves the connection issue. I can confirm this is the case and I can remote desktop to my Wintel machine at home from my arch wayland machine at the office.
* Under wayland remote users can not control the local machine, they see a black rectangle. Did not test this.
As for the PKGBUILD AUR file, for X server users there does not need to be any change. For those using wayland, I would suggest trying with the unsupported system tarball instead of the deb package files.
@nipsky: is the teamviewerd.service running (systemctl status teamviewerd.service)?
nipsky commented on 2017-02-08 08:26 (UTC)
Hi, teamviewer freezes on start for me before even showing any GUI, here’s the terminal output:
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
Am I the only one with this problem?
swiftgeek commented on 2017-02-07 00:46 (UTC)
@otrazhenije no one should try it, at most magically i386 build works better for you (x86_64 works very reliable here FYI)
Don't give ideas for bypassing package manager on AUR -.-
otrazhenije commented on 2017-02-06 09:38 (UTC) (edited on 2017-02-06 12:58 (UTC) by otrazhenije)
Faced the same problem
Solved with:
1. Download https://download.teamviewer.com/download/teamviewer_i386.tar.xz
2. Extract
3. rsync to /opt/teamviewer, overwrite existing files
You should try
cubethethird commented on 2017-02-03 01:15 (UTC) (edited on 2017-02-06 05:20 (UTC) by cubethethird)
Link to relevant support thread:
https://community.teamviewer.com/t5/TeamViewer-12/Not-ready-Please-check-your-connection-after-upgrade-to-v12/m-p/2177
Users with this issue describe 3 possible causes/solutions:
- Incorrect DNS lookups -> change DNS server/manual entries
- Error in service startup -> restart the service
- Usage of IPv6 -> disable IPv6 in router/modem settings
Sadly none of these solutions work for me, including the Remmina workaround recommended.
summonholmes commented on 2017-01-28 00:03 (UTC)
Regarding the connection errors of the previous comments, I've found a temporary workaround. Install Remmina, then install the TeamViewer plugin (AUR). If teamviewerd is active, Remmina will execute TeamViewer in a connected state. Hope this helps.
joanmanel commented on 2017-01-26 13:37 (UTC)
Hey purboo, what exactly did you do, because I executed that command, then open teamviewer, and I get the same error.
purboo commented on 2017-01-22 08:10 (UTC)
I got this error:
"Not Ready. Please check your connection. "
And it works after I execute this command:
$ sudo systemctl restart teamviewerd.service
I am very curious about what causes the no-connection problem.
wangyue9014 commented on 2017-01-17 08:57 (UTC)
can't connect to server.
it say:
Not ready. Please check your connection.
joanmanel commented on 2017-01-16 17:25 (UTC)
I have the same problems. It asks for a proxy even though I am not using one.
eri commented on 2017-01-11 10:46 (UTC) (edited on 2017-01-11 10:46 (UTC) by eri)
pls add line in /usr/share/applications/com.teamviewer.TeamViewer.desktop
StartupWMClass=TeamViewer.exe
It fixes icon in gnome-shell dock (and possibly unity and cinnamon)
https://github.com/jake-phy/WindowIconList/issues/30#issuecomment-156702093
grigruss commented on 2017-01-08 13:07 (UTC) (edited on 2017-01-08 13:31 (UTC) by grigruss)
Error: No network connection. Check the proxy settings.
I tried to set the default, and then as suggested by @maofree. Both methods give me this error.
P.S.: And method by kgizdov also did not help...
Maybe need to add some user to some group?
aptx commented on 2017-01-03 13:31 (UTC)
If I download the .tar.xz file from the official page of teamviewer, it is possible to run the program without a daemon. Since I do not trust a proprietary program to run as root on my system (or even as my standard user - I am using a sudo wrapper and a dedicated user instead), I was wondering why this does not seem to be possible with this package.
maofree commented on 2017-01-01 15:09 (UTC)
Hi
I've solved the connection error removing all lib32 dependencies leaving only the row of libxtst. The GUI will be opened after 30 seconds
bye
kgizdov commented on 2016-12-30 00:42 (UTC)
This is what I use - https://gist.github.com/kgizdov/e3e73d62bd3b491bdf06a31f04bdee89
aajoshi commented on 2016-12-29 18:02 (UTC) (edited on 2016-12-29 18:25 (UTC) by aajoshi)
You need to enable multilib packages:
https://wiki.archlinux.org/index.php/multilib
This will get rid of lib32 related dependency errors. No need to modify the package build script or anything.
Additionally, teamviewer won't work on wayland!
https://community.teamviewer.com/t5/TeamViewer-11/No-connection-to-TeamViewer-server/m-p/720#M199
Make sure that you are not running Wayland, switch to xorg for wine related applications.
mozo commented on 2016-12-21 10:26 (UTC)
Unfortunately this doesn't works for me. I followed your advice and removed lib32- in the PKGBUILD, then uninstalled lib32-libpng12 and lib32-libjpeg6-turbo. Restart and Teamviewer is "Not ready. Please check your connection". Back to the beta again...
mjago85 commented on 2016-12-21 03:53 (UTC)
@kgizdov +1 to this.
I just wanted to add that after editing the PKGBUILD to point to the 64-bit equivalents of the listed dependencies (for those needing instruction, remove "lib32-" from the start of each library listed in the "depends_x86_64" section of the PKGBUILD) and updating TeamViewer with this edited PKGBUILD, yaourt noted that lib32-libpng12 and lib32-libjpeg6-turbo were no longer required by any installed package, so I removed these. After rebooting the system, TeamViewer 12 appears functional.
My guess is that the 32-bit versions of libpng12 and libjpeg6-turbo were installed on my system with earlier versions of TeamViewer, but these libraries now clash with TeamViewer 12. As indicated in your namcap output, there appears to be a bit of work with fixing the dependencies in this package.
kgizdov commented on 2016-12-20 17:53 (UTC) (edited on 2016-12-20 17:56 (UTC) by kgizdov)
OK, so this doesn't need the multilib libraries any more. I just edited the PKGBUILD and installed with the 64 bit libs and it runs absolutely fine. Please put the correct dependencies as this might be contributing to a lot of people's problems.
Also, if you run namcap on the pkg file you get:
teamviewer E: Symlink (usr/share/licenses/teamviewer/LICENSE) points to non-existing /opt/teamviewer/License.txt
teamviewer W: Directory (etc/teamviewer) is empty
teamviewer W: Directory (var/log/teamviewer12) is empty
teamviewer W: Referenced library 'usr/lib32/libXinerama.so.1' is an uninstalled dependency
teamviewer W: Referenced library 'usr/lib32/libpng12.so.0' is an uninstalled dependency
teamviewer W: Referenced library 'libwine.so.1' is an uninstalled dependency
teamviewer W: Referenced library 'usr/lib32/libjpeg.so.62' is an uninstalled dependency
teamviewer E: Dependency lib32-qt4 detected and not included (libraries ['usr/lib32/libQtXml.so.4', 'usr/lib32/libQtNetwork.so.4', 'usr/lib32/libQtGui.so.4', 'usr/lib32/libQtDBus.so.4', 'usr/lib32/libQtWebKit.so.4', 'usr/lib32/libQtCore.so.4'] needed in files ['opt/teamviewer/tv_bin/TVGuiDelegate', 'opt/teamviewer/tv_bin/RTlib/libQtNetwork.so.4', 'opt/teamviewer/tv_bin/RTlib/libQtDBus.so.4', 'opt/teamviewer/tv_bin/RTlib/libQtXml.so.4', 'opt/teamviewer/tv_bin/RTlib/plugins/systemtrayicon/libsni-qt.so', 'opt/teamviewer/tv_bin/RTlib/libQtWebKit.so.4', 'opt/teamviewer/tv_bin/RTlib/libQtGui.so.4'])
teamviewer W: Dependency included and not needed ('libpng12')
teamviewer W: Dependency included and not needed ('libxinerama')
teamviewer W: Dependency included and not needed ('libjpeg6-turbo')
teamviewer W: Dependency included and not needed ('libxtst')
These need to be addressed.
WFV commented on 2016-12-18 20:10 (UTC) (edited on 2016-12-18 21:34 (UTC) by WFV)
After re-installing 12 (after downgrade), still get mixed results - same with starting from terminal as nipsky, times out and get the proxy error message on the gui. Doing this restarts it to working, but isn't guaranteed at next reboot:
# systemctl stop teamviewerd
# systemctl enable teamviewerd
# systemctl start teamviewerd
the gui launches starting the service from systemctl and then connects
EDIT: or just # systemctl restart teamviewerd works, maybe service is trying to start too soon in the boot?
nipsky commented on 2016-12-18 10:39 (UTC)
Hi, teamviewer opens no window for me when I start it, all I get in the console is:
Init...
CheckCPU: SSE2 support: yes
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
The daemon is running of course, and also I already deleted the profile folder, didn’t help. Are there any debug options to get more out of it?
shoko commented on 2016-12-16 20:25 (UTC)
Since the upgrade to 12 teamviewerd will only work sporadically... I have to stop/start it 4-5times till it works. Same error messages as the others. I use Manjaro.
cereal.kkiller commented on 2016-12-13 11:25 (UTC)
Hi guys,
has the issue reported by
@keysona
@Syco
@M-Gregoire
@blackace306
@edio
regarding the connection between two Arch machines been resolved in any way?
Override commented on 2016-12-11 03:57 (UTC)
For anyone getting the "teamviewer daemon is not running!" message just type these commands into the terminal:
-sudo systemctl enable teamviewerd.service <ENTER>
then
-systemctl start teamviewerd.service <ENTER>
So far everytime I've started Teamviewer up after shuting my machine down it hasn't given me any errors yet.
WFV commented on 2016-12-10 20:14 (UTC)
Get same problem, Teamviewer won't connect and says check proxy settings. Sometimes it connects if I restart teamviewerd and reload daemons. Once connected it stays connected until next reboot. Just noting that occasionally I get same proxy message on a Windows 10pc with its equivalent rev 12. I downgraded to TV11 for now. (not wayland)
mozo commented on 2016-12-09 15:13 (UTC)
@Ham_Radio No, I'm with X11.
Angel_Caido commented on 2016-12-09 00:58 (UTC)
Same problem here. After upgrading teamviewer, I get the message "Only LAN connections are possible".
I am using Xorg.
The result of "loginctl show-session 1 -p Type" is:
Type=x11
I will have to downgrade.
Ham_Radio commented on 2016-12-08 01:18 (UTC)
@mozo @dantopa Are you guys using wayland?
mozo commented on 2016-12-07 13:00 (UTC)
Mine doesn't connect too but nobody cares...
dantopa commented on 2016-12-06 23:19 (UTC)
Latest update is not connecting to internet. How to resolve the issue? Thanks
spsf64 commented on 2016-12-06 22:13 (UTC)
12.0.71510-6 Fixed the problem!!
Thanks for the fast response!
spsf64 commented on 2016-12-06 21:16 (UTC)
@swiftgeek the installer is creating 2 entries with same name in the menu (XFCE)
tm-x commented on 2016-12-06 10:43 (UTC)
With the latest update, the location of the desktop file changed. I had to manually fix it from:
teamviewer.desktop -> /opt/teamviewer/tv_bin/desktop/teamviewer-teamviewer12.desktop
to:
com.teamviewer.TeamViewer.desktop -> /opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop
saverio commented on 2016-12-06 08:54 (UTC)
Thanks for bringing TeamViewer here in AUR :)
hubate commented on 2016-12-05 19:58 (UTC)
Thanks for no. 12!
mozo commented on 2016-12-05 19:41 (UTC)
Not ready:
http://i66.tinypic.com/2hre5q9.jpg
I just upgraded from v.11 which works fine. There isn't any problems with the beta too. Just this new version can't connect to internet. I can't even login at Computers and Contacts panel. Downgrade to beta ant it is working again.
Ham_Radio commented on 2016-12-05 15:14 (UTC)
When are going to get version 12? I'm having to use the Chrome app because I can't connect to some of my clients :(
mastercoms commented on 2016-12-04 04:54 (UTC)
The not connected issue is because you guys are using Wayland accidentally. Use Xorg.
commented on 2016-12-02 23:00 (UTC)
--- /home/gregf/teamviewer/PKGBUILD 2016-10-15 08:30:52.000000000 -0400
+++ PKGBUILD 2016-12-02 17:58:00.230894284 -0500
@@ -1,8 +1,8 @@
# Maintainer: Alex Taber <aft dot pokemon at gmail dot com>
pkgname=teamviewer
-pkgver=11.0.67687
-pkgrel=4
+pkgver=12.0.71510
+pkgrel=1
pkgdesc='All-In-One Software for Remote Support and Online Meetings'
arch=('i686' 'x86_64')
url='http://www.teamviewer.com'
@@ -30,8 +30,8 @@ depends_i686=(
install=teamviewer.install
source_x86_64=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_amd64.deb")
source_i686=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
-md5sums_i686=('312d6eea860a9314e19140a8a9378e1d')
-md5sums_x86_64=('2504895aa8e50da78d68235630402c51')
+sha512sums_i686=('edc1e5823939f20a9879bd29d952a728275f5f190ad434b95e71e886086b8aca407749d5671284cec9b20007aaa4b5907c84a83cc4921f9f715738cd33c704db')
+sha512sums_x86_64=('543826bce6e973cc7100d6107ff57a289222376f5df32b15d162fae9136cb82e3029bbe7f1da807b2148a834fc8e9a3013d2fb4e81a2c5beda5fc7bdb3c7ac16')
prepare() {
echo "If the install fails, you need to uninstall Teamviewer 10"
commented on 2016-12-02 22:59 (UTC)
--- PKGBUILD 2016-12-02 17:58:00.230894284 -0500
+++ /home/gregf/teamviewer/PKGBUILD 2016-10-15 08:30:52.000000000 -0400
@@ -1,8 +1,8 @@
# Maintainer: Alex Taber <aft dot pokemon at gmail dot com>
pkgname=teamviewer
-pkgver=12.0.71510
-pkgrel=1
+pkgver=11.0.67687
+pkgrel=4
pkgdesc='All-In-One Software for Remote Support and Online Meetings'
arch=('i686' 'x86_64')
url='http://www.teamviewer.com'
@@ -30,8 +30,8 @@ depends_i686=(
install=teamviewer.install
source_x86_64=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_amd64.deb")
source_i686=("https://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
-sha512sums_i686=('edc1e5823939f20a9879bd29d952a728275f5f190ad434b95e71e886086b8aca407749d5671284cec9b20007aaa4b5907c84a83cc4921f9f715738cd33c704db')
-sha512sums_x86_64=('543826bce6e973cc7100d6107ff57a289222376f5df32b15d162fae9136cb82e3029bbe7f1da807b2148a834fc8e9a3013d2fb4e81a2c5beda5fc7bdb3c7ac16')
+md5sums_i686=('312d6eea860a9314e19140a8a9378e1d')
+md5sums_x86_64=('2504895aa8e50da78d68235630402c51')
prepare() {
echo "If the install fails, you need to uninstall Teamviewer 10"
commented on 2016-12-02 22:39 (UTC)
@swiftgeek if you no longer have time to keep this up to date could you allow one of us to take it over?
bastiendurel commented on 2016-12-01 11:52 (UTC)
teamviewer 12/stable is out now, so the package is really out of date this time ;)
dhtseany commented on 2016-11-22 16:15 (UTC)
@swiftgeek... People likely keep flagging this package as out of date because many of us are still dealing with broken installs after a recent ugprade of our systems. It's been over a month and none of the comments suggesting fixes for resolution are fixing the "Not connected" issues. Just figured you'd want to know.
By the way, if you want a system for troubleshooting/debugging my laptop is still impacted and I'd be happy to assist.
swiftgeek commented on 2016-11-22 09:27 (UTC) (edited on 2016-11-22 09:28 (UTC) by swiftgeek)
Teamviewer is (for now) a beta version, please stop flagging package out-of-date -.-
IF you want to install beta version:
https://aur.archlinux.org/packages/teamviewer-beta/
syakyou commented on 2016-11-21 11:10 (UTC)
@Angel_Caido Thanks a lot!
Angel_Caido commented on 2016-11-19 15:50 (UTC)
Teamviewer wasn't launching for me after I updated/upgraded my system. I was having this error message -when running teamviewer from the terminal-:
Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
0. I killed any teamviewer process running in the background.
1. I removed the teamviewer profile folder located at:
/home/<your user>/.config/teamviewer
2. I ran:
sudo teamviewer --daemon start
3. I started teamviewer without a problem.
I Hope this helps.
Sylvain_07 commented on 2016-11-14 19:48 (UTC) (edited on 2016-11-14 19:49 (UTC) by Sylvain_07)
have the same problem...
have remouved this version and I use v11.0.67687 (tar.xz) to
https://www.teamviewer.com/fr/download/linux/
: it work perfectly
milocario commented on 2016-10-20 12:25 (UTC)
I had the same connection problem "Not ready. Please check your connection", but it was related to Xorg. I recommend uninstalling gdm and execute gnome with startx to see the error.
It was resolved by removing the .conf files in /etc/X11
arjesus commented on 2016-10-20 10:42 (UTC) (edited on 2016-10-28 15:55 (UTC) by arjesus)
Gnome DE: "Not ready. Please check your connection"
Cinnamon DE: OK
XFCE DE: OK
Edit: "Start TeamViewer with system" and "Close to tray" options are not working.
Edit: No TeamViewer options are working.
Edit: Start TV in the tray workaround:
wmctrl -c 'Computers & Contacts' && wmctrl -c 'TeamViewer'
shieldwed commented on 2016-10-20 07:46 (UTC)
Why not using http://download.teamviewer.com/download/teamviewer_amd64.deb for x86_64 builds?
zhblu commented on 2016-10-20 01:16 (UTC)
Same problem here after upgraded gnome-shell, but it is working fine under KDE plasma.
paki976 commented on 2016-10-18 14:12 (UTC)
"Not ready. Please check your connection". Downloading the tar.zx and running it from homedir is a workaround.
nnnms commented on 2016-10-18 11:51 (UTC)
Same problem as el.Quero: "Not ready. Please check your connection".
el.Quero commented on 2016-10-17 16:37 (UTC)
Hi, I've noticed that this Teamviewer package ships a version that don't work: after opening it reports the error message "Not ready. Please check your connection" near the bottomleft windows corner.
The build downloaded from the teamviewer official site works without any issue.
Maybe this package uses the wrong teamviewer version because the urls are different: the one I've used is https://download.teamviewer.com/download/teamviewer_i386.deb.
Do you have the same issue?
vdemin commented on 2016-10-12 18:34 (UTC)
@swiftgeek Why do you ignore comments about non-working remote control? Please replace libxtst with lib32-libxtst in depends_x86_64 section.
z3ntu commented on 2016-10-12 18:24 (UTC) (edited on 2016-10-12 18:24 (UTC) by z3ntu)
Please reset the pkgrel back to 1 when bumping the pkgver variable.
keysona commented on 2016-10-10 15:05 (UTC)
Same here, mouse and keyboard isn't work.
The output is fine.
Syco commented on 2016-10-09 11:13 (UTC)
@M-Gregoire
@blackace306
@edio
Same here, I use teamviewer on 4 pc, all with archlinux, without any problem.
Today I did a new installation and I can't get it to work.
Connection works perfectly fine, but no input from mouse or keyboard.
Daemon is started and systemctl status teamviewerd shows not errors.
commented on 2016-10-07 07:31 (UTC)
@blackace306
@edio
Did you typed :
sudo systemctl enable teamviewerd
sudo teamviewer --daemon start
After install ?
edio commented on 2016-09-28 19:11 (UTC)
@blackace306
Have the same issue as you. That's a bummer, I can't now help my parents remotely.
blackace306 commented on 2016-09-26 17:27 (UTC)
I am having an issue when I try to connect to my Arch machines. The screen shows up, and it connects, however I cannot control the screen from the remote device. Any ideas?
dopeadmin commented on 2016-09-20 05:28 (UTC)
what is the package name ? I try to install and get no found after makepkg command
I tried teamviewer , teamviewer 11 .. no luck
seagull commented on 2016-09-16 18:15 (UTC) (edited on 2016-09-16 18:16 (UTC) by seagull)
Enabling the multilib-repo is required! to get the 32-bit libraries.
To use the multilib repository, uncomment the [multilib] section in /etc/pacman.conf (Please be sure to uncomment both lines):
[multilib]
Include = /etc/pacman.d/mirrorlist
See: https://wiki.archlinux.org/index.php/Multilib
PhotonX commented on 2016-09-11 11:21 (UTC)
After two years I am still stuck with the problem that the teamviewer service fails to start automatically though being enabled:
$ systemctl status teamviewerd
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled; vendor
Active: inactive (dead)
Starting manually works though. Any thoughts on how to solve the autostart problem?
Glaeqen commented on 2016-08-24 13:54 (UTC)
Is DEB/RPM package for Debianlike, Fedoralike more native solution as an app than this WINE trash "for other linux distros"? It's really horrible..
yrds commented on 2016-08-18 23:35 (UTC)
viperpaulo is right! You need lib32-libxtst to working remote control
viperpaulo commented on 2016-08-08 14:10 (UTC)
Hi ! lib32-libxtst is missing, it's mandatory to get remote control.
step21 commented on 2016-08-05 15:52 (UTC)
@vdemin If I change this manually, should this fix the "no kb/mouse on incoming connection to arch" issue? Such as described here with libxtst as a fix https://bbs.archlinux.org/viewtopic.php?id=206014 But seeing as I installed it this morning it should be fine ...right?
vdemin commented on 2016-07-31 17:23 (UTC)
@swiftgeek Please replace libxtst with lib32-libxtst in depends_x86_64 section.
swiftgeek commented on 2016-07-29 06:14 (UTC)
@tsouzar elabolarate, paste log somewhere like dpaste.com, add `uname -a` output
tsouzar commented on 2016-07-28 22:30 (UTC)
Should't lib32-* packages be required only for 64bit systems?
They are being required on my 32bit Arch, instead of others without lib32 prefix. Because of this, I can't install teamviewer. Somebody suggested to enable [multilib] repository, but I don't need it, that is for 64bit systems. What the shit is going here? Other packages with options for both 32bit and 64bit systems doesn't have such problems.
evil5826 commented on 2016-07-26 23:27 (UTC)
If anyone is having issue with mouse and keyboard not working, install lib32-libxtst. Found this in an old arch bbs post from 4-22-16.
rabo commented on 2016-07-25 05:36 (UTC)
==> Validating source files with sha256sums...
libjpeg-turbo-1.5.0.tar.gz ... Passed
==> Extracting sources...
-> Extracting libjpeg-turbo-1.5.0.tar.gz with bsdtar
==> Starting build()...
/tmp/yaourt-tmp-ralf/aur-lib32-libjpeg6-turbo/./PKGBUILD: line 27: ./configure: Permission denied
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build lib32-libjpeg6-turbo.
HarlemSquirrel commented on 2016-07-14 16:19 (UTC)
I was able to get it working with lib32-libjpeg-turbo and lib32-libpng
cybertron commented on 2016-07-07 14:05 (UTC) (edited on 2016-07-07 14:47 (UTC) by cybertron)
The problem here is that package lib32-libjpeg6-turbo is needed, but it also works with the core variant, just have to change the package name to "lib32-libjpeg-turbo" in PKGBUILD
hepha commented on 2016-07-06 07:13 (UTC)
hello
Two have the same installation file to be wrong, I can perform the installation lib32-libjpeg-turbo
multilib/lib32-libjpeg-turbo
aur/lib32-libjpeg6-turbo
swiftgeek commented on 2016-06-28 11:19 (UTC) (edited on 2016-06-28 11:26 (UTC) by swiftgeek)
@marungbukid: teamviewer is not using that (check with namcap yourself) and this page is not dedicated for accessing teamviewer support -.-
(You can even access tty in teamviewer 11, and yes it works)
@pschichtel x86_64 or i686 ?
EDIT: ok looked up debian, indeed x86_64 version may be needed (not lib32)
marungbukid commented on 2016-06-28 09:42 (UTC)
Confirmed. Input from keyboard and mouse worked for me upon installing lib32-libxtst package. Is there a way to run teamviewer from login screen?
pschichtel commented on 2016-06-15 21:05 (UTC)
I cannot confirm TankMissiles suggestion: I don't have that dependency (lib32-libxtst, libxtst however is) installed and the input (keyboard and mouse) is working fine.
TankMissile commented on 2016-06-15 17:35 (UTC) (edited on 2016-06-15 17:35 (UTC) by TankMissile)
For people who can't use their mouse and keyboard, install the lib32-libxtst package. It solved the problem for me. It should be made a dependency.
dhtseany commented on 2016-06-11 21:39 (UTC)
Reporting the same problem as @trekjunky... Connects fine but no input working keyboard or mouse.
trekjunky commented on 2016-06-11 05:08 (UTC)
Since updating to lib32-libxcb 1.12-2, I now get the GUI to load and I can login and I can start a session from a client to my host, BUT no keystrokes nor mouse works to remote control the host. Keyboard and mouse input doesn't work.
I have Arch Linux, KDE w/Plasma 5, teamviewer 11.0.57095-4, and full version of wine-1.9.11. Please help. I have searched online for a solution but everything I tried failed to work.
shoko commented on 2016-06-09 18:41 (UTC)
For privacy reasons I prefer not enable/start teamviewerd.service by default. So I use a short shell script to invoke teamviewer:
#!/bin/sh
systemctl start teamviewerd
/opt/teamviewer/tv_bin/script/teamviewer
systemctl stop teamviewerd
To avoid the password prompt for the systemctl actions add this to /etc/polkit-1/rules.d/90-teamviewerd.rules:
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.systemd1.manage-units") {
if (action.lookup("unit") == "teamviewerd.service") {
var verb = action.lookup("verb");
if (verb == "start" || verb == "stop" || verb == "restart") {
return polkit.Result.YES;
}
}
}
});
Maybe this is useful to others.
hcj1009 commented on 2016-06-07 15:57 (UTC)
@everyone, the bug caused by lib32-libxcb 1.12 is now fixed. The latest version is 1.12-2, and it works pretty good. The bug page has been closed too. You can now safely upgrade lib32-libxcb to 1.12-2.
ronjouch commented on 2016-06-04 18:54 (UTC)
@everyone concerned by lib32-libxcb 1.12 breaking teamviewer, here's the relevant bug: https://bugs.archlinux.org/task/49560
I already mentioned TeamViewer is concerned so there's no need to add "+1 teamviewer broken too" comments, but you might want to subscribe to the bug to be informed about an eventual fix so that you can remove the IgnorePkg when the problem gets fixed :)
micsnare commented on 2016-05-31 20:24 (UTC)
@cryzed: thanks a lot :)))))
for everyone facing the same problem, downgrade the broken dependency by the steps mentioned below, and afterwards add the following to your /etc/pacman.conf
IgnorePkg = lib32-libxcb
so that it won't be upgraded with the next update..
Ham_Radio commented on 2016-05-30 23:27 (UTC)
Update of lib32-libxcb from verion 1.11.1-1 to 1.12-1 broke TeamViewer. The GUI no longer shows up. Downgrading the package fixes the issue.
cd /var/cache/pacman/pkg/
sudo pacman -U lib32-libxcb-1.11.1-1-x86_64.pkg.tar.xz
cryzed commented on 2016-05-30 22:59 (UTC)
@micsnare: https://wiki.archlinux.org/index.php/pacman#Skip_package_from_being_upgraded
micsnare commented on 2016-05-30 22:57 (UTC)
one more question:
is there a way to tell pacman to skip this package for future updates, e.g
pacman -Syu ?
micsnare commented on 2016-05-30 21:35 (UTC)
guys, you are legends! thanks for helping me, now it works for me as well :)
thanks y'all
abeltje commented on 2016-05-30 21:33 (UTC)
@micsnare: try to fetch from here https://archive.archlinux.org/packages/l/lib32-libxcb/
cryzed commented on 2016-05-30 21:27 (UTC) (edited on 2016-05-30 21:28 (UTC) by cryzed)
@micsnare: It's likely in /var/cache/pacman/pkg if you had it installed at some point. If not, you can also use downgrade (https://aur.archlinux.org/packages/downgrade/) to fetch and install an older version of a package.
Please note that this is unsupported and might break some stuff in funny ways.
micsnare commented on 2016-05-30 21:25 (UTC)
@abeltje:
just tried that, unfortunately pacman is unable to find that package :(
abeltje commented on 2016-05-30 21:20 (UTC)
had the same problem, did a downgrade of lib32-libxcb and get a gui again.
sudo pacman -U lib32-libxcb-1.11.1-1-x86_64.pkg.tar.xz
Invisible commented on 2016-05-30 20:48 (UTC)
can some one help me??
I have the same error and i need teamviewer now...
Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI
yesterday it works perfect -.-
pschichtel commented on 2016-05-30 20:44 (UTC)
ops sorry for flagging out-of-date, I thought the version number is in sync with the windows version
pschichtel commented on 2016-05-30 20:20 (UTC)
Seems to be related to the wine upgrade to 1.9.11
micsnare commented on 2016-05-30 19:54 (UTC)
having exactly the same problem here... not even teamviewer10 works for me :(
Init...
Checking setup...
Launching TeamViewer ...
:(
gorki.b commented on 2016-05-30 17:36 (UTC)
Hello
Yes exact the same here
$ teamviewer
Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI
cryzed commented on 2016-05-30 16:42 (UTC)
With an up-to-date Arch installation the current version doesn't seem to launch successfully anymore:
$ teamviewer
Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
Launching TeamViewer ...
Launching TeamViewer GUI ...
However the GUI never shows up. Is anyone else having this issue? I made sure to restart teamviewerd at least once, moved ~/.teamviewer for a fresh configuration and killed all related processes.
ThePilot commented on 2016-05-13 15:29 (UTC)
The fonts look pretty awful by default in Teamviewer. Does anyone have any suggestions for making them look better?
mbrandalero commented on 2016-05-06 16:57 (UTC) (edited on 2016-05-06 17:01 (UTC) by mbrandalero)
I am running into the same issue as @NJCS below: No remote control is possible in the machine where this is installed on. Connection is setup OK, but no kb/mouse input is detected.
EDIT: Following @jungliztik 's solution below, I installed lib32-libxtst and restarted the teamviewer daemon. Everything is working now. I believe this package should be a required dependency.
Bazon commented on 2016-05-04 04:59 (UTC)
@swiftgeek:
OK, then the problem is in the other PKGBUILD. And in fact, as I tried to install lib32-libjpeg6 package, I got lib32-libjpeg6-turbo:
$ sudo pacman -S lib32-libjpeg6
warning: lib32-libjpeg6-turbo-1.4.2-1 is up to date -- reinstalling
So OK, no general problem.
swiftgeek commented on 2016-05-03 23:39 (UTC)
@Bazon i don't see lib32-libjpeg6 package anywhere
NJCS commented on 2016-05-02 22:32 (UTC)
On both Antegros-Cinnamon and Antegros-KDE, I cannot remotely control the system this is installed on. I can control other systems though. I am not sure how to go about solving this problem.
Bazon commented on 2016-05-01 04:49 (UTC)
Does it really need to depend on lib32-libjpeg6-turbo and not "only" on lib32-libjpeg6 (which is provided by/conflicts lib32-libjpeg6-turbo)?
This dependency caused some trouble for me: Another, yet installed package depends on lib32-libjpeg6. So a teamviewer-update was not possible, as teamviewer now depends on lib32-libjpeg6-turbo which conflicts lib32-libjpeg6.
So I think a good solution would be: Change dependency to lib32-libjpeg6: That would cause no trouble for people who want lib32-libjpeg6-turbo, as lib32-libjpeg6-turbo provides lib32-libjpeg6, and it would avoid the trouble I described before.
z3ntu commented on 2016-04-30 10:09 (UTC)
The .install file should say "sudo systemctl enable --now teamviewerd" otherwise the daemon will only be started after a reboot.
swiftgeek commented on 2016-04-29 16:13 (UTC)
@FadeMind, ocetox
can confirm deps as written by FadeMind solving indicator (it's not the old systray xembed way) issue.
Tested with enlightenment e21
ocetox commented on 2016-04-29 15:49 (UTC)
libjpeg6-turbo solve tray icon problem
FadeMind commented on 2016-04-26 14:20 (UTC) (edited on 2016-04-26 14:23 (UTC) by FadeMind)
Please add depend
lib32-libjpeg6-turbo for depends_x86_64
and libjpeg6-turbo for depends_i686
against required file and realuser comment
/usr/lib32/libjpeg.so.62 is part of lib32-libjpeg6-turbo package
realuser commented on 2016-04-26 14:11 (UTC)
I have all dependencies installed. But i had these issues:
- a chat window did not open.
- icon missing in tray.
I've created a link
ln -s /usr/lib32/libjpeg.so /usr/lib32/libjpeg.so.62
And all problems gone!
/usr/lib32/libjpeg.so is owned by lib32-libjpeg-turbo 1.4.2-1
FadeMind commented on 2016-04-22 14:50 (UTC) (edited on 2016-04-22 14:52 (UTC) by FadeMind)
RubenKelevra:
$ ldd /opt/teamviewer/tv_bin/teamviewerd
linux-gate.so.1 (0xf775b000)
libdbus-1.so.3 => /usr/lib32/libdbus-1.so.3 (0xf76af000)
librt.so.1 => /usr/lib32/librt.so.1 (0xf76a6000)
libdl.so.2 => /usr/lib32/libdl.so.2 (0xf76a1000)
libm.so.6 => /usr/lib32/libm.so.6 (0xf764c000)
libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf762e000)
libc.so.6 => /usr/lib32/libc.so.6 (0xf7479000)
/lib/ld-linux.so.2 (0xf775d000)
$ ldd /opt/teamviewer/tv_bin/TeamViewer_Desktop
linux-gate.so.1 (0xf7798000)
libdbus-1.so.3 => /usr/lib32/libdbus-1.so.3 (0xf76ec000)
librt.so.1 => /usr/lib32/librt.so.1 (0xf76e3000)
libdl.so.2 => /usr/lib32/libdl.so.2 (0xf76de000)
libm.so.6 => /usr/lib32/libm.so.6 (0xf7689000)
libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf766b000)
libc.so.6 => /usr/lib32/libc.so.6 (0xf74b6000)
/lib/ld-linux.so.2 (0xf779a000)
AND infact Teamviewer is just customized WINE environment app with 32-bit.
RubenKelevra commented on 2016-04-22 14:38 (UTC)
Why are there 32 bit packages for the amd64 version? Are they really needed?
FadeMind commented on 2016-04-17 09:19 (UTC)
KinG-InFeT first install depends next build package.
Simply install teamviewer via yaourt
yaourt -S --noconfirm teamviewer
instead of packer tool.
KinG-InFeT commented on 2016-04-17 09:16 (UTC)
[benzi@benzi-pc ~]$ packer -S teamviewer
Aur Targets (1): teamviewer
Proceed with installation? [Y/n] y
Edit teamviewer PKGBUILD with $EDITOR? [Y/n] n
Edit teamviewer.install with $EDITOR? [Y/n] n
==> Creazione del pacchetto: teamviewer 11.0.53191-2.3 (dom 17 apr 2016, 11.15.36, CEST)
==> Controllo delle dipendenze durante l'avvio in corso...
==> Dipendenze mancanti:
-> lib32-libpng12
-> lib32-libxinerama
==> Controllo delle dipendenze durante la compilazione in corso...
==> ERRORE: Impossibile risolvere tutte le dipendenze.
The build failed.
jungliztik commented on 2016-04-14 13:55 (UTC)
I had the issue where I could connect to my remote pc but not control it (no keyboard or mouse inputs were being recognised).
I had to install the lib32-libxtst package and then after restarting the teamviewer service, I could control the desktop as expected.
CupIvan commented on 2016-04-05 15:36 (UTC)
I installed it without this packages:
lib32-libpng12 (x86_64)
lib32-libxinerama (x86_64)
plonqor commented on 2016-03-29 11:04 (UTC)
@ian_x86 I also have this problem on KDE. Did you find a fix?
comgunner commented on 2016-03-23 14:53 (UTC)
missing dependencies, installed manually with "packer -S"
lib32-fontconfig
lib32-libpng12
lib32-libxinerama
plonqor commented on 2016-03-23 02:03 (UTC) (edited on 2016-03-23 02:07 (UTC) by plonqor)
I can confirm JDCNS's suspicions. My mouse/keyboard now works.
These are the packages that teamviewer10 depends on that teamviewer (11) doesn't list. After installing these manually, the issue was fixed. Note I uninstalled teamviewer before installing the below, not sure if that matters.
- lib32-alsa-lib
- lib32-libxtst
- lib32-libxdamage
- lib32-libxrandr
JDCNS commented on 2016-03-20 05:39 (UTC)
I'd been struggling with getting the keyboard and mouse to work under 11 ever since I wiped my hard drive and reinstalled Arch. None of these suggestions worked for me except the one by JoeKnock90. I uninstalled teamviewer, but it did not remove the /etc/teamviewer directory. After that, I was able to install the teamviewer10 package, prove that it worked, uninstalled it and reinstalled this one. It now works.
So, I must also conclude that something is missing from the dependencies. I did not write them down, but I noticed uninstalling 10 left 4 "unneeded" packages behind. I really only expected 2: lib32-png12 and lib32-jpeg.
swiftgeek commented on 2016-03-15 17:08 (UTC) (edited on 2016-03-15 17:09 (UTC) by swiftgeek)
@astronautlevel: Also whenever you just change metadata (like description, (make,opt)deps) that do not affect resulting package files in any meaningful way, please do not bump pkgrel - git history is widely accessible nowadays.
biinari commented on 2016-03-15 15:00 (UTC)
Why does this package use a `major.minor` format in `pkgrel` instead of the normal single number? This causes an issue where aura does not think the package needs to be upgraded https://github.com/aurapm/aura/issues/403 (I do not know whether any other AUR tools do the same but yaourt picks it up fine).
astronautlevel commented on 2016-03-10 12:10 (UTC)
@adhokshajm
Install the package using Yaourt or by building it yourself - lib32-libpng12 is an AUR dependency.
adhokshajm commented on 2016-03-10 11:53 (UTC)
in PKGBUILD, line 15 "lib32-libpng12" must be changed to "lib32-libpng", otherwise pacman will throw following error
error: target not found: lib32-libpng12
==> ERROR: 'pacman' failed to install missing dependencies.
Platform: Arch x86_64 Gnome
ian_x86 commented on 2016-03-10 01:53 (UTC)
Using teamviewer 11 on xfce4 but it won't minimize/close to tray menu, any tricks to fix this?
astronautlevel commented on 2016-03-08 12:24 (UTC)
@tsouzar
You'll need to enable multilib repositories to install the 32 bit libraries on your system. See: https://wiki.archlinux.org/index.php/multilib
@cybertron
gcc-multilib is needed to compile lib32-libpng12. You can install gcc again if you want to once teamviewer is installed.
severach commented on 2016-03-08 01:33 (UTC)
Yes, for lib32-libpng12 which you must compile.
cybertron commented on 2016-03-07 21:11 (UTC)
So gcc-multilib is really needed?
V1del commented on 2016-03-07 19:18 (UTC)
@bil-elmossaoui
There's a systemd service and the post-install message in your terminal tells you of that fact.
bil-elmoussaoui commented on 2016-03-07 18:51 (UTC) (edited on 2016-03-07 18:54 (UTC) by bil-elmoussaoui)
Whenever i open teamviewer i receive a message asking me to execute this command as root
teamviewer --daemon start
is there a way to fix this?
Update: fixed with sudo teamviewer daemon enable
astronautlevel commented on 2016-03-07 14:24 (UTC)
Re-added lib32-libpng12 to x86_64 dependencies
rafalp commented on 2016-03-07 14:14 (UTC)
There is no connect button visible. This can be fixed by installing lib32-libpng12 (on x64).
eworm commented on 2016-03-02 11:35 (UTC)
Please revert your last change! (lib32-)libpng12 is required to display all graphical elements. User ata is suffering a missing (lib32-)libpng12, look at his screenshot...
tsouzar commented on 2016-03-01 23:01 (UTC)
@pelo I still can't install teamviewer in my i686 system, same error messages:
:: no results found for lib32-fontconfig
:: no results found for lib32-libpng
:: no results found for lib32-libsm
:: no results found for lib32-libxinerama
:: no results found for lib32-libxrender
There's nothing such as "multilib" in my /etc/pacman.conf.
LKHN commented on 2016-02-29 22:31 (UTC)
@ata
Install lib32-libpng12 from AUR.
ata commented on 2016-02-29 15:08 (UTC)
Where connect button
http://i.hizliresim.com/a3DGlz.png
aligator commented on 2016-02-25 16:08 (UTC)
I had same problem as theLadder.
For me installing lib32-libpng12 worked, too.
phR0ze commented on 2016-02-24 14:32 (UTC)
I've tried all the suggestions here to no avail. As other have described I'm able to connect to the system and view the desktop fine just can't interact (i.e mouse/keyboard).
JoeKnock90 commented on 2016-02-23 14:51 (UTC) (edited on 2016-02-23 14:52 (UTC) by JoeKnock90)
@Jesse
I was getting the same thing. Try uninstalling teamviewer, installing teamviewer10, then uninstalling teamviewer10, and reinstalling teamviewer.
I know it sounds kind of stupid and I can't tell if it's a missing possibly optional dependency, but this worked for me on Arch Linux Kernel 4.4.1-2-ARCH with KDE 5.5.4
I should probably also mention that I used yaourt to do all of it.
nerdoc commented on 2016-02-23 08:04 (UTC)
OK then, seems that we should ask at TeamViewer's to upgrade their sowtware to a newer png version ;-)
Thanks anyway.
theLadder commented on 2016-02-22 13:50 (UTC)
This installed for me, but i had GUI problems, some buttons and textboxes did not render so i could not press the connect button for example.
Installing lib32-libpng12 from AUR solved that problem for me.
To find this out i downloaded the teamviewer.tar.gz package from teamviewer.com, extracted it, then ran ./tv-setup checklibs, and that told me that these where missing:
Analyzing dependencies (64 bit)...
All 64 bit dependencies seem to be satisfied!
Analyzing dependencies (32 bit)...
libjpeg.so.62 => not found
libpng12.so.0 => not found
The 32 bit libraries listed above seem to be missing.
libjpeg.so.62 is still missing but it seems to work anyway...
astronautlevel commented on 2016-02-20 00:37 (UTC)
@nerdoc
Thanks, I'll fix this in about two hours or so
nerdoc commented on 2016-02-20 00:33 (UTC)
@luislezcair Thanks - that solved the issue. libpng is sufficient to build/install the package. Should be updated.
Jesse commented on 2016-02-18 20:09 (UTC) (edited on 2016-02-19 18:51 (UTC) by Jesse)
There is a bug for me with this package. When I configure a host machine for sharing and remote control, I cannot control it from a guest remote login. I can see the host screen, but I can't use the mouse or keyboard to manage the machine.
Is anyone else having this problem? Is there a fix for this, or is this a bug that needs to be corrected?
(Running Antergos x64, KDE Plasma 5.5.4, kernel 4.4.1-2-ARCH)
Thanks!
luislezcair commented on 2016-02-18 18:20 (UTC)
I have the same problem with the dependencies as the users below. I solved it by editing the PKBUILD file and replacing the dependency "lib32-libpng12" with "lib32-libpng". Then it installed just fine.
KinG-InFeT commented on 2016-02-18 09:16 (UTC)
packer -S teamviewer
warning: teamviewer is flagged out of date
AUR (1): teamviewer
Proceed with installation? [Y/n] y
Installing AUR package: teamviewer
Edit teamviewer PKGBUILD? [y/N] n
Edit teamviewer.install? [y/N] n
==> Creazione del pacchetto: teamviewer 11.0.53191-2.1 (gio 18 feb 2016, 10.15.21, CET)
==> Controllo delle dipendenze durante l'avvio in corso...
==> Dipendenze mancanti:
-> lib32-libpng12
==> Controllo delle dipendenze durante la compilazione in corso...
==> ERRORE: Impossibile risolvere tutte le dipendenze.
The build failed.
nerdoc commented on 2016-02-04 21:20 (UTC)
There are some dependencies on other AUR packages like lib32-libpng12 - do I have to install them manually (argh!) or is there a way to install this teamviewer package with all it's (AUR) dependencies?
pelo commented on 2016-01-28 07:53 (UTC)
@tsouzar
Edit '/etc/pacman.conf' by uncommenting 'multilib' and its 'include' and do a 'pacman -Syu'. This will resolve the errors you get.
@kvasir
You could continue with the removal of 'gcc' and install 'gcc-multilib'. This is just used to compile the package. Once the package has been installed, you could use 'pacman' to install the normal 'gcc' 64-bit package.
tsouzar commented on 2016-01-28 06:09 (UTC)
There's something wrong. It's requiring x86_64 dependencies on a i686 system. This makes pacaur show following messages and can't proceed installing teamviwer:
:: no results found for lib32-fontconfig
:: no results found for lib32-libsm
:: no results found for lib32-libxinerama
:: no results found for lib32-libxrender
:: no results found for gcc-multilib
:: no results found for lib32-zlib
kvasir commented on 2016-01-27 21:37 (UTC)
/usr/lib/yaourt/util.sh: line 203: PKGBUILD: command not found
/usr/lib/yaourt/util.sh: line 203: teamviewer.install: command not found
==> Install or build missing dependencies for lib32-libpng12:
resolving dependencies...
looking for conflicting packages...
:: gcc-multilib and gcc are in conflict. Remove gcc? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: gcc-multilib and gcc are in conflict
astronautlevel commented on 2016-01-27 12:14 (UTC)
Done.
Also, Arch isn't officially supported by teamviewer, which could be leading to some people's tray problems.
cedricziel commented on 2016-01-27 08:20 (UTC)
Could you please use the https links to the source packages? Thx :)
BanderasPL commented on 2016-01-26 23:50 (UTC)
New version not helped.
astronautlevel commented on 2016-01-26 21:33 (UTC)
Upgraded to 11.0.53191, should fix tray problem.
BanderasPL commented on 2016-01-26 21:15 (UTC)
I've got tray problem too....
dsch commented on 2016-01-23 10:34 (UTC)
I have contacted TeamViewer with regards to the system tray problem and they assured me that it corrected in the latest version on their website.
eerie commented on 2016-01-14 18:47 (UTC) (edited on 2016-01-19 16:07 (UTC) by eerie)
~$ sudo systemctl enable teamviewerd.service
~$ sudo systemctl start teamviewerd.service
~$ teamviewer
Init...
XRandRWait: No value set. Using default.
XRandRWait: Started by user.
Checking setup...
/opt/teamviewer/tv_bin/wine/bin/wineserver: Symbol `wine_casemap_upper' has different size in shared object, consider re-linking
/opt/teamviewer/tv_bin/wine/bin/wineserver: Symbol `wine_casemap_lower' has different size in shared object, consider re-linking
wine client error:0: version mismatch 440/492.
Your wineserver binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?
astronautlevel commented on 2016-01-13 11:08 (UTC)
Alright, I'll get that up tonight.
dixi_minga commented on 2016-01-13 08:05 (UTC)
there is a new version (11.0.53191):
http://download.teamviewer.com/download/teamviewer_i386.deb
robertolos commented on 2016-01-04 14:09 (UTC)
Doesn't reduce anymore to the tray bar with plasma 5 :(
astronautlevel commented on 2015-12-20 19:33 (UTC)
@PiousMinion
This isn't really the place to ask this, but you can configure the teamviewer daemon via the command line only. Try running teamviewer --help.
PiousMinion commented on 2015-12-20 19:28 (UTC)
Teamviewer 11 now supports headless systems... but how in the world do you configure it or get the ID/password?
severach commented on 2015-12-18 17:35 (UTC)
No SysTray on XFCE or Cinnamon here. Fortunately the app now minimizes on exit which works well enough.
Strit commented on 2015-12-18 17:16 (UTC)
Any one else having trouble getting the systray icon on xfce? It just minimized to panel when I try to either minimize or close it.
mrlamud commented on 2015-12-12 01:05 (UTC)
@SonikkuAmerica
Use this modified PKGBUILD
----START COPYING FROM BELOW---------
pkgname=teamviewer
pkgver=11.0.52520
pkgrel=2
pkgdesc="All-In-One Software for Remote Support and Online Meetings"
arch=('i686' 'x86_64')
url="http://www.teamviewer.com"
license=('custom')
depends=('bash')
options=('!strip')
install=teamviewer.install
if [[ $CARCH == 'i686' ]]; then
source=("teamviewer_linux-${pkgver}.deb::http://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_i386.deb")
md5sums=('233d98a671d9ae6376c7265a3db2031f')
depends+=('alsa-lib' 'gcc-libs' 'libxdamage' 'libxtst' 'zlib' 'freetype2' 'libxrandr' 'libice' 'libsm')
elif [[ $CARCH == 'x86_64' ]]; then
source=("teamviewer_linux_x64-${pkgver}.deb::http://download.teamviewer.com/download/version_${pkgver%%.*}x/teamviewer_${pkgver}_amd64.deb")
depends+=('lib32-gcc-libs' 'lib32-alsa-lib' 'lib32-libxtst' 'lib32-libxdamage' 'lib32-zlib' 'lib32-freetype2' 'lib32-libxrandr' 'lib32-libice' 'lib32-libsm' 'lib32-libxinerama')
fi
build() {
cd "${srcdir}"
tar -xf data.tar.bz2
}
package() {
cd "${srcdir}"
# Install
cp -dr --no-preserve=ownership {etc,opt,usr,var} "${pkgdir}"/
# Additional files
rm "${pkgdir}"/opt/teamviewer/tv_bin/xdg-utils/xdg-email
install -D -m0644 "${pkgdir}"/opt/teamviewer/tv_bin/script/teamviewerd.service \
"${pkgdir}"/usr/lib/systemd/system/teamviewerd.service
install -d -m0755 "${pkgdir}"/usr/{share/applications,share/licenses/teamviewer}
ln -s /opt/teamviewer/tv_bin/desktop/teamviewer-teamviewer${pkgver%%.*}.desktop \
"${pkgdir}"/usr/share/applications/teamviewer.desktop
ln -s /opt/teamviewer/License.txt \
"${pkgdir}"/usr/share/licenses/teamviewer/LICENSE
}
md5sums=('233d98a671d9ae6376c7265a3db2031f')
butler360 commented on 2015-12-10 06:03 (UTC)
You can install multilib-devel to solve that, SonikkuAmerica.
See: https://wiki.archlinux.org/index.php/64-bit_FAQ#Multilib_repository
SonikkuAmerica commented on 2015-12-10 06:01 (UTC)
This build will not work on 64-bit systems because lib32-libpng12 depends on gcc-multilib, which would uninstall gcc!
astronautlevel commented on 2015-12-04 22:49 (UTC)
@Utini
The only AUR dependency is lib32-libpng12
@lockheed
lib32-libpng12 is already a dependency.
lockheed commented on 2015-12-04 17:30 (UTC)
Please, add necessary dependency on lib32-libpng12
Utini commented on 2015-12-04 09:42 (UTC)
Why so many dependencies from the AUR? Aren't there any equivalents from the official repos? :/ Thanks !
willruss1 commented on 2015-12-03 22:53 (UTC)
After removing v10 it works perfectly under awesome-wm on manjaro, thanks for the version bump @astronautlevel.
astronautlevel commented on 2015-12-03 18:20 (UTC)
@f3bruary
You have to uninstall old versions of teamviewer, the directory structure has changed from teamviewer 10 to 11.
f3bruary commented on 2015-12-03 18:18 (UTC)
error: failed to commit transaction (conflicting files)
teamviewer: /opt/teamviewer/config exists in filesystem
teamviewer: /opt/teamviewer/logfiles exists in filesystem
Errors occurred, no packages were upgraded.
==> WARNING: Your packages are saved in /tmp/yaourt-tmp-username
==> ERROR: unable to update
I could probably delete those files to complete the installation, but I assume config might have personalized settings.
markzz commented on 2015-12-03 17:47 (UTC) (edited on 2015-12-03 18:27 (UTC) by markzz)
PKGBUILDs here are intended for use with Arch Linux, not with derivative systems. If it doesn't build with makepkg on Arch Linux, it isn't the maintainer's problem. I can verify all is well on Arch Linux.
greh commented on 2015-12-03 11:44 (UTC)
@astronautlevel: I'm using Antergos with Cinnamon. Yes, unnatended access is set up.
astronautlevel commented on 2015-12-03 11:33 (UTC)
greh, what desktop environment and window manager are you using? Did you set up unattended access?
farnsworth commented on 2015-12-03 09:04 (UTC)
Connect button is back, thanks.
greh commented on 2015-12-03 06:11 (UTC) (edited on 2015-12-03 08:47 (UTC) by greh)
After updating there is no icon in the notification area. Daemon started, service is up, but something does not work correctly. The option of closing to notification area is enabled, but greyed out...
MUsk commented on 2015-12-03 05:27 (UTC) (edited on 2015-12-03 07:58 (UTC) by MUsk)
It's working now.
astronautlevel commented on 2015-12-03 01:27 (UTC)
It's working on my test box, though I updated the dependencies to be like the beta release and fixed the desktop link.
Can you try now?
farnsworth commented on 2015-12-02 23:38 (UTC) (edited on 2015-12-02 23:51 (UTC) by farnsworth)
Hi,
/usr/share/applications/teamviewer.desktop link is wrong, it is still linking /opt/teamviewer/tv_bin/desktop/teamviewer-teamviewer10.desktop
Also, I'm unable to use your version to connect to a client while it works fine with the beta release.
it's missing something, the window opens, I can enter the client ID but I'm unable to validate, the connect button is not displayed like many other graphics in the window.
I don't know if it's revelant but dependancies are also different between beta and this one whereas they have the same release number (11.0.52520).
mareex commented on 2015-12-02 23:11 (UTC)
There is something wrong.
Package Details: teamviewer 11.0.52520-1.2
But in PKGBUILD:
pkgrel=1.1
astronautlevel commented on 2015-12-02 22:23 (UTC)
Teamviewer 10 appears to have folders in different locations than teamviewer 11.
I'm going to recommend uninstalling older versions of teamviewer before upgrading.
maxyme commented on 2015-12-02 21:30 (UTC)
Upon upgrading:
error: failed to commit transaction (conflicting files)
teamviewer: /opt/teamviewer/config exists in filesystem
teamviewer: /opt/teamviewer/logfiles exists in filesystem
I think you accidentally included the logfiles and config folder.
astronautlevel commented on 2015-12-02 20:36 (UTC)
I already applied it, see my previous message.
invik commented on 2015-12-02 20:35 (UTC)
PKGBUILD has an issue. This easy patch fixes the problem:
--- fix/PKGBUILD 2015-12-02 21:31:27.402300843 +0100
+++ broken/PKGBUILD 2015-12-02 21:34:39.552310491 +0100
@@ -26,7 +26,7 @@
build() {
cd "${srcdir}"
- tar -xf data.tar.gz
+ tar -jxf data.tar.bz2
}
package() {
astronautlevel commented on 2015-12-02 20:33 (UTC)
It's fixed now, the new version of the package uses bz2 rather than gz, which I didn't realize after the first commit.
greh commented on 2015-12-02 20:28 (UTC)
Getting an error.
==> Budowanie i instalowanie pakietu
==> Tworzę pakiet: teamviewer 11.0.52520-1 (śro, 2 gru 2015, 21:27:48 CET)
==> Sprawdzanie zależności potrzebnych do uruchomienia...
==> Sprawdzanie zależności potrzebnych do budowy...
==> Pobieranie źródeł...
-> Znaleziono teamviewer_linux_x64-11.0.52520.deb
==> Sprawdzam pliki źródłowe przy użyciu md5sums...
teamviewer_linux_x64-11.0.52520.deb ... Zgadza się
==> Rozpakowywanie źródeł...
-> Rozpakowywanie teamviewer_linux_x64-11.0.52520.deb za pomocą bsdtar
==> Usuwanie istniejącego katalogu $pkgdir/...
==> Zaczynam build()...
tar: data.tar.gz: Nie można open: Nie ma takiego pliku ani katalogu
tar: Error is not recoverable: exiting now
==> BŁĄD: Wystąpił błąd w build().
Przerywam...
==> BŁĄD:Makepkg nie był w stanie zbudować teamviewer.
KingYes commented on 2015-12-02 20:07 (UTC)
Your welcome.
astronautlevel commented on 2015-12-02 20:05 (UTC)
I can maintain it if you're unable to.
KingYes commented on 2015-12-02 19:58 (UTC)
For now I can't update the package. anyone want to maintainers this?
astronautlevel commented on 2015-12-02 19:56 (UTC)
Now that 11 is out of beta, this package won't install properly.
scarecrow commented on 2015-12-02 18:27 (UTC)
11.0.52520 is now the official stable version.
ranger commented on 2015-11-27 18:55 (UTC)
The only urgent I see, it that Sukumi has to read the arch wiki urgently
"The large number of packages and build scripts in the various Arch Linux repositories support freedom of choice, offering free and open source software for those who prefer it as well as proprietary software packages for those who embrace functionality over ideology. "
https://wiki.archlinux.org/index.php/Arch_Linux#Pragmatism
PhotonX commented on 2015-11-27 17:53 (UTC)
Doesn't the same apply to many other packages like Skype?
Sukumi commented on 2015-11-27 17:30 (UTC)
########### !!!! URGENT ACTION REQUIRED !!!!!!!!! #####################
########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!! ###############
NO SOURCE, PROPRIETARY SOFTWARE LICENSE, BINARIES ONLY
The maintainer is responsible that the managed packaged adhere and comply with the community
and ArchLinux philosophy and rules of package submission.
I THINK THE COMPLIANCE AUDIT RULES NEED A REVIEW.
LICENSE EXCERPT GIVEN BELOW
########### !!!! REQUEST FOR DELETION SUBMITTED !!!!!!!!!!!!!! ###############
########### !!!! URGENT ACTION REQUIRED !!!!!!!!!!!!!! #######################
JDCNS commented on 2015-11-17 02:58 (UTC)
dixi_minga wrote: "I can't remember that teamviewer published a beta Version in the last years "
They did last year as well. I remember because that is the first time I purchased a business license from them, and I remember waiting to ensure I got one for the new version.
What's weird is that I modified the PKGINFO with the new version and MD5 checksum, it installed, it downloaded a package with "11" in the name, but everything still says "10". If you ask me, this is too crude to be called a beta.
Anyhow, I hope the speed is everything I've heard about. I still have to actually try it out.
dixi_minga commented on 2015-11-06 22:31 (UTC)
@mgd:
> why do people in need of support install a beta ?
they just check for udates inside the application an get the new version, thats all
I can't remember that teamviewer published a beta Version in the last years - I don't know, why they do this
eworm commented on 2015-11-06 10:38 (UTC)
Teamviewer started to advertise version 11 beta on their website. So if you tell a customer: "Please go to the website and download the quicksupport module!" chances are that they download version 11 beta.
Sadly version 10 can not connect to version 11 beta. That is where the hassle starts.
But please do not update, yet! That would break the setup for people who have a license for the recent stable version but did not upgrade to next version, yet.
mgd commented on 2015-11-05 13:30 (UTC)
Only to satisfy my curiosity:
why do people in need of support install a beta ?
Or phrased differently:
people in need of support should not install a beta.
Or have I misunderstood something ?
Kind regards,
Michael
dixi_minga commented on 2015-11-05 11:51 (UTC)
Some of my supported windows clients have now version 11 beta
for these I need the new version: http://download.teamviewer.com/download/version_11x/teamviewer_i386.deb
THANKS
Raansu commented on 2015-11-03 19:06 (UTC)
Is there a reason why there is no desktop audio streaming here? Supposedly it's possible for Linux clients/servers of teamviewer as mentioned at http://askubuntu.com/a/419662
JoeKnock90 commented on 2015-11-03 15:38 (UTC) (edited on 2015-11-03 16:10 (UTC) by JoeKnock90)
Looks like Teamviewer 11 Beta is out.
I managed to edit your PKGBUILD to get it installed, but I'm REALLY bad at this kind of thing. So while it is working, I am positive it is not the right way to do it.
In other news. Teamviewer 11 is still NOT native and doesn't work well with KDE. But it works, and I suppose it is a little faster than 10.
Some text isn't rendering properly either, going to try installing the MS fonts.
severach commented on 2015-10-19 05:32 (UTC)
downgrade only works for repos.
My TeamViewer PKGBUILD builds 8 9 or 10. Included is a patch that fixes missing .Xauthority file, required for version 10, and a patch that allows operation installed with or without the daemon, and some hassle to switch over. It can build 10.0.41499 which, unlike 10.0.46203, is mostly functional.
I set the version to 9 and added a teamviewer9 package.
nrq commented on 2015-10-19 03:29 (UTC)
@maclinuxfree you need to install `downgrade` to get the past versions of a package.
maclinuxfree commented on 2015-10-10 15:23 (UTC)
Hello guys,
could someone readd the TeamViewer 9 Version please?
thx
gobostone commented on 2015-09-17 18:01 (UTC)
@Xavion: thanks so much, that was driving me nuts.
Xavion commented on 2015-09-17 01:49 (UTC)
I couldn't see my Android's screen until I installed the "lib32-libjpeg6-turbo" and "lib32-libpng12" packages. To prevent other users from facing this problem, I think you should add those two packages as dependencies for this one.
severach commented on 2015-09-02 21:25 (UTC)
I just got the i686 version 15 minutes ago and it downloaded just fine. Erase the deb file and try again. TV doesn't work (not ready, please check your connection) but that might be because I'm running too old of a kernel.
macxcool commented on 2015-09-02 21:08 (UTC)
teamviewer_linux-10.0.46203.deb is 1667 bytes and fails the validity check on i686
FadeMind commented on 2015-08-21 04:04 (UTC)
Ravenman
Enable multilib repo in /etc/pacman.conf file.
Next run:
yaourt -Sy teamviewer --noconfirm
Ravenman commented on 2015-08-21 03:44 (UTC)
I can not install this package on my x86_64 system:
==> Continue building teamviewer ? [Y/n]
==> ------------------------------------
==>
==> Building and installing package
==> Install or build missing dependencies for teamviewer:
Password:
error: target not found: lib32-libxrandr
error: target not found: lib32-freetype2
error: target not found: lib32-alsa-lib
error: target not found: lib32-libxinerama
error: target not found: lib32-zlib
error: target not found: lib32-libxdamage
error: target not found: lib32-libsm
error: target not found: lib32-libice
error: target not found: lib32-gcc-libs
error: target not found: lib32-libxtst
==> Restart building teamviewer ? [y/N]
==> -----------------------------------
==>
Somebody can help me, please?
KingYes commented on 2015-08-19 13:32 (UTC)
v10.0.46203 Updated.
izmntuk commented on 2015-07-22 05:30 (UTC)
'teamviewer.install' should not be executable. Please remove the "x" mode bit in the next release.
I-sty commented on 2015-06-17 14:50 (UTC)
Exactly!
SupKurtJ you are right! That's worked for me too!
Thank you very much!
Joan31 commented on 2015-06-17 14:39 (UTC)
Hello,
I have a solution.
The problem is the service with systemctl teamviewerd.
Don't enable this.
You must start everytime per session the daemon with : teamviewer --daemon start
And launch Teamviewer, and all work fine.
If the systemctl teamviewerd is start, teamviewer doesn't work correctly.
So conclusion, the service has a problem.
unclesam commented on 2015-05-22 04:33 (UTC)
This was a misleading formulation, sorry.
Ubuntu and Debian are officially supported and the website provides two deb-packages.
RedHat, CentOS, Fedora and SUSE are also officially supported and the website provides an rpm-package.
The third package (Download.tar.gz) is for Linux-distributions, which are not offcially supported.
I think that the software is the same, but the packing is different and the software is tested on the officially supported distributions.
Sorry for the misleading information in my previous comment.
@ Louis: I think that the situation is the same for both versions
Louis commented on 2015-05-21 18:00 (UTC)
@unclesam
I think it best to build upon an officially supported package even if it's require a move extensive PKGBUILD. This is just my
opinion - I'm not the maintainer.
unclesam commented on 2015-05-21 13:15 (UTC)
I have reached the limit of my knowledge and this program is still driving me crazy.
There is an unsupported version (same version-numer) of teamviewer on the official website (Download.tar.gz). Thus, I have downloaded the archive, extracted the content into ~/.teamviewer and then copied the file teamviewer.desktop to /usr/share/applications (programstarter for gnome/cinnamon) and everything works perfectly with this copy!!!
This could be an alternative to the debian-package, but I don't want to maintain this PKGBUILD.
If there's anybody willing to adopt the package, I would write a PKGFILE.
All the best,
unclesam
I-sty commented on 2015-05-21 06:39 (UTC)
I also use the LightDM but I also have problem
unclesam commented on 2015-05-21 05:22 (UTC)
I switched to lightdm, but this was not the solution. (On my second machine it runs fine with gdm.)
However, thanks for the suggestion.
I've also removed teamviewer completely (including configuration) and reinstalled it afterwards. This did not solve the problem either...
milocario commented on 2015-05-20 21:27 (UTC)
The Teamviwer Team recommended me to use "sudo teamviewer --daemon restart".
It works with version 10.0.41499 and GDM, but I have to do it every time I restart my computer.
will.price94 commented on 2015-05-20 20:52 (UTC)
Are you using gdm? If so try with an alternate login manager like lightdm
unclesam commented on 2015-05-20 20:49 (UTC)
I have an issue with the login into my account. When I try to login, I get an timeout and the error-message, that the server did not reply. I've found the following lines in teamviewers logfile:
2015/05/20 22:30:21.737 33 39 G1 Account::TryAutoLogin: enabled: 0
2015/05/20 22:30:26.868 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.869 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.869 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.870 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.870 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.870 33 46 G1 Timeout for master message.
2015/05/20 22:30:26.870 33 46 G1 Timeout for master message.
2015/05/20 22:30:37.039 33 34 G1 Account::SetNewLoginState: 3
2015/05/20 22:30:37.073 33 34 G1 AccountLogin::Start: Trying account authentication
2015/05/20 22:30:57.051 33 34 G1!! BuddyList: SignIn failed. (SignIn Timeout), Errorcode=5
2015/05/20 22:30:57.059 33 34 G1!! BuddyPageList.OnDestroy: RemoveMessageFilter failed
2015/05/20 22:31:07.087 33 34 G1!! AccountLogin::Error: Authentication failed with error 2
2015/05/20 22:31:07.088 33 34 G1 Account::SetNewLoginState: 2
Nevertheless, the program works when I try to connect to a diffrent machine with its id and password.
Teamviewer used to work fine before, but I cannot say which system- or teamviewer-update caused the problems.
I have a second machine (same DE: cinnamon 2.4 and gnome 3.16) with nearly identical setup, just different hardware where teanviewer is still running fine.
Is there anybody who has a similar issue?
Thanks.
All the best,
unclesam
yochaigal commented on 2015-05-20 20:22 (UTC)
I am getting the "PID file /var/run/teamviewerd.pid not readable (yet?) after start." other folks have had in the past - unfortunately, none of the fixes in this thread have worked out. I tried changing the permissions on the folder where the PID lives, and pointing the unit file to another directory.
Any ideas?
I-sty commented on 2015-05-20 19:30 (UTC)
Hi,
I installed the latest version, I added the systemctl service but the app doesn't work for me.
[isti@istiLaptop ~]$ systemctl --all | grep teamv
teamviewerd.service loaded active running TeamViewer remote control daemon
[isti@istiLaptop ~]$ teamviewer -h
Init...
Checking setup...
Launching TeamViewer ...
[isti@istiLaptop ~]$
KingYes commented on 2015-04-22 11:47 (UTC)
Updated. Now all work perfect :)
Pietro_Pizzi commented on 2015-04-21 16:02 (UTC)
new md5sum teamviewer_linux_x64-10.0.37742.deb
fdbc27543e0955e217097810a7983507
Midov commented on 2015-04-20 15:05 (UTC)
Disabling wayland in GDM didnt work for me, but simply not using gdm did.
I started my awesomewm with startx and teamviewer suddenly works again.
Goddamn Gnome, not only breaks its own addons with every version but now it also breaks everything else..
commented on 2015-04-20 14:49 (UTC)
Not working with GDM unless wayland is disabled in /etc/gdm/custom.conf
drewofdoom commented on 2015-04-20 13:32 (UTC)
Report from TeamViewer support:
"We got some news from our developers that this is unfortunately a known problem. But please note that the problem is related to Gnome itself.
Our developers are already working on a solution and this will be fixed as soon as possible. We are really sorry about the inconvenience."
drewofdoom commented on 2015-04-14 14:02 (UTC)
I have filed a bug with TeamViewer support. I will let you all know if this case gets resolved.
KingYes commented on 2015-04-13 14:23 (UTC)
Anyone know what need to do? I have same problem with the new Gnome (3.16).
drewofdoom commented on 2015-04-13 14:21 (UTC)
FYI, running without the daemon (tar.gz version from TeamViewer website) is broken now as well. Seems to be an upstream issue.
max.bra commented on 2015-04-13 09:41 (UTC)
@Midov: there's nothing missing in teamviewerd:
ldd /opt/teamviewer/tv_bin/teamviewerd
linux-gate.so.1 (0xf770f000)
libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf76b6000)
librt.so.1 => /usr/lib32/librt.so.1 (0xf76ad000)
libXau.so.6 => /usr/lib32/libXau.so.6 (0xf76a9000)
libX11.so.6 => /usr/lib32/libX11.so.6 (0xf755a000)
libm.so.6 => /usr/lib32/libm.so.6 (0xf750c000)
libc.so.6 => /usr/lib32/libc.so.6 (0xf7352000)
/lib/ld-linux.so.2 (0xf7710000)
libxcb.so.1 => /usr/lib32/libxcb.so.1 (0xf732c000)
libdl.so.2 => /usr/lib32/libdl.so.2 (0xf7327000)
libXdmcp.so.6 => /usr/lib32/libXdmcp.so.6 (0xf7320000)
it's simply broken.
silly question: have you an nvidia video card?
Midov commented on 2015-04-13 09:37 (UTC)
Teamviewerd is not working properly for me either. Service does seem to start and it says its running but when i try to run teamviewer client its still complaining about teamviewerd being turned off.
I tried installing teamviewer manually from their website but instalation says im missing libjpeg.so.62. wchich is weird since i do have
extra/libjpeg-turbo 1.4.0-1 [installed]
multilib/lib32-libjpeg-turbo 1.4.0-1 [installed]
It started after updating gnome too.
max.bra commented on 2015-04-13 09:08 (UTC)
Gnome 3.16 huge update has broken teamviewerd on my system: despite is running is not found by the GUI and freeze shutdown procedure (above 90s timeout problem, system is not responsive at all and never halt) if not 'kill -9'ed in advance.
Any one else?
raqua commented on 2015-03-30 21:05 (UTC)
It did not work again. I have looked at the AUR search tool here and found out that the lib you are referencing should exist in Arch, so the problem was with my system, not your package. I apologize for the confusion and possibly waste of your time.
I had multilib repo not working on my system. It is fixed now, should work.
KingYes commented on 2015-03-30 06:24 (UTC)
@raqua please try now again
macxcool commented on 2015-03-27 00:22 (UTC)
I can't get this working on i686. First there is an md5sum error. When I fix that in the PKGBUILD I get an error about there being no .tar.gz file to unpack. Are you supporting 32-bit installations?
raqua commented on 2015-03-26 22:27 (UTC)
Ok, let me repeat that. Let's see:
raqua@phenom:~
$ yaourt -Ss libxinerama
extra/libxinerama 1.1.3-2 [installed]
X11 Xinerama extension library
aur/libx32-libxinerama 1.1.2-1.1 (1)
X11 Xinerama extension library (x32 ABI)
Dependency requested: lib32-libxinerama
Dependency in AUR : libx32-libxinerama
Do you see where the problem is now? :)
KingYes commented on 2015-03-25 07:05 (UTC)
@raqua, You need to install that from AUR.
raqua commented on 2015-03-24 18:37 (UTC)
Hi,
my build is now failing, because it can not find lib32-libxinerama.
There is only libx32-libxinerama package in AUR.
KingYes commented on 2015-03-22 07:32 (UTC)
Updated.
Manraj commented on 2015-03-20 14:38 (UTC)
Installed dependencies specified by @DaBunglow and incoming connections to archlinux machine started working.
@KingYes please add the following pacman targets to the package
lib32-libice lib32-libsm lib32-libxinerama
macxcool commented on 2015-03-03 17:49 (UTC)
i686 computer - MD5sum is incorrect (should be 313a81a8a7840ddfa814a6187e72a9ef )
When MD5 sum is corrected I get 'tar: data.tar.gz: Cannot open: No such file or directory'
There is no data.tar.gz file in the 'src' folder. I don't think the .deb is being extracted. Is there a makedepend missing?
Forvord commented on 2015-03-03 12:49 (UTC)
I have a problem using the TV and wine (now is 1.7.37). After installing wine TV does not start.
I solved it by installing PlayOnLinux and removing wine (pacman -Rdd wine). Now Now I use POL and its internal version of wine.
P.S. Arch Linux 32bit.
KingYes commented on 2015-02-23 14:27 (UTC)
I have all this dependencies, and incoming connects not work.
JojOatXGME commented on 2015-02-23 13:08 (UTC)
I think there are missing dependencies. I have installed the package and it was possible to start teamviewer. But when I tried to connect from somewhere else to the computer, it did not work. The client hang while connecting and my pc with the package from here was not doing anything.
The log says that someone was connecting but the process which was started to handle the connection exited with exit code 0.
The dependency checker of teamviewer detected missing dependencies:
lib32-libice
lib32-fontconfig
lib32-libsm
lib32-libxinerama
lib32-libpng12
After installing them, it was possible to connect from another computer while using the package from here.
thefirstofthe300 commented on 2015-02-12 21:28 (UTC)
According to the Teamviewer library checker, these are also dependencies of TeamViewer: lib32-libice lib32-libsm lib32-libxinerama
gerryst commented on 2015-02-09 08:15 (UTC)
@ yurikoles
Had the same problem on my Manjaro installation.
This fixed it for me:
https://bbs.archlinux.org/viewtopic.php?id=188990
The file you need to change should be:
/usr/lib/systemd/system/teamviewerd.service
daklaus commented on 2015-02-02 16:31 (UTC)
Hello, using pacaur I get the following when I wanted to update teamviewer from 10.0.36281-2 to 10.0.37742-1:
:: Starting AUR upgrade...
:: resolving dependencies...
:: no results found for lib32-alsa-lib
:: no results found for lib32-freetype2
:: no results found for lib32-gcc-libs
:: no results found for lib32-libxdamage
:: no results found for lib32-libxrandr
:: no results found for lib32-libxtst
:: no results found for lib32-zlib
I am on a 32 bit machine and therefore the library names on those systems are without the prefix lib32- since this is only for the multilib libraries. Please correct the dependencies here to be valid for both x86_64 (with multilib) and x86.
eennbb commented on 2015-01-31 03:43 (UTC)
Hi, i get this updating via yaourt
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 180 100 180 0 0 341 0 --:--:-- --:--:-- --:--:-- 340
100 169 100 169 0 0 151 0 0:00:01 0:00:01 --:--:-- 151
11 38.7M 11 4435k 0 0 538k 0 0:01:13 0:00:08 0:01:05 599kcurl: (56) Recv failure: Connection reset by peer
==> ERROR: Failure while downloading teamviewer_linux_x64-10.0.37742.deb
Aborting...
yurikoles commented on 2015-01-22 21:25 (UTC)
My system has problem stoping teamviewerd. It waits for 90s every shutdown.
How to fix it?
levitsky commented on 2015-01-22 10:15 (UTC)
@pngochai Yep, happens to me, too.
pngochai commented on 2015-01-21 16:02 (UTC)
I'm using systemd by the way
pngochai commented on 2015-01-21 16:02 (UTC)
Anyone has the problem that if you enable teamviewer daemon, system shutdown will take 1m30s more waiting for the daemon to stop?
JDCNS commented on 2015-01-19 21:59 (UTC)
I had some difficulty with initiating chat without first initiating a remote connection. TeamViewer looked over my issue and stated there was a missing library, so I downloaded their program and ran tvsetup, and libjpeg.so.62 was missing.
BTW, there are two versions, one is out of date. The latest one is https://aur.archlinux.org/packages/libjpeg6-turbo/.
jwallden commented on 2015-01-19 20:20 (UTC)
I get
Validating source files with md5sums...
teamviewer_linux_x64-10.0.36281.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
:: failed to verify teamviewer integrity
when trying to install this with Pacaur
thearcherblog commented on 2015-01-09 12:55 (UTC)
@PhotonX
I found the same issue here.
My keyboard is locally setup as norwegian and I'm connecting from a Windows computer using keyboard layout and same teamviewer version, 10.
I didn't notice it before upgrading to Teamviewer 10.
PhotonX commented on 2014-12-30 12:28 (UTC)
I experience follwing bug: After the update to 10.0 the keyboard layout is recognized in a wrong way. Following setup: machine 1 (my machine, running Arch Linux) and machine 2 (another machine running Manjaro) both have the German keyboard layout. Neither of the machines has a problem with wrong keyboard layout. However, if I connect to machine 2 through teamviewer and type, on machine 2 my input is translated into standard QUERTY layout, i.e. I get [ for ü, / for - and so on. Downgrading to teamviewer9 on both machines solves the problem. Anybody else who can reproduce this?
lockheed commented on 2014-12-25 22:04 (UTC)
I mean any Teamviewer window at all. I know the "Computer & Contacts" can be disabled, but still there's another TV window that opens.
lockheed commented on 2014-12-25 22:02 (UTC)
Is there some way to disable automatic start of the " Computers & Contacts" window when teamviewerd service starts?
Kspap commented on 2014-12-21 08:03 (UTC)
@rkelly @t.iglo
Synchronizing participants stuck?
I fixed mine by disabling 'Play computer sound and music' in teamviewer options.
swiftgeek commented on 2014-12-08 14:28 (UTC)
Can anyone check if chat/quicksupport for phones is working?
For both i don't get windows at all, while rest of logic seems to be working (eg. phone displays that connection exist and after disconnection i get in TV ~statusbar information about session duration)
It's strange as it worked fine on beta… (i tested already with clean $HOME)
waitnsea commented on 2014-12-03 08:54 (UTC)
Needs to install a link in /opt :
ln -s /opt/teamviewer /opt/teamviewer9
KingYes commented on 2014-12-02 13:39 (UTC)
Guys, Thanks !
Updated..
rafaelndev commented on 2014-12-02 13:21 (UTC)
There is a problem with the desktop link.
The PKGBUILD links the file 'teamviewer-teamviewer.desktop' but in version 10 the desktop file is named 'teamviewer-teamviewer10.desktop'.
183.amir commented on 2014-12-02 13:19 (UTC)
Hi there is a problem with this package:
ln -s /opt/teamviewer/tv_bin/desktop/teamviewer-teamviewer.desktop "${pkgdir}"/usr/share/applications/teamviewer.desktop
should be:
ln -s /opt/teamviewer/tv_bin/desktop/teamviewer-teamviewer10.desktop "${pkgdir}"/usr/share/applications/teamviewer.desktop
change: "teamviewer-teamviewer.desktop" to "teamviewer-teamviewer10.desktop"
KingYes commented on 2014-12-02 12:35 (UTC)
I just update to 10.0.36281 version.
Have fun
jdawg commented on 2014-11-29 22:21 (UTC)
I wasn't able to get TeamViewer to work on my computer without installing lib32-libnss_sss. I use sssd for user authentication. It would just silently fail until I used strace to figure out what was going on.
florck commented on 2014-11-27 21:34 (UTC)
I have the same problem as @a5702532.
I had it on my other computer, it was fixed.
Now I have it on my server, but what is installed is same version as on my other computer where it works successfully.
What am I forgetting?
Tallix commented on 2014-11-27 05:20 (UTC)
This application appears to run through Wine. Could the maintainer please add wine to the dependency list (along with lib32-libxrandr as others have mentioned)?
richcocoa commented on 2014-11-19 09:41 (UTC)
Sorry for flagging it as out date. Teamviewer 10 for linux is still in beta. Didn't notice it right out. Sorry again.
rkelly commented on 2014-10-30 20:53 (UTC)
I'm experiencing the same thing as t.iglo. Stuck on "Synchronizing participants."
t.iglo commented on 2014-10-20 18:21 (UTC)
Hi I need help guys, my outgoing connection doesn't work. When I fill ID and then password (in password dialog) this windows appears:
http://postimg.org/image/rqhgiz633/
and nothing happens :(
Can anyone help please?
PS: I tried connection to Windows or Debian with no reaction.
jradxl commented on 2014-10-15 15:48 (UTC)
Thanks, -2 fixed issue for me.
I can log in Manjaro to Manjaro, except I do not have a choice of resolutions - just 1024x768
KingYes commented on 2014-10-13 17:45 (UTC)
I just upgrade my package. Please let's me know if it's okay for you.
dhiru1602 commented on 2014-10-13 08:33 (UTC)
@KingYes,
I had issues with incoming connections not working. I can connect to another partner but others can't connect to me. It's similar to what @xlightwaverx, @MorningWood and @mgruben have reported. It turned out that I needed lib32-libxrandr and after installing, Teamviewer worked fine. However, this dependency was not installed directly when installing teamviewer from your AUR package.
Just for reference, lib32-libxrandr is needed and teamviewer-quicksupport package also uses it.
https://aur.archlinux.org/packages/te/teamviewer-quicksupport/PKGBUILD
KingYes commented on 2014-10-13 06:54 (UTC)
@dhiru1602: Are you sure what you talk about?
dhiru1602 commented on 2014-10-13 02:18 (UTC)
For those of you who are having problems with Incoming Connections failing, but Outgoing connections working fine, make sure you have installed lib32-libxrandr.
Requesting the Maintainer to please add the dependency.
KingYes commented on 2014-10-11 18:04 (UTC)
9.0.32150 is the last version for Linux.
jradxl commented on 2014-10-10 19:31 (UTC)
This Arch version is 32150, whereas my Windows 8.1 version is 32494 (12th Sept).
Could that be the reason that the Windows PC(local) won't start a remote session on the Manjaro KDE system (server).
Two Windows PCs connector, and another Manjaro system (also 32150) as client can connect to both Windows PCs.
KingYes commented on 2014-09-13 18:34 (UTC)
To start the deamon please use `systemctl` like this:
sudo systemctl start teamviewerd
(When you install the package, you can see this info)
someoneelse123 commented on 2014-09-13 17:56 (UTC)
Seems broken:
sudo teamviewer --daemon start
/etc/init.d/teamviewerd start
/opt/teamviewer9/tv_bin/script/tvw_daemon: line 204: /etc/init.d/teamviewerd: No such file or directory
fail
xlightwaverx commented on 2014-09-10 01:25 (UTC)
@russo79
Thanks, apparently you have to uncomment the [multilib] part too, which I didn't do. Thanks again!
Unfortunately, even though it installs, it still doesn't allow connections. All circumstances lead to "Login Cancelled" when trying to remotely connect via other devices with TV installed. This is both with and without daemon set up.
russo79 commented on 2014-09-10 00:12 (UTC)
@xlightwaverx
You need to enable the multilib repos [1]
[1] https://wiki.archlinux.org/index.php/Multilib
xlightwaverx commented on 2014-09-09 21:35 (UTC)
Calls for the following dependencies:
error: target not found: lib32-gcc-libs
error: target not found: lib32-alsa-lib
error: target not found: lib32-libxtst
error: target not found: lib32-libxdamage
error: target not found: lib32-zlib
error: target not found: lib32-freetype2
==> ERROR: 'pacman' failed to install missing dependencies.
When running the following (sudo pacman -S gcc-libs alsa-lib libxtst libxdamage zlib freetype2) I get:
warning: gcc-libs-4.9.1-1 is up to date -- reinstalling
warning: alsa-lib-1.0.28-1 is up to date -- reinstalling
warning: libxtst-1.2.2-1 is up to date -- reinstalling
warning: libxdamage-1.1.4-2 is up to date -- reinstalling
warning: zlib-1.2.8-3 is up to date -- reinstalling
warning: freetype2-2.5.3-2 is up to date -- reinstalling
Teamviewer is not detecting the current dependencies are already installed. Please advise.
drewofdoom commented on 2014-09-08 23:11 (UTC)
trialuser,
It has not been saving settings for me for a few point releases. Highly annoying. Tried using the standalone installation in my home directory as well as this package.
If anyone has a way to get it to start saving settings again, I would be eternally grateful!
a5702532 commented on 2014-09-07 10:51 (UTC)
"not ready - please check your internet connection"
how i can solve it?
trialuser commented on 2014-09-05 04:34 (UTC)
is teamviewer not saving settings for anyone else or is it just me?
Svenstaro commented on 2014-08-25 10:24 (UTC)
You should add options = ('!strip').
acidflash commented on 2014-08-19 08:05 (UTC)
==> Retrieving sources...
-> Downloading teamviewer_linux_x64-9.0.30203.deb...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
==> ERROR: Failure while downloading teamviewer_linux_x64-9.0.30203.deb
Aborting...
==> ERROR: Makepkg was unable to build teamviewer.
==> Restart building teamviewer ? [y/N]
==> -----------------------------------
==>
==> ERROR: unable to update
stmc commented on 2014-08-18 17:21 (UTC)
tar.gz version works fine without daemon in any user's directory, from system directory it works only when permissions for directory & all files are 0777. I think in normal installation there are no ways to run it without daemon
alejandro.perez commented on 2014-08-18 15:04 (UTC)
I don't know in other systems, but the tar.gz version executes in my system without executing the daemon. I suggested to make a PKGBUILD using that version, but I did not tried that version. It is possible to be related with lack of permission for the user on the installation path?
I tried the tar.gz version on /tmp, where any user can write.
stmc commented on 2014-08-18 14:44 (UTC)
I am sorry for the inconvenience. A few posts ago, alejandro.perez said that the tar.gz version from teamviewer's website works without daemon, which makes it more safe. So, I tried to build a package from tar.gz, and it works on my PC, but fails to start on other. I will try fix it later. The old version of PKGBUILD (that builds package from .deb) was returned.
wenLiangcan commented on 2014-08-18 14:22 (UTC)
Failed to start, and I found the errors in /var/log/teamviewer/startup.log:
mkdir: cannot create directory ‘/opt/teamviewer9/profile’: Permission denied
Error: Could not create /opt/teamviewer9/profile/dosdevices
smirky commented on 2014-08-18 13:35 (UTC)
[0:smirky@lilly ~/Downloads/teamviewer]: teamviewer
error calling "tv_bin/script/teamviewer"
[254:smirky@lilly ~/Downloads/teamviewer]:
With: teamviewer 9.0.30203-3
smirky commented on 2014-08-18 13:25 (UTC)
The conflict was easily resolved with:
pacman -Rsn teamviewer
and then:
pacman -U new_teamviewer_pakage
macxcool commented on 2014-08-18 13:23 (UTC)
file conflict with /opt/teamviewer9/config and logfiles
smirky commented on 2014-08-18 12:58 (UTC)
[0:smirky@lilly ~]: teamviewer
Init...
Checking setup...
[1:smirky@lilly ~]:
As you see, exit code: 1
Teamviewer doesn't start for me. I noticed the info about teamviewer working without the teamviewerd daemon. Could that be the problem?
drewofdoom commented on 2014-08-18 12:57 (UTC)
Update seems to have broken TeamViewer for me. Running in terminal prints the following:
Init...
Checking Setup...
Immediately crashes afterwards.
alejandro.perez commented on 2014-08-16 09:43 (UTC)
I support amish's proposal. Why don't we use the tar.gz version which does not require to become root? I don't know if it is safer, but for me it is much convenient.
stmc commented on 2014-08-14 17:59 (UTC)
updated
killedbymonkeys commented on 2014-08-12 20:52 (UTC)
The new MD5 is decce9d21dbf99d508bb40c9a706e837
FadeMind commented on 2014-08-09 11:12 (UTC)
TeamViewer 9.0 Build 30203 available.
MichaelTunnell commented on 2014-08-07 20:08 (UTC)
asuglia's PKGBUILD changes worked for me as well. Thank you asuglia.
For those interested in the difference, asuglia updated the pkgver (package version) and the MD5SUMS of the downloads. The rest of the PKGBUILD is the same so this package is using the same sources from teamviewer.com.
Note- A message at the end of the build will be "The Teamviewer daemon must be running for Teamviewer 8 to work." which is true but the package is in fact Teamviewer 9 not 8. Here is a new teamviewer.install file for this update - http://codepad.org/nJhA59W0
j3zz4h commented on 2014-08-07 12:31 (UTC)
I can confirm that asuglia's new PKGBUILD is working with the new version on a x86_64 system.
(Linux 3.15.8-1-ARCH #1 SMP PREEMPT x86_64 GNU/Linux)
asuglia commented on 2014-08-03 16:49 (UTC)
A new teamviewer's version is available on the official website. For this reason, the md5 checksum validity check fails while installing the package with yaourt.
This should be the correct PKGBUILD: http://codepad.org/XB9P4NuK
I hope that it will be help you in updating the package.
Thank you for effort in mantaining it.
dixi_minga commented on 2014-07-26 01:54 (UTC)
finally after month: For Haswell CPUs a modified lib32-glibc is no longer needed with version 9.0.30203
scjet commented on 2014-07-25 14:53 (UTC)
yep, it's still "Out of Date":
teamviewer_linux_x64-9.0.27891.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build teamviewer.
-------
@Matthew_Moore,
Thx again, for the quick fix.
--------
Also, on a minor note, it still says: "...The Teamviewer daemon must be running for Teamviewer 8 to work...." ? should say "9", but just an fyi. :)
kunaguvarun commented on 2014-07-21 16:58 (UTC)
@Matthew_Moore,
Thank you for posting this fix...
spsf64 commented on 2014-07-17 22:09 (UTC)
Flagged as out of date, new ver 9.0.30203
developej commented on 2014-07-16 05:03 (UTC)
@Matthew_Moore
https://wiki.archlinux.org/index.php/makepkg#Generate_new_checksums
Matthew_Moore commented on 2014-07-16 05:00 (UTC)
The source package has been updated and the checksums no longer work. PLEASE UPDATE!!
In the meantime For those that need to install this package simply edit the pkgbuild and replace the checksums with 'SKIP' this will act as a workaround until the package is updated.
travnick commented on 2014-07-13 18:43 (UTC)
With current package I'm getting segmentation fault (no more info ...).
But http://download.teamviewer.com/download/teamviewer_linux.tar.gz works flawlessly.
reed1 commented on 2014-06-28 05:49 (UTC)
For those who can't get the sound and mic working for conference, replacing the old binaries should fix it: http://askubuntu.com/questions/419605/teamviewer-9-ubuntu-13-10-sound
trialuser commented on 2014-06-24 23:12 (UTC)
For anyone else who can't connect to your computer, I fixed it by uninstalling teamviewer (with -Rns flags), then installing wine + all optional dependency's, then re-installing teamviewer.
Manouchehri commented on 2014-05-21 22:47 (UTC)
Fails to download with aria2c, please update the PKGBUILD to this:
https://drive.google.com/file/d/0B7Jh7kkafSr7Vi03UWJZbnFNYkU/edit?usp=sharing
dixi_minga commented on 2014-05-20 20:21 (UTC)
lib32-glibc-2.19-5-x86_64.pkg.tar.xz without enabled lock elision for 64 Bit Systems with Haswell CPU Error (teamviewer GUI doesn't start):
https://dl.dropboxusercontent.com/u/90154171/lib32-glibc-2.19-5-x86_64.pkg.tar.xz
Install: pacman -U lib32-glibc-2.19-5-x86_64.pkg.tar.xz
Restore original: pacman -S lib32-glibc
PhotonX commented on 2014-05-18 14:24 (UTC)
The teamviwerd.service fails to start automatically:
$ systemctl status teamviewerd
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled)
Active: inactive (dead)
Manually it can be started without any problems, but it's a pity to run the start command every time. I observe this behavior on one Arch and two Manjaro installs.
keibak commented on 2014-05-10 08:47 (UTC)
@dot Thanks. What a stupid mistake from me :(
dot commented on 2014-05-10 07:12 (UTC)
@keibak when using 32bit applications on a 64bit platform you have to enable multilib: https://wiki.archlinux.org/index.php/multilib
keibak commented on 2014-05-10 06:57 (UTC)
Can't resolve dependencies:
==> Making package: teamviewer 9.0.27891-1 (Sat May 10 08:55:58 CEST 2014)
==> Checking runtime dependencies...
==> Installing missing dependencies...
error: target not found: lib32-gcc-libs
error: target not found: lib32-alsa-lib
error: target not found: lib32-libxtst
error: target not found: lib32-libxdamage
error: target not found: lib32-zlib
error: target not found: lib32-freetype2
==> ERROR: 'pacman' failed to install missing dependencies.
dixi_minga commented on 2014-05-05 17:56 (UTC)
20140502: New lib32-glibc-package -> same old error with Haswell-CPUs
I don't know whom to blame: teamviewer or glibc :-(
lib32-glibc for 64 Bit systems:
lib32-glibc-2.19-4-x86_64.pkg.tar.xz without enabled lock elision:
https://dl.dropboxusercontent.com/u/90154171/lib32-glibc-2.19-4-x86_64.pkg.tar.xz
Install: pacman -U lib32-glibc-2.19-4-x86_64.pkg.tar.xz
Restore original: pacman -S lib32-glibc
Comment by Holoduke 2014-03-18 00:46:
If you have a Haswell CPU and TeamViewer won't start, try building lib32-glibc
(or glibc on 32-bit) without --enable-lock-elision. That fixed it for me. I
found teamviewerd to crash in __lll_unlock_elision (), very similar to that
issue: https://bugs.archlinux.org/task/37617?project=5.
Hilinus commented on 2014-05-01 13:24 (UTC)
let me know if there are any problems.
e-v commented on 2014-05-01 10:17 (UTC)
35ba2b46fe7d2669bfc8e67e8243694d teamviewer_linux_x64.deb
pomukal commented on 2014-04-27 13:41 (UTC)
Please update.
smirky commented on 2014-04-27 08:38 (UTC)
There's a newer version. Please update.
dixi_minga commented on 2014-04-27 07:59 (UTC)
@Pyrdracon: It doesn't work for Haswell Bug
dixi_minga commented on 2014-04-27 00:50 (UTC)
teamviewer 9.0.27891 has the same well known for month Haswell-CPU-bug as 9.0.24147; thus you don't need to update or to hope, it's solved in the new version
teamviewer shows the disadvantages of closed commercial software very clearly
strapjaw commented on 2014-04-26 20:25 (UTC)
ehs0329 stated the work-around for this out of date package. KinG-InFet posted about an md5 error. The work-around is the solution for that md5 error. Here is a more detailed example of the posted work-around on a 64bit system.
The PKGBUILD script downloads a .deb with version and md5 of:
35ba2b46fe7d2669bfc8e67e8243694d teamviewer_linux_x64-9.0.24147.deb
The download from http://www.teamviewer.com/en/download/linux.aspx states that it is version v9.0.27891. The md5 of that file is:
35ba2b46fe7d2669bfc8e67e8243694d teamviewer_linux_x64.deb
The md5 for which the PKGBUILD is looking is:
md5sums=('ab46126b05e523479b53d576254f5a43')
I just changed that to 35ba2b46fe7d2669bfc8e67e8243694d and it compiled and installed without issue.
Again, this was for a 64bit system. If you're on a 32, you'll have to run md5sum against to downloaded .deb and update the PKGBUILD
KinG-InFeT commented on 2014-04-25 19:53 (UTC)
error md5sum
root@luongovincenzo ~ $ packer -S teamviewer
Aur Targets (1): teamviewer
Proceed with installation? [Y/n] y
Edit teamviewer PKGBUILD with $EDITOR? [Y/n] n
Edit teamviewer.install with $EDITOR? [Y/n] n
==> Creazione del pacchetto: teamviewer 9.0.24147-1 (ven 25 apr 2014, 21.50.50, CEST)
==> Controllo delle dipendenze durante l'avvio in corso...
==> Controllo delle dipendenze durante la compilazione in corso...
==> Download dei sorgenti in corso...
-> Download di teamviewer_linux-9.0.24147.deb in corso...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 181 100 181 0 0 79 0 0:00:02 0:00:02 --:--:-- 918
100 21.0M 100 21.0M 0 0 1292k 0 0:00:16 0:00:16 --:--:-- 1844k
==> Validazione dei sorgenti con md5sums in corso...
teamviewer_linux-9.0.24147.deb ... NON RIUSCITO
==> ERRORE: Uno o più file non hanno superato il controllo di validità!
The build failed.
ehs0329 commented on 2014-04-25 02:10 (UTC)
Workaround for this package being out-of-date:
Go to http://www.teamviewer.com/en/download/linux.aspx and make note of the version number. Download the version you want. Run "md5sum teamviewer_linux.deb > teamviewer_linux.deb.md5" or "md5sum teamviewer_linux.deb > teamviewer_linux_x64.deb.md5" depending on which version you downloaded. Edit the PKGBUILD to reflect the new version number and replace the md5sum with the output from the md5sum command. Quick and dirty but it works in a pinch.
Pyrdracon commented on 2014-04-23 20:10 (UTC)
If TeamViewer doesn't show up, you could try this patch: http://chakraos.org/ccr/diff_view.php?p=teamviewer&d=fix-winelib.patch
I had problems starting TeamViewer because it tried to use libwine.so.1 from the installed wine package (it searched for the lib and told me that there is a version mismatch). The old tvw_config had the lines from the patch included. I've tried this on two computers now and the connection window showed up again.
MorningWood commented on 2014-04-22 21:22 (UTC)
because as the out of date flag notes, the package is out of date and the m5sum for the newer teamviewer package is different.
uboot commented on 2014-04-22 20:38 (UTC)
==> Validating source files with md5sums...
teamviewer_linux_x64-9.0.24147.deb ... FAILED
FadeMind commented on 2014-04-22 07:29 (UTC)
Updated PKGBUILD file for 9.0.27891
https://pastebin.com/raw.php?i=4y4tx3ay
ThecaTTony commented on 2014-04-21 21:42 (UTC)
Hi, any plans to update this? If not, orphan the package, someone will eventually adopt and update. Thanks.
Kudlaty commented on 2014-04-16 11:15 (UTC)
Can U update pkgbuild to:
http://pastebin.com/ME3mnFF7
atertillic commented on 2014-04-15 13:14 (UTC)
No problems with v9.0.27891 x64 on Haswell i7.
@num1champ
If you use KDE you can execute scripts one the login screen (before logging in). Have a look at system settings -> autostart.
developej commented on 2014-04-12 15:52 (UTC)
Well, if you put lockscreen as the first thing to be executed after autologin (it seems to me you didn't read all I wrote or you didn't underatand it), you should be ok
num1champ commented on 2014-04-12 15:49 (UTC)
I noticed that this uses the .deb pkg for install. Is there a reason that the tar.gz pkg is not used?
num1champ commented on 2014-04-12 15:45 (UTC)
@developej
That looks like it might be a good work around, but I am concerned about who could get on my pc during that time with the autologin. (my kids would figure it out :-)
developej commented on 2014-04-12 14:59 (UTC)
@num1champ
I searched for a solution for some time, didn't find it.
A way around it is to set up an autologin on your machine, followed by an immediate screenlock:
1. https://wiki.archlinux.org/index.php/automatic_login_to_virtual_console
2. I am using i3wm, so I have a 'autostart' script which looks something like this:
'i3lock' as first line
sleep 5 seconds (so my DHCP kicks in and everything settles down)
run teamviewer and bunch of apps
That way when you reboot your computer remotely (via teamviewer or ssh), you will log in after reboot as if you were right in front of your computer, but screen will be locked and still ask for a password.
Teamviewer is waiting for connections now!
wget commented on 2014-04-08 10:20 (UTC)
@poincare. At this time of writing, this is still the latest available version. This package shouldn't be marked as out-of-date thus.
poincare commented on 2014-03-29 20:30 (UTC)
Why is this marked out of date?! Isn't this the current version?
developej commented on 2014-03-29 16:00 (UTC)
I have Haswell, but haven't had this problem...
My problem is that even though deamon is running my computer is not online. I have to log in and manually start the Teamviewer application, only then I can connect.
dixi_minga commented on 2014-03-29 14:53 (UTC)
@Holoduke: Thx - works also for me
maclinuxfree commented on 2014-03-23 19:34 (UTC)
I confirm the "Haswell-Bug" also. And the fix without "--enable-lock-elision" solved it for me, too. But I found another tool which is not working on my haswell i7 cpu "qfinder".
Medved commented on 2014-03-21 11:41 (UTC)
@Holoduke, I confirm that this works. Since I've changed the PC at work (with a new Haswell CPU) my teamviewer stoped working and kept on "core dumping".
Rebuilding and installing lib32-glib without "--enable-lock-elision" solved the issue.
Thanks!
Holoduke commented on 2014-03-18 00:46 (UTC)
If you have a Haswell CPU and TeamViewer won't start, try building lib32-glibc (or glibc on 32-bit) without --enable-lock-elision. That fixed it for me. I found teamviewerd to crash in __lll_unlock_elision (), very similar to that issue: https://bugs.archlinux.org/task/37617?project=5.
giner commented on 2014-03-13 08:47 (UTC)
If you want to run teamviewer without root then you can go the following way:
1. Install all necessary dependencies (check PKGBUILD)
2. Use the script bellow to download and run teamviewer in a home directory:
http://pastebin.com/xJNA4x1P
#!/bin/bash -e
if [[ ! -d $HOME/.teamviewer/teamviewer9 ]]; then
wget http://download.teamviewer.com/download/teamviewer_linux.tar.gz -O /tmp/teamviewer_linux.tar.gz
mkdir -p $HOME/.teamviewer
tar -xf /tmp/teamviewer_linux.tar.gz -C $HOME/.teamviewer
fi
$HOME/.teamviewer/teamviewer9/teamviewer
jeeves commented on 2014-03-13 06:06 (UTC)
I have not been able to successfully launch Teamviewer 9 either. The problem seems to be some problem that is keeping the teamviewerd.service from launching. Here is the terminal output when I check the service status after attempting to start the teamviewerd.service:
BTW - I tested "maxuwux" fix that involved modifying the service file, but unfortunately it made no difference for me (and yes I ran "systemctl daemon-reload" after editing the service file).
---------------------------------
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; disabled)
Active: activating (start) since Wed 2014-03-12 22:55:05 PDT; 35s ago
Process: 740 ExecStart=/opt/teamviewer9/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
CGroup: /system.slice/teamviewerd.service
`-743 /opt/teamviewer9/tv_bin/teamviewerd -d
Mar 12 22:55:05 dellpc systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Aerion commented on 2014-03-01 21:57 (UTC)
Why is this package flagged out of date when the latest version upstream is the very one on offer here?
maxwux commented on 2014-02-22 03:24 (UTC)
I fixed this problem.
edit /usr/lib/systemd/system/teamviewerd.service
change
ExecStart = /opt/teamviewer9/tv_bin/teamviewerd -d
to
ExecStart = /opt/teamviewer9/tv_bin/teamviewerd
PieterDeBruijn commented on 2014-02-18 09:48 (UTC)
Mine does not work either.
One small typo (maybe it's in the application itself):
"The Teamviewer daemon must be running for Teamviewer 8 to work." --> we are at version 9 now.
developej commented on 2014-02-15 12:46 (UTC)
Mine says 'Ready to connect', so it's not the package. I don't know what could be the problem for you, though.
AleXoundOS commented on 2014-02-15 11:36 (UTC)
The package has 823 votes and not working. Does anybody know a fix for "Not ready. Please check your connection" issue?
maxwux commented on 2014-02-12 02:37 (UTC)
$ sudo systemctl start teamviewerd
Job for teamviewerd.service failed. See 'systemctl status teamviewerd.service' and 'journalctl -xn' for details.
$ sudo systemctl status teamviewerd.service
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled)
Active: failed (Result: timeout) since Wed 2014-02-12 10:34:43 CST; 1min 50s ago
Process: 4403 ExecStart=/opt/teamviewer9/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Feb 12 10:31:43 max-t430s systemd[1]: Starting TeamViewer remote control daemon...
Feb 12 10:31:43 max-t430s systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Feb 12 10:33:13 max-t430s systemd[1]: teamviewerd.service operation timed out. Terminating.
Feb 12 10:34:43 max-t430s systemd[1]: teamviewerd.service stopping timed out (2). Killing.
Feb 12 10:34:43 max-t430s systemd[1]: Failed to start TeamViewer remote control daemon.
Feb 12 10:34:43 max-t430s systemd[1]: Unit teamviewerd.service entered failed state.
$ pacman -Q systemd
systemd 208-11
AleXoundOS commented on 2014-02-11 12:48 (UTC)
Same problem: "Not ready. Please check your connection"
MorningWood commented on 2014-02-08 19:26 (UTC)
I'm also having the same problem as mgruben. This package is not recognizing any incoming connections for me.
giner commented on 2014-01-23 13:16 (UTC)
> I found the working script for teamviewer8
I assume it's written by me a while ago.
> Hey did anyone figure out how to start teamviewer9 without root?
No luck so far, they changed something.
confusedfla commented on 2014-01-23 13:13 (UTC)
Hey did anyone figure out how to start teamviewer9 without root?
I found the working script for teamviewer8, but the daemon
/opt/teamviewer9/tv_bin/teamviewerd
does not start anymore (with root it works fine).
Would be glad to hear ideas :-)
mgruben commented on 2014-01-13 16:13 (UTC)
I'm having difficulty with this package. It installs fine (both through pacman and yaourt), but even after setting up for unattended access, it won't recognize incoming connections (no indication of incoming connections on the main Teamviewer window, even though iftop reveals that data is being sent to and from the Arch computer).
I use teamviewer on several Windows and other Linux boxes, but none are Arch.
Teamviewer8 on the same Arch box works great though (installs fine both through pacman and yaourt, and accepts incoming connections and allows for remote administration).
Am I missing something?
arriagga commented on 2013-12-25 01:54 (UTC)
scarecrow commented on 2013-12-24 20:00 (UTC)
The connection issues with build 24147 also exist in the windoze version. They were resolved in build 24951, which isn't available yet for linux.
roepi commented on 2013-12-17 10:45 (UTC)
That's what I meant with "dig in aur-mirror.git or in the Unofficial User Repositories." I guess my post wasn't clear enough. Sorry.
swiftgeek commented on 2013-12-16 20:49 (UTC)
Well actually person maintaining older version of package should be the one which is actually deploying them…
Gist is not needed as you can just use this URL (Warning - contains async JS)
http://pkgbuild.com/git/aur-mirror.git/log/teamviewer/PKGBUILD
roepi commented on 2013-12-16 20:41 (UTC)
That's what I meant with my first sentence. "Gist" was just proposed as a fallback, if maintaining multiple packages is to much hassle.
swiftgeek commented on 2013-12-16 13:03 (UTC)
It would make more sense to create new package eg teamviewer8
roepi commented on 2013-12-16 11:41 (UTC)
As upgrading to a new TeamViewer major version (e.g. 8 -> 9) does involve buying a new license, wouldn't it make sense to keep PKGBUILDs of the previous version(s) around within AUR packages TeamViewer8, 7...? Those should be mature enough to just be provided with little to no maintenance.
(I know I can lock the upgrade with pacman.conf->IgnorePkg, but for new installs I have to dig in aur-mirror.git or in the Unofficial User Repositories.)
I have seen users asking for old versions in the comments every so often, so if all fails maybe a simple github gist with old PKGBUILDs/Install.scripts would help. Thanks.
sm0x commented on 2013-12-16 08:38 (UTC)
Can't connect :(
teamviewerd is running, but when i try to connect on my ArchMaschines, it stucks on "connecting..." while nothing happens :(
On both PCs, have anyone an idea why this happens?
swiftgeek commented on 2013-12-13 21:15 (UTC)
Also .desktop file misses two things (notice missing %u):
Exec=/opt/teamviewer9/tv_bin/script/teamviewer %u
MimeType=x-scheme-handler/teamviewer8;
Change requires `update-desktop-database /usr/share/applications` in post_install
(And probably something else because i can't get it to work also in firefox, though after this change prompt to choose binary to open url is shown)
swiftgeek commented on 2013-12-13 20:14 (UTC)
It should be enough to sed those lines
./tv_bin/script/tvw_config: TV_LOG_DIR="$TV_BASE_DIR/logfiles"
./tv_bin/script/tvw_config: TV_INSTALL_LOG="$TV_BASE_DIR/logfiles/install_teamviewerd.log"
./tv_bin/script/tvw_config: TV_CFG_DIR="$TV_BASE_DIR/config"
Also global.conf rewrites itself so kinda not useful after all :<
Maybe sed inside ./tv_bin/script/tvw_config could provide similar effect…
VDP76 commented on 2013-12-13 20:02 (UTC)
thanks for that, swiftgeek... those pop-up have always annoyed me!
swiftgeek commented on 2013-12-13 19:46 (UTC)
Add "[int32] ShowTaskbarInfoOnMinimize = 0" to "~/.config/teamviewer9/config/client.conf" to disable most useless popup/balloon ever - "teamviewer is still running"… No idea yet how to make it global. (Wasted 30 minutes on »Windows« for this… so i will take some time for convalescence)
Also "/opt/teamviewer*/logfiles" should point to some dir in /var/log
Same would go for config (/var/lib)
… And found global config accidentally
/opt/teamviewer*/config/global.conf
(If this was helpful for your job - I have none)
RazZziel commented on 2013-12-11 16:23 (UTC)
After I cleaned all the configuration and reinstalled teamviewer, it started working again
RazZziel commented on 2013-12-11 16:15 (UTC)
TeamViewer stopped starting up after I upgraded to version 9. /etc/systemd/system/teamviewerd.service was pointing to teamviewer8, but even after fixing that the client runs and quits before showing any window, with no error
mbunkus commented on 2013-12-06 11:48 (UTC)
Minor nitpiuck: Your post_install() routine still talks about TeamViewer 8. post_remove() removes the correct directory, though.
max-k commented on 2013-12-06 08:30 (UTC)
Hi,
You must also update your teamviewer.install file so it refelects the version (9).
Thanks.
Hilinus commented on 2013-12-06 07:55 (UTC)
Updated.
saabzero commented on 2013-12-03 14:39 (UTC)
i was checking today and found that this package is now officially out of date.
http://www.teamviewer.com/en/download/linux.aspx says 9.0.24147 at the time of writing this.
Please update this package :)
developej commented on 2013-11-17 08:15 (UTC)
any way to fix this?
sudo journalctl -u teamviewerd.service
-- Reboot --
Nov 16 23:27:01 workstation systemd[1]: Starting TeamViewer remote control daemon...
Nov 16 23:27:01 workstation systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Nov 16 23:27:01 workstation systemd[1]: Started TeamViewer remote control daemon.
a guy in the forums told me to try to change the PID file location to /var/run/teamviewerd/teamviewerd.pid, didn't help
VDP76 commented on 2013-11-15 08:27 (UTC)
@ZeroBit, is that reproducible?
on my pc, the md5sums in the PKGBUILD seem to match those of the downloaded .deb files for both architectures.
try to repeat the install and/or use a different AUR helper and/or download, check the md5sum and compile the package manually...
ZeroBit commented on 2013-11-15 04:46 (UTC)
==> Validating source files with md5sums...
teamviewer_linux_x64-8.0.20931.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build teamviewer.
dgbaley27 commented on 2013-11-13 15:43 (UTC)
I'm not sure if there's different stuff in there, but I noticed they provide a .tar.gz rather than a .deb directly on the website.
flamusdiu commented on 2013-11-05 12:41 (UTC)
Not sure why this is out of date. Checking the source (http://www.teamviewer.com/en/download/linux.aspx) shows 8.0.20931 as the current version. There is a beta package out; however, this is the beta package installer.
skiguy0123 commented on 2013-10-13 15:07 (UTC)
I switched from NetworkManager to netctl, and this caused systemctl start teamviewerd to hang indefinately. For a workaround, I commented out the line starting with "After" in the service file, and this seems to work.
Disclaimer: There's a very good chance I botched my netctl configuration, I just stopped messing with it when I could consistently get online.
z1lt0id commented on 2013-09-18 03:46 (UTC)
I'm using testing repos and it seems that it doesn't play well with SystemD. I get the following errors.
TeamViewer 8.0.20931
teamviewerd status teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; disabled)
Active: active (running) since Wed 2013-09-18 13:42:10 EST; 1min 1s ago
Process: 14376 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 14378 (teamviewerd)
CGroup: /system.slice/teamviewerd.service
└─14378 /opt/teamviewer8/tv_bin/teamviewerd -d
Sep 18 13:42:10 ziltoid-pc systemd[1]: PID file /var/run/teamviewerd.pid not readable (yet?) after start.
Sep 18 13:42:10 ziltoid-pc systemd[1]: Started TeamViewer remote control daemon.
TeamViewer ID: not found
Try restarting the TeamViewer daemon (e.g. teamviewer --daemon restart)
And here is the systemd status.
systemctl status teamviewerd.service
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; disabled)
Active: active (running) since Wed 2013-09-18 13:42:10 EST; 26s ago
Process: 14376 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 14378 (teamviewerd)
CGroup: /system.slice/teamviewerd.service
└─14378 /opt/teamviewer8/tv_bin/teamviewerd -d
commented on 2013-09-14 18:07 (UTC)
Thanks Hilinus! Hopefully this version works better :)
Hilinus commented on 2013-09-13 17:56 (UTC)
Updated.
commented on 2013-09-06 15:35 (UTC)
It seems to be a "teamviewerd" problem...
By killing /opt/teamviewer8/tv_bin/teamviewerd -d and running it again, it works perfectly...
commented on 2013-09-06 08:42 (UTC)
Hi,
teamviewer seems to be started (my computer appears in connected clients as friends tell me it's OK). BUT i they can't connect :
it says "Connecting ..." and no more.
sudo systemctl status teamviewerd
[sudo] password for olivier:
teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; enabled)
Active: active (running) since ven. 2013-09-06 10:29:34 CEST; 6min ago
Process: 580 ExecStart=/opt/teamviewer8/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
Main PID: 582 (teamviewerd)
CGroup: name=systemd:/system/teamviewerd.service
├─582 /opt/teamviewer8/tv_bin/teamviewerd -d
└─612 /opt/teamviewer8/tv_bin/wine/bin/wineserver
sept. 06 10:29:34 antergos systemd[1]: teamviewerd.service: Supervising process 582 which is not our child. We'll most likely not notice...t exits.
sept. 06 10:29:34 antergos systemd[1]: Started TeamViewer remote control daemon.
A weird thing : it worked the very first time i installed teamviewer but on the next computer reboot, it started well (appears in connected clients list from my friends) but could not connect (no screen).
I've re-installed winbind, smbclient, ... but nothing new.
Thanx in advance for the help.
zeltak commented on 2013-08-27 05:06 (UTC)
thx Hilinus
i did have it installed by re-installing seems to do the trick
appreciate the help
Z.
Hilinus commented on 2013-08-26 16:10 (UTC)
@zeltak:
Have you tried installing the smbclient package?
zeltak commented on 2013-08-26 13:00 (UTC)
Hi Guys
urgent help needed as i am really dependent on teamviewer for work stuff (long story... :))
i cant Teamviewer to start anymore:
Init...
Checking setup...
Launching TeamViewer...
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 2
wine: Unhandled page fault on read access to 0xffffffff at address 0xf75b9155 (thread 0013), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 18 64") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: configuration in '/home/zeltak/.config/teamviewer8' has been updated.
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libwinbind-client.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by /usr/lib/samba/libutil_cmdline.so)
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
wine: Unhandled page fault on read access to 0xffffffff at address 0xf753a155 (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 140") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
any help would be really appriciated!
best
Z
zeltak commented on 2013-08-26 12:41 (UTC)
Hi Guys
urgent help needed as i am really dependent on teamviewer for work stuff (long story... :))
i cant Teamviewer to start anymore:
Init...
Checking setup...
Launching TeamViewer...
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 2
wine: Unhandled page fault on read access to 0xffffffff at address 0xf75b9155 (thread 0013), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 18 64") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: configuration in '/home/zeltak/.config/teamviewer8' has been updated.
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libwinbind-client.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by /usr/lib/samba/libutil_cmdline.so)
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
wine: Unhandled page fault on read access to 0xffffffff at address 0xf753a155 (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 140") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
any help would be really appriciated!
best
Z
zeltak commented on 2013-08-26 12:31 (UTC)
Hi Guys
urgent help needed as i am really dependent on teamviewer for work stuff (long story... :))
i cant Teamviewer to start anymore:
Init...
Checking setup...
Launching TeamViewer...
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 2
wine: Unhandled page fault on read access to 0xffffffff at address 0xf75b9155 (thread 0013), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 18 64") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
wine: configuration in '/home/zeltak/.config/teamviewer8' has been updated.
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libwinbind-client.so: version `SAMBA_4.0.8' not found (required by ntlm_auth)
ntlm_auth: /usr/lib/samba/libreplace.so: version `SAMBA_4.0.8' not found (required by /usr/lib/samba/libutil_cmdline.so)
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
wine: Unhandled page fault on read access to 0xffffffff at address 0xf753a155 (thread 0009), starting debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 140") (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
any help would be really appriciated!
best
Z
nickoe commented on 2013-08-18 21:16 (UTC)
It is just because I have that installed (serched for installed packages in relation to winbind), and your paste mention winbind.
nickoe commented on 2013-08-18 21:15 (UTC)
@sdukan, do you have libwbclient installed?
sdukan commented on 2013-08-18 13:32 (UTC)
No, it has not been fixed:
http://dpaste.com/1348066/
wine still fails to start teamviewer. glibc is 2.18-2.
VDP76 commented on 2013-08-17 14:56 (UTC)
@xyz3186
It has fixed it, indeed. Thanks for information!
xzy3186 commented on 2013-08-17 04:10 (UTC)
@VDP76, kalib
Today the problem was fixed by glibc-2.18-2.
kalib commented on 2013-08-16 20:06 (UTC)
Same in here.. stoped working.. :/
kalib commented on 2013-08-16 18:23 (UTC)
Same in here.. stoped working.. :/
VDP76 commented on 2013-08-16 09:36 (UTC)
@xzy3186 I can confirm that with the upgraded version of those packages TeamViewer has stopped to work, wine fails to start it.
by the way, this package is NOT out-of-date: the current stable version is 8.0.17147. On their website (http://www.teamviewer.com/en/download/linux.aspx) there is a version 8.0.17864, but is declared as "Other systems (not officially supported)".
PiousMinion commented on 2013-08-16 00:12 (UTC)
Take a look at the teamviewer forums. Seems about 50% of the posts describe my issue across various distros. This is almost certainly an upstream bug.
@xyz3168 It wasn't really working for me anyway. :P
xzy3186 commented on 2013-08-15 15:51 (UTC)
The following upgrade will break this package. I don't know why but be careful.
core/binutils 2.23.2-2 2 -> 3
core/glibc 2.17-6 -> 2.18-1
commented on 2013-08-13 12:20 (UTC)
Another note. On their website they have an updated tarbell of TeamViewer that is newer than the .deb on their site:
http://www.teamviewer.com/en/download/linux.aspx
Deb (32/64): 8.0.17146
Tarbell: 8.0.17864
commented on 2013-08-13 12:14 (UTC)
@Hilinus @PiousMinion
This isn't strictly an Arch Linux issue. Every Linux distro that I have tried has had issues with TeamViewer 8.0.17146 :(
Honestly, TeamViewer needs to make a full port for Linux to do it correctly, not a half-fast Wine version.. They have a lane to be the primary Linux Screen Sharing/Meeting tool (GoTo doesn't seem to care about Linux) and they have neglected concerns with version 8+
PiousMinion commented on 2013-08-12 11:01 (UTC)
@Hilinus This is printed on startup. When I try to connect, nothing new is printed. http://dpaste.com/hold/1340331/
Hilinus commented on 2013-08-12 07:42 (UTC)
Can you post the host logfile
~/.config/teamviewer8/logfiles/TeamViewer8_Logfile.log
when someone is attempting to connect?
PiousMinion commented on 2013-07-24 09:02 (UTC)
Same problem here. The service is running, the client is open on the desktop, and it says that there are no connection issues, but no external client can connect.
commented on 2013-07-05 20:22 (UTC)
I have same problem as Enyx. Help anyone?
eNyx commented on 2013-06-02 14:30 (UTC)
I have some strange problem with this package recently, i cant connect to a arch's teamviwer host i tried windows -> linux or linux -> linux it keeps in connecting forever... Also i have some strange alfanumeric passwords when it (should) be only a numeric password
cowai commented on 2013-06-02 13:15 (UTC)
EDIT: When I removed infality's fontconfig and installed the original ones it just worked.
cowai commented on 2013-06-02 11:42 (UTC)
After installing and starting the daemon it's stuck on trying to displaying the terms of use. But the GUI crashes. I have tried deleting ~/.teamviewer but to no help.
x33a commented on 2013-06-01 13:16 (UTC)
Here's the service file for anyone using OpenRC:
https://github.com/notfoss/archlinux-openrc-services/blob/master/init.d/teamviewerd
capoeira commented on 2013-05-11 18:04 (UTC)
>If you download this it's going to be the same :)
>pastebin converts it automatically
damnnn, this windows world sucks. hahahah
giner commented on 2013-05-11 17:05 (UTC)
> I converted it to unix format: http://pastebin.com/fwWqQPM9
If you download this it's going to be the same :)
pastebin converts it automatically
giner commented on 2013-05-11 17:04 (UTC)
sed -i 's/\r//g' teamviewer.sh
capoeira commented on 2013-05-11 17:03 (UTC)
I converted it to unix format: http://pastebin.com/fwWqQPM9
now it works
capoeira commented on 2013-05-11 16:57 (UTC)
thank's for the script giner, but it's got a problem executing;
/bin/bash^M: bad interpreter: no such file or directory
giner commented on 2013-05-09 23:17 (UTC)
Script to run teamviewer under normal user account: http://pastebin.com/WshA2G9J
Script requires "sudo" for iptables changes.
giner commented on 2013-05-09 21:56 (UTC)
If you closed teamviewer and want to start it again:
killall teamviewerd
/opt/teamviewer8/tv_bin/teamviewerd
# check opened port, should be 6039 but can vary
# if port is different you can:
# - kill teamviewerd, start again and repeat untill success
# or
# - sudo iptables -o lo -t nat -I OUTPUT --dst 127.0.0.1 -p tcp --dport 5939 -j REDIRECT --to-ports $OPENED_PORT
sudo netstat -nlpt | grep teamviewerd
teamviewer
giner commented on 2013-05-09 21:29 (UTC)
Work around to run TeamViewer 8 without root permissions (update):
sudo touch /var/run/teamviewerd.pid
sudo chown $USER /var/run/teamviewerd.pid
sudo iptables -o lo -t nat -I OUTPUT --dst 127.0.0.1 -p tcp --dport 5939 -j REDIRECT --to-ports 6039
/opt/teamviewer8/tv_bin/teamviewerd
teamviewer
capoeira commented on 2013-05-09 19:32 (UTC)
nice xillius200
now all the advantages of dummie-usibility are gone. lol
any alternatives?
commented on 2013-05-08 21:26 (UTC)
for all the problems of starting teamviewer this seemed to work for me a bit annoying I have to do it everytime I start teamviewer though...
systemctl stop teamviewerd
systemctl disable teamviewerd
systemctl enable teamviewerd
systemctl start teamviewerd
sudo teamviewer
at least it actually runs each time...it's just annoying but shell scripts help with that :)
UnsolvedCypher commented on 2013-05-04 16:05 (UTC)
It seems like the service file starts up teamviewer at startup sometimes. Is there a way to start the service without starting teamviewer?
roentgen commented on 2013-04-25 17:44 (UTC)
gustavi, enable multilib in pacman.conf
commented on 2013-04-25 11:37 (UTC)
Impossible to find "lib32-libxtst" in AUR.
Log:
==> Construction et installation du paquet
==> Installation/compilation des dépendances manquantes pour teamviewer:
Erreur: impossible de trouver la cible: lib32-libxtst
jevonearth commented on 2013-04-05 18:44 (UTC)
I have done a fresh install of Temviewer today, and all fresh config.
Trying to sign into Teamviewer (So I get a buddy list etc) always times out. I get the following error in the logs:
2013/04/05 11:39:27.417 8 9 G0!! BuddyList: SignIn failed. (SignIn Timeout), Errorcode=5
A Ubuntu user has a similar issue here: http://superuser.com/questions/560621/teamviewer-cannot-log-in
Has anybody come across this issue?
Hilinus commented on 2013-04-04 16:56 (UTC)
@ZeroBit:
Please scroll down, click on "Show all comments" and read the one Raikia posted.
ZeroBit commented on 2013-04-03 20:46 (UTC)
"sudo systemctl start teamviewerd" causes long shutdown to me.
How to get yo know the reason and solve it?
nickoe commented on 2013-03-27 18:13 (UTC)
@webdawg, you have to enable multilib.
webdawg commented on 2013-03-27 17:10 (UTC)
with yaourt:
==> Building and installing package
==> Install or build missing dependencies for teamviewer:
error: target not found: lib32-freetype2
with packer:
Dependency `lib32-alsa-lib' of `teamviewer' does not exist.
uname -a
Linux sesopsec 3.8.4-1-ARCH #1 SMP PREEMPT Wed Mar 20 22:10:25 CET 2013 x86_64 GNU/Linux
bawrak commented on 2013-03-26 04:03 (UTC)
@Alucryd / Hilinus
Thanks for that. After replacing freetype2-ubuntu (used for the LCD rendering patches to freetype2) with freetype2 and installing lib32-freetype my teamviewer finally starts up!
kellerman commented on 2013-03-21 20:47 (UTC)
And I kinda hate that it's installing it into another wine environment.
kellerman commented on 2013-03-21 20:45 (UTC)
It worked for me for a 1-2 reboots, then just hangs. Installing it on wine doesn't help either. I have freetype2-infinality and lib32-freetype-infinality installed on my arch.
Output:
http://pastebin.com/ysStFG6f
hcjl commented on 2013-03-15 13:16 (UTC)
Does anyone know how to start Teamviewer daemon so that I can access the server without a user being logged in?
I already started a discussion here https://bbs.archlinux.org/viewtopic.php?id=155990, but obviously nobody knows.
Thx & Rgds
hcjl
Hilinus commented on 2013-03-14 17:37 (UTC)
@Alucryd:
I removed lib32-freetype2 and teamviewer hangs as expected. I have added the dependency to the PKGBUILD.
Thanks, as always.
solixxx commented on 2013-03-14 11:18 (UTC)
@giner
Thx for the workaround
alucryd commented on 2013-03-12 10:09 (UTC)
If lib32-freetype2 is needed, then freetype2 is probably needed on i686 machines, can somebody confirm this?
Hilinus: Anyway, I must have missed the deps when I made the PKGBUILD, can you add them both?
commented on 2013-03-12 10:01 (UTC)
I can confirm that lib32-freetype2 is necessary, otherwise it just hangs without stopping.
giner commented on 2013-03-07 20:33 (UTC)
Work around to run TeamViewer 8 without root permissions:
sudo iptables -o lo -t nat -I OUTPUT --dst 127.0.0.1 -p tcp --dport 5939 -j REDIRECT --to-ports 6039
/opt/teamviewer8/tv_bin/teamviewerd
teamviewer
arokux commented on 2013-03-07 12:06 (UTC)
I needed to install multilib/lib32-freetype2 so that teamviewer works.
Hilinus commented on 2013-03-04 17:03 (UTC)
@JohnnyDeacon
Enable the [multilib] repo.
JohnnyDeacon commented on 2013-03-04 16:09 (UTC)
==> Making package: teamviewer 8.0.17147-4 (Mon Mar 4 11:08:41 COT 2013)
==> Checking runtime dependencies...
==> Missing Dependencies:
-> lib32-libxtst
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
wonko commented on 2013-03-03 22:43 (UTC)
@DaemonGPL
Thanks, worked for me, too. ~/.config/teamviewer8 must not exist, otherwise it didn't start even using sudo. Had to delete it first, then ran once using sudo and afterwards it did start up normaly.
commented on 2013-03-03 07:29 (UTC)
@wonko
Finally fixed this error!!! Appears it needs 'sudo teamviewer' to run for the first time... I wasted many days troubleshooting. 'sudo pacman -Rs teamviewer' > download tarball > 'makepkg -s' > 'sudo pacman -U teamviewer-8.0.17147-4-x86_64.pkg.tar.xz' > 'sudo teamviewer --daemon enable' > 'sudo systemctl start teamviewerd' > 'sudo teamviewer'
Finally launched without the error... Maybe this will help someone else.
Launching TeamViewer...
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
scorici commented on 2013-03-02 15:14 (UTC)
@mdallaire
Click "All comments" at the bottom of the page and search for "2012-10-31 06:56"
(without the quotes) and there I found a PKGBUILD for teamviewer 7 and I made a little modification here: http://pastebin.com/CdC5s8MK
I tried it on i686 (I can't guarantee that it will work on x86_64) and fires up but did not connect to anyone...
You just have to trust the dependency posted by scarecrow or try to figure them out yourself.
Next time you want to update try to backup your packages first with bacman in pacman-contrib package:
bacman teamviewer
And optionally ignore the package /etc/pacman.conf
Uncomment "#IgnorePkg =" and add "teamviwer" :
"#IgnorePkg =" >> "IgnorePkg =teamviewer"
until you upgrade your license.
Take care and good luck.
Ferik commented on 2013-03-01 02:59 (UTC)
sudo pacman -Rsc teamviewer
remove teamviewer8 in /home/<yourhome>/./config
Install:
yaourt -Sy teamviewer
sudo teamviewer --daemon enable
sudo teamviewer --daemon start
work for me bye :)
mdallaire commented on 2013-02-28 13:50 (UTC)
Does anyone still have a copy of the PKGBUILD for teamviewer 7 ? License upgrade costs to version 8 are quite expensive so I will have to stay at version 7 for a while...
Hilinus commented on 2013-02-27 19:43 (UTC)
@pwalker
You should enable the [multilib] repository, that's where all the lib32- packages are located.
pwalker commented on 2013-02-26 21:23 (UTC)
the x64 build seems a bit out of date. Some of the dependencies are no longer in the aur, like lib32-alsa. Can anyone else install this?
commented on 2013-02-25 22:27 (UTC)
Hi all, for me a reboot resolved the issue...
wonko commented on 2013-02-25 21:24 (UTC)
Similar problem as elvisd. Wiped ~/.teamviewer, ~/.config/teamviewer8 , but didn't solve the problem. 64 bit, kde 4.10.
Ideas? Any suggestions are very appreciated.
Init...
Checking setup...
Launching TeamViewer...
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:resource:GetGuiResources (0xffffffff,0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32dc60,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x32d918,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x32dc60,0x00000000), stub!
alucryd commented on 2013-02-25 18:04 (UTC)
@Hilinus: My computer shuts down just fine with teamviewerd running. How many of you guys are affected?
@elvisd: I ran into that problem once, I believe I fixed it by wiping ~/.config/teamviewer (or sth like that). Can you try that?
Hilinus commented on 2013-02-25 17:57 (UTC)
@Raikia
I noticed the same problem using teamviewerd. I'm searching for some other solutions, but if I don't find anything satisfying I'll use your hotfix.
Thanks again.
commented on 2013-02-25 16:36 (UTC)
Hi I have installed but have the following problem (I'm on 64 bit):
Init...
Checking setup...
Launching TeamViewer...
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:resource:GetGuiResources (0xffffffff,0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33dc60,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33d918,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x33dc60,0x00000000), stub!
Raikia commented on 2013-02-25 02:23 (UTC)
I'm having trouble shutting down my computer with teamviewerd running.
I followed the instructions here: http://freedesktop.org/wiki/Software/systemd/Debugging#Shutdown_Completes_Eventually
Here is my log output:
http://pastebin.com/iAW51AeQ
It gets to "Stopped target Remote File Systems." and hangs for about 2 minutes. As you can see in that snippet of log file, teamviewerd is the next process to get shut down.
Does anyone else have this problem? Any ideas on how to fix it? My quick-fix for it is:
sudo vim /etc/systemd/system/teamviewerd.service
Under "[Service]", add "TimeoutStopSec = 2"
This will add a 2 second timeout to the shutdown process instead of the default 90 seconds (which is what I was getting).
Its still a hotfix since it doesn't address the problem, just minimizes it.
I'm able to supply any other log files you would like. Anybody have any ideas?
Hilinus commented on 2013-02-24 13:59 (UTC)
Thanks for your contributions and suggestions, Alucryd. I have uploaded your package.
alucryd commented on 2013-02-24 01:09 (UTC)
I have merged teamviewer8 into this package. However your PKGBUILD contains quite a few errors, please upload this tarball instead: http://dl.dropbox.com/u/43076209/teamviewer-8.0.17147-4.src.tar.gz
From now on please run namcap on both your PKGBUILD and the resulting pkg.tar.xz to notice these kind of errors (missing maintainer line, redundant deps, license array, etc).
See here: https://wiki.archlinux.org/index.php/PKGBUILD
And here: https://wiki.archlinux.org/index.php/Namcap
PhotonX commented on 2013-02-23 09:44 (UTC)
I had the same problem as scorici and his workaround worked for me (thanks, @scorici :)). Maybe the .service file should be placed to the right place by pacman?
hariskar commented on 2013-02-18 18:10 (UTC)
trizen, thank you. I tried that before I posted, but did not work. So I uninstalled 8.0.17147-1 and made a clean installation of 8.0.17147-3 and now teamviewerd does not autostart.
trizen commented on 2013-02-18 15:22 (UTC)
@hariskar - Disable it by running: systemctl disable teamviewerd
When you need it, start it with the following command: systemctl start teamviewerd (not 'enable'!)
hariskar commented on 2013-02-18 15:16 (UTC)
How can I make teamvewerd not start automatically? I want to start it manually when
i need it.
Thank you
scorici commented on 2013-02-18 06:26 (UTC)
I didn't manage to start the teamviewer daemon with these commands:
sudo teamviewer --daemon start
or
sudo systemctl start teaviewerd
So I had to make a link for systemctl to recognize teamviewerd.service:
sudo ln -s /opt/teamviewer8/tv_bin/script/teamviewerd.service /usr/lib/systemd/system/
If anyone encounters this problem I hope this will help.
Hilinus commented on 2013-02-17 19:32 (UTC)
Sorry guys, I missed the old entry.
trizen commented on 2013-02-17 14:32 (UTC)
@Fraterius - here is a working PKGBUILD: http://pastebin.com/Eg5PzPpF
Fraterius commented on 2013-02-17 12:30 (UTC)
install: cannot stat 'teamviewer.desktop': No such file or directory
any ideas?
Mektub commented on 2013-02-17 09:57 (UTC)
fabienwang,
thanks, it works.
Mektub
schrodinger72 commented on 2013-02-17 06:20 (UTC)
ava1ar, you had a typo on the last install in package().
here is the only WORKING pkgbuild http://pastebin.com/6vkkjdXe
ava1ar commented on 2013-02-17 00:21 (UTC)
Here is updated PKBDUILD: http://pastebin.com/V8PpYxDT
commented on 2013-02-16 23:08 (UTC)
+1 with ras0ir.
ras0ir commented on 2013-02-16 22:00 (UTC)
I get following error while trying to install it:
install: cannot stat ‘teamviewer.desktop’: No such file or directory
Hilinus commented on 2013-02-16 21:43 (UTC)
Fixed the .desktop file.
test0 commented on 2013-02-16 20:26 (UTC)
@GUiHKX
I think you should do it, because as you can see, the default installing method also enables it. Closed-source software, as root, in autostart... What the hell?
And of course that would simplify the installation process.
test0 commented on 2013-02-16 20:14 (UTC)
Because in /opt/teamviewer8/tv_bin/script/tvw_daemon there is:
function installDaemonSystemD()
{
exec 2>&1
installLogHeader "Installing daemon ($TV_VERSION) for 'systemd' ..."
installDaemonCfg "$TVD_SYSD_DIR" "$TVD_SYSD_FILE"
systemctl daemon-reload # just in case...
echo "Try: systemctl enable $TV_SCRIPT_DIR/$TVD_SYSD_FILE"
systemctl enable "$TV_SCRIPT_DIR/$TVD_SYSD_FILE" # on openSUSE 12.2, systemctl does not accept a sole filename (if symlink?)
[ $? = 0 ] && return
echo "Try: systemctl enable $TVD_SYSD_FILE"
systemctl enable "$TVD_SYSD_FILE" # on Fedora 15, systemctl does not accept a full path (to /opt/...)
}
It also enables it, not only installing.
gbr commented on 2013-02-16 20:14 (UTC)
I just don't know if that's the right way to do it. :p
gbr commented on 2013-02-16 20:12 (UTC)
@russo79, @test0
I guess that it will work too, but if I add this line to the PKGBUILD, will solve all the issues:
install -Dm644 $pkgdir/opt/teamviewer8/tv_bin/script/teamviewerd.service $pkgdir/usr/lib/systemd/system/teamviewerd.service
test0 commented on 2013-02-16 20:08 (UTC)
After
# teamviewer --daemon enable
and trying to
# systemctl disable teamviewerd.service
I've got a
Failed to issue method call: No such file or directory
So I've decided to do
# ln -s /opt/teamviewer8/tv_bin/script/teamviewerd.service /etc/systemd/system/teamviewerd.service
manually.
russo79 commented on 2013-02-16 20:05 (UTC)
Oh, and I think I'm a bit less stupid now ;P
russo79 commented on 2013-02-16 20:05 (UTC)
@GUiHKX
My bet would be to do something like this:
You enable the service with sudo teamviewer --daemon enable.
You then you manually remove the /etc/systemd/system/graphical.target.wants/teamviewerd.service file so that the service isn't automatically started on boot.
Afterwards, you can use teamviewer --daemon start as you wish.
gbr commented on 2013-02-16 19:59 (UTC)
@russo79
hehheh it's ok...
russo79 commented on 2013-02-16 19:46 (UTC)
@GUiHKX
Forget my previous comment. I'm stupid sometimes.
russo79 commented on 2013-02-16 19:41 (UTC)
@GUiHKX
I may be wrong here, but it seems to me that with systemd you cannot start a service that is not enabled.
gbr commented on 2013-02-16 19:39 (UTC)
@Hilinus
I'm getting this error when I try with '--start':
# teamviewer --daemon start
systemctl start teamviewerd.service
Failed to issue method call: Unit teamviewerd.service failed to load: No such file or directory. See system logs and 'systemctl status teamviewerd.service' for details.
fail
I didn't use the '--enable' because I don't want to enable the service on bootup. Thank you.
crysisgod commented on 2013-02-16 13:42 (UTC)
Please edit .desktop file.
Hilinus commented on 2013-02-16 12:44 (UTC)
@GUiHKX:
Please see the .install file. Teamviewer manages automatically teamviewerd.service.
Just issue the "teamviewer --daemon enable" to link the .service under /etc/systemd/system and start it.
gbr commented on 2013-02-16 10:38 (UTC)
Now Teamviewer have a daemon, which is needed to get it work. Adding this will do the job:
install -Dm644 $pkgdir/opt/teamviewer8/tv_bin/script/teamviewerd.service $pkgdir/usr/lib/systemd/system/teamviewerd.service
and then to start the service:
# teamviewer --daemon start
Or if you don't want to have to start the service every time you use teamviewer, you can enable it on system bootup:
# systemctl enable teamviewerd
(I'm sorry for my english)
Hilinus commented on 2013-02-16 10:06 (UTC)
Updated. Let me know if you encounter some issues.
butler360 commented on 2013-02-15 09:33 (UTC)
The stable version of 8 is out: http://www.webupd8.org/2013/02/popular-remote-desktop-tool-teamviewer.html
alucryd commented on 2013-02-13 08:58 (UTC)
@Raikia: Hmm, this does not happen to me, my machine stops fine. I have pretty much the same log as you, except I'm using gdm instead of systemd-user-sessions to handle my session but I doubt it's relevant.
Don't know what could be going wrong on your side. If you have time, could you try a fresh install (either on your HDD or in a VM, both could be informative)? Also it might be worth reporting the bug in their forums.
Raikia commented on 2013-02-12 21:35 (UTC)
I managed to fix the problem a little better by adding a timeout to the systemd service file:
sudo vim /usr/lib/systemd/system/teamviewerd.service
Under "[Service]", add "TimeoutStopSec = 2"
This will add a 2 second timeout to the shutdown process instead of the default 90 seconds (which is what I was getting).
Its still a hotfix since it doesn't address the problem, just minimizes it.
Raikia commented on 2013-02-12 20:39 (UTC)
I'm having trouble shutting down my computer with teamviewerd running. I have done "sudo systemctl enable teamviewerd" so that it starts and stops by itself, but it hangs on shutdown while disabling.
I followed the instructions here: http://freedesktop.org/wiki/Software/systemd/Debugging#Shutdown_Completes_Eventually
Here is my log output:
http://pastebin.com/iAW51AeQ
It gets to "Stopped target Remote File Systems." and hangs for about 2 minutes. As you can see in that snippet of log file, teamviewerd is the next process to get shut down.
Does anyone else have this problem? Any ideas on how to fix it? My quick-fix for it is to write a small script that starts the daemon, runs teamviewer8, then stops the daemon...but that obviously kills the ability to have the daemon running in the background like it should be. Aside from having to manually stop the service before shutting down, does anyone have any recommendations? I'm able to supply any other log files you would like.
alucryd commented on 2013-02-12 14:15 (UTC)
If you had a look at the terminal when you installed it, the post install script tells you exactly how to start teamviewerd:
sudo systemctl start teamviewerd
alex-eri commented on 2013-02-12 12:29 (UTC)
sory)
"teamviewerd -d" starts)
alex-eri commented on 2013-02-12 12:25 (UTC)
i installed teamviewer8 by yaourt. started it. it asked me to start teamviewerd, but it not started without errors. i tryed ldd and strace to anderstand what it want.
/opt/teamviewer8/tv_bin/teamviewerd
execve("/opt/teamviewer8/tv_bin/teamviewerd", ["/opt/teamviewer8/tv_bin/teamview"...], [/* 51 vars */]) = 0
and so on as is as i posted before.
i tryed put teamviewerd in /usr/bin as workarount (after reading debian postinst script), but it fails to start too.
alucryd commented on 2013-02-12 09:01 (UTC)
@alex-eri: Have never used strace, does this mean you put teamviewerd in '/usr/bin'?
execve("/usr/bin/teamviewerd", ["teamviewerd"], [/* 49 vars */]) = 0
alex-eri commented on 2013-02-11 13:12 (UTC)
seems needs symlinks
strace teamviewerd
execve("/usr/bin/teamviewerd", ["teamviewerd"], [/* 49 vars */]) = 0
brk(0) = 0xa394000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7750000
readlink("/proc/self/exe", "/opt/teamviewer8/tv_bin/teamview"..., 4096) = 35
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/tls/i686/sse2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/tls/i686/sse2", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/tls/i686/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/tls/i686", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/tls/sse2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/tls/sse2", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/tls/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/tls", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/i686/sse2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/i686/sse2", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/i686/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/i686", 0xbfbc4240) = -1 ENOENT (No such file or directory)
open("/opt/teamviewer8/tv_bin/../lib/sse2/libpthread.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat64("/opt/teamviewer8/tv_bin/../lib/sse2", 0xbfbc4240) = -1 ENOENT (No such file or directory)
alucryd commented on 2013-01-26 14:43 (UTC)
@fuxter: I always leave upx disabled, all my roots are lzo btrfs.
fuxter commented on 2013-01-26 09:49 (UTC)
@bawrak @Alucryd i just repackaged teamviewer without automatic `upx' and now it runs. i was getting core dumps before. weird.
alucryd commented on 2013-01-25 20:59 (UTC)
@webmonarch: That's weird cause the command I (totally mis)used was setting the executable bit on everything. I've fixed that now though, only what needs to be executable is. Can you try rev 7?
webmonarch commented on 2013-01-25 20:18 (UTC)
i had some permission issues on my machine. Fixed them with chmod +x'ing the following:
/opt/teamviewer8/tv_bin/teamviewerd
/opt/teamviewer8/tv_bin/script/teamviewer
/opt/teamviewer8/tv_bin/wine/bin/wine
alucryd commented on 2013-01-25 09:54 (UTC)
@LookTJ: I wouldn't say one is better than the other, this package is bound to disappear anyway once teamviewer 8 is out of beta, unless there is a beta for the 9th version by that time. If that becomes a regular thing, I'll have its name changed to teamviewer-beta.
LookTJ commented on 2013-01-25 09:15 (UTC)
a better source is the tar they provide. http://www.teamviewer.com/download/teamviewer_linux.tar.gz
LookTJ commented on 2013-01-25 09:14 (UTC)
Would a better name be teamviewer-beta?
bawrak commented on 2013-01-23 10:20 (UTC)
Thanks.
I Compared your log to mine and the first line that I don't have is:
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
Maybe it is network related? I will give the teamviewerforums a try.
alucryd commented on 2013-01-23 10:14 (UTC)
@bawrak: I tried launching teamviewer using my system's wine, but to no avail.
Using the built-in, I get the exact same CLI messages as you, but mine keeps going past that point, don't why it does not for you. I suggest you ask for help here: http://teamviewerforums.com/index.php?board=2.0, unfortunately I don't really know what could go wrong.
bawrak commented on 2013-01-23 09:10 (UTC)
Unfortunately no change after rm -r ~/.config/teamviewer8
I do get a small popup for maybe 1/2 a second saying wine is generating a new configuration, but nothing happens afterwards. CLI has same text as my first post below.
alucryd commented on 2013-01-23 09:04 (UTC)
Well I'm getting a lot of errors too (http://pastebin.com/p5TTiJBx) but the GUI starts and I could succesfully connect to the demo server.
Could you delete ~/.config/teamviewer8 and try again? This is where teamviewer stores its wine config. Doing this got rid of the failed auto-start service errors it throws at the beginning for me.
bawrak commented on 2013-01-23 08:55 (UTC)
@Alucryd: Thanks.
Updated now to teamviewer8-8.0.16675-6. Did systemctl --system deamon-reload and started the teamviewerd again. Running teamviewer8 still gives me the same error as below.
Is it possible I am missing something else?
alucryd commented on 2013-01-23 08:41 (UTC)
@bawrak: Alright, can you try it now? It runs again on my machine.
alucryd commented on 2013-01-23 08:37 (UTC)
Well that's definitely a wine issue, but not the one in your system. teamviewer8 uses its own version. It happens to me too now, I'll see what I can do.
bawrak commented on 2013-01-23 04:46 (UTC)
Thanks for your work on this.
It does not work for me though. teamviewerd is running. Running teamviewer8 gives me:
---------------
Init...
Checking setup...
Launching TeamViewer...
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 2
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
err:winspool:add_printer_driver failed with 1722 for L"wineps.drv" (L"Windows NT x86")
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
fixme:resource:GetGuiResources (0xffffffff,0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33df44,0x00000000), stub!
fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33dbfc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x33df44,0x00000000), stub!
-------------
And then nothing. It just hangs there with no GUI. I have mono installed and the latest version of wine if that is important.
Any suggestions?
Thanks
Hilinus commented on 2013-01-17 17:38 (UTC)
Is this reproducible on other distros, such as Ubuntu or Fedora? I'm searching...
alucryd commented on 2013-01-16 08:40 (UTC)
@bandroix: No problem. There is indeed a daemon that must be launched for teamviewer to work (teamviewer fails to start if it is not running). As for what it's used for, I couldn't find any useful info on the internet, and of course the file is a binary so no peeking in it. You could try to connect to a computer running only the daemon to find out whether it enables this (only have one working computer at the moment so I can't test).
bandroidx commented on 2013-01-16 08:06 (UTC)
@Alucryd thank you for the info, the changes, the testing, and the hard work maintaining and creating this package. It's much appreciated. Now I can finally install teamviewer 8 and won't have to connect to my work pc first to connect to machines using this newer version.
That reminds me. I recall there being a service involved with this version? Is that something that is required for inbound connections only? I really prefer not to have another service running especially since I never want inbound connections to be possible under any circumstances. (call me paranoid, i call me security conscious LOL)
commented on 2013-01-15 23:44 (UTC)
Closing teamviewer 7.0.9377-1 causes multiple ghost instances to spawn, consuming all system resources. Only work-around for user is to reboot system; trying to kill tasks returns error that user doesn't have the permissions.
Repeatable 100% of the time.
Using Manjaro xfce 0.8.3
alucryd commented on 2013-01-15 22:00 (UTC)
I doubt this is my doing, I just added a message in an install file. Next time you might want to be a bit more precise, because "doesn't work" will not get you very far in the Linux world.
commented on 2013-01-15 21:59 (UTC)
now works
commented on 2013-01-15 19:30 (UTC)
doesn't work
alucryd commented on 2013-01-14 16:31 (UTC)
Okay I made some changes, you can have both teamviewer package installed at the same time. Also, I fired both up, and had the same ID, it will probably be the same with a licensed version.
alucryd commented on 2013-01-14 16:07 (UTC)
@bandroidx: I don't know about the ID, have always used the free version.
About the compatibility, there are currently some file conflicts (which reminds me I didn't put a conflicts array in the PKGBUILD) but nothing some editing can't handle. I could modify the PKGBUILD to play along well with teamviewer if you need both at the same time.
bandroidx commented on 2013-01-14 15:52 (UTC)
Does anyone know if installing this will end up with the same ID as with teamviewer 7? Mine is licensed and I am running low on license transfers. Also is it possible to have this AND teamviewer AUR package installed at the same time (teamviewer 7) and use either or?
alucryd commented on 2013-01-13 15:04 (UTC)
There's no need for that, teamviewer8-beta does not exist anymore, any user upgrading from it should have removed it beforehand.
commented on 2013-01-13 12:57 (UTC)
add teamviewer8-beta to conlict packages
lockheed commented on 2013-01-11 09:23 (UTC)
I just tried connecting with this version to a newly installed windows version and I got the message
"Your partner uses a newer version of TV. Would you like to update to establish connection?"
And the only option is Cancel.
coolpyrofreak commented on 2013-01-05 04:28 (UTC)
One of the listed download options for v7 is a tar.gz. Any way we could use this to build the package instead of the .deb?
alucryd commented on 2013-01-03 16:10 (UTC)
@simul: Woops, forgot a ${pkgdir}, thx for the report, it should work fine now.
simul commented on 2013-01-03 15:50 (UTC)
I'm getting this error when trying to install with yaourt.
Starting package()...
install: cannot stat ‘/opt/teamviewer8/tv_bin/script/teamviewerd.service’: No such file or directory
alucryd commented on 2013-01-03 08:44 (UTC)
Okay, so systemd is not inception-friendly, can't create a symlink to a symlink^^ Copied the service file directly, also corrected the log and config dirs.
alucryd commented on 2013-01-02 18:02 (UTC)
Wow, I just realized my symlinks in /var/log and /etc are not named correctly, they should both be named teamviewer. Sorry about that, I'll correct that too.
alucryd commented on 2013-01-02 17:57 (UTC)
@roentgen: Yeah I noticed the thing about the symlink too, I intended to look into the reason systemd doesn't like it but haven't found the time yet (I'll just copy the file over instead of making a symlink).
About the log symlink, I was wondering the same thing but seeing the deb package contains it, I added it. Haven't had a crash yet so I can't really tell whether it puts crashlogs in there. I'll probably remove it if nothing is created in there after some time (again haven't had the time to look into this, probably next week).
I'll try to fix the service file issue tomorrow.
roentgen commented on 2013-01-02 16:15 (UTC)
1. The systemd service file is a symlink and it seems systemd doesn't like it
# systemctl enable teamviewerd.service
Failed to issue method call: No such file or directory
2. Is it really necessary to have the /var/log/logfiles symlink?
alucryd commented on 2012-12-29 18:49 (UTC)
@Alp: Glad it worked for you! Also please note that I won't add this in the package as SysV is no longer supported on ArchLinux.
Alp commented on 2012-12-29 18:29 (UTC)
Great, thanks! But it's /etc/rc.d instead of /etc/init.d
That worked for me:
> sudo cp /opt/teamviewer8/tv_bin/script/teamviewerd.sysv /etc/rc.d/teamviewerd
> sudo chmod 755 /etc/rc.d/teamviewerd
> sudo /etc/rc.d/teamviewerd start
After that, teamviewer can be started without problems.
alucryd commented on 2012-12-29 18:23 (UTC)
Are you using systemd or SysV to boot your system? I have no problem here using systemd. If you are using SysV you'll have to copy /opt/teamviewer8/tv_bin/script/teamviewerd.sysv to /etc/init.d/teamviewerd and start it there (sudo /etc/init.d/teamviewerd start) then launch teamviewer.
Alp commented on 2012-12-29 18:04 (UTC)
Thanks for your answer. I get another error now:
> sudo systemctl start teamviewerd
Failed to get D-Bus connection: No connection to service manager.
alucryd commented on 2012-12-29 17:33 (UTC)
I'm taking over the package. You have to start the daemon with systemd "sudo systemctl start teamviewerd" then you will be able to launch teamviewer.
Alp commented on 2012-12-29 17:29 (UTC)
@Ariec:
i tried your solution: /opt/teamviewer8/tv_bin/teamviewerd start && teamviewer
but it does not work, i am still getting this error message:
"Teamviewer daemon is not running
Please start teamviewerd and then restart TeamViewer"
commented on 2012-12-26 06:55 (UTC)
It's work:
/opt/teamviewer8/tv_bin/teamviewerd start && teamviewer
[url=http://www.zimagez.com/zimage/-26122012-105846.php][img]http://www.zimagez.com/miniature/-26122012-105846.php[/img][/url]
Tomato commented on 2012-12-24 11:08 (UTC)
package still doesn't install correctly, no systemd service file
gardar commented on 2012-12-23 20:35 (UTC)
sudo teamviewer --daemon enable
Sun Dec 23 20:32:12 GMT 2012
Action: Installing daemon (8.0.16675) for 'SystemV' ...
Failed to update daemon configuration
/etc/init.d/teamviewerd start
/opt/teamviewer8/tv_bin/script/tvw_daemon: line 166: /etc/init.d/teamviewerd: No such file or directory
fail
alucryd commented on 2012-12-21 15:11 (UTC)
You might want to fix that desktop file of yours. Just copying the one from the regular teamviewer is not gonna do it.
And that "teamviewer --daemon enable" should be done in the pkgbuild because now we all have a service file in our system that is not referenced by pacman, and this is _bad_.
Finally please run namcap on your package once build and correct all the errors it throws at you, there are a lot but you can of course disregard errors telling you files are in a wrong directory as /opt is not supported.
commented on 2012-12-21 07:25 (UTC)
muflone, a new upstream version was released. PKGBUILD has been updated to the latest verion now. :)
muflone commented on 2012-12-20 23:55 (UTC)
wrong md5 value for both 32 and 64 bit packages.
==> Validating source files with md5sums...
teamviewer_linux-8.0.16485.deb ... FAILED
teamviewer.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
$ md5sum *.deb
8615365b444eb3927cefbbf3dbed6ffa teamviewer_linux-8.0.16485.deb
4f718ad52ea9091fab4218968a3c1fd7 teamviewer_linux_x64-8.0.16485.deb
Fong-Wan commented on 2012-12-20 03:54 (UTC)
New version: v8.0.16675 beta
Zeth commented on 2012-12-17 09:40 (UTC)
The only clients that'll be unable to connect are outdated clients in their respective main version number.
E.g. I had collegues using windows with an old 7 version which where unable to connect. But they were asked to update either to latest 7 oder new 8 version.
And this package uses the latest 7 (7.0.9377) published on teamviewer.com so please don't mark it as outdatet...
Also, if you want to use the version 8, please use the teamviewer8-beta package.
I'd also vote for not upgrading this package to 8 even when 8 is released as stable (not beta) on the teamviewer website. It'll break my license.
commented on 2012-12-16 10:57 (UTC)
Once the daemon has been enabled via the 'teamviewer --daemon enable' command you should be abled to control it with systemctl.
commented on 2012-12-15 16:38 (UTC)
My fault.
Default behaviour for systemd is that enable is used for autostart on boot.
For example, I use tomcat and mysql for development, I can start/stop them as I want without enabling them first.
Teamviewer seems to do things differently. I can't even enable/disable the service using systemctl. I mistakenly assumed that "teamviewer --daemon" was just a wrapper for "systemctl".
commented on 2012-12-15 13:53 (UTC)
pkgname fixed, thanks.
You will need to enable the daemon before you can start it.
Use: 'teamviewer --daemon enable' to enable the daemon in systemd before you try to start it.
You cannot start a daemon that has not been enabled.
commented on 2012-12-15 10:06 (UTC)
It currently does not build, it should be:
pkgname=teamviewer
and not
pkgname=teamviewer8-beta
And after fixing that, the service does not seem to be getting installed.
$ sudo teamviewer --daemon start
systemctl start teamviewerd.service
Failed to issue method call: Unit teamviewerd.service failed to load: No such file or directory. See system logs and 'systemctl status teamviewerd.service' for details.
fail
$ sudo systemctl status teamviewerd
teamviewerd.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
commented on 2012-12-15 09:00 (UTC)
When trying to launch teamviewer it will complain: "TeamViewer Daemon is not running, Please start teamviewerd and then restart TeamViewer."
Use: 'teamviewer --daemon enable' to enmable the daemon in systemd
Use: 'teamviewer --daemon start' to start the daemon in systemd
And you're good to go.
Source: http://ubuntuforums.org/showthread.php?t=2092298
max.bra commented on 2012-12-13 08:42 (UTC)
the real problem is not stable or beta!
download pages for other systems except linux offers version 8.x as unique download link available. sooner or later in these days, 7.x linux client will not more be able to connect with others (like me yesterday). at least this will happens with occasional remote controlled customers.
russo79 commented on 2012-12-11 17:15 (UTC)
@Raymondcal
If you go to the linux downloads page[1], you will see that the version 8 provided for linux is still a beta one.
[1] http://www.teamviewer.com/en/download/linux.aspx
Raymondcal commented on 2012-12-11 17:03 (UTC)
@all :
Where have you read that version 8 is a beta version ? On the official website, they present this 8 version as as whole stable one…
@vwyodajl :
yaourt -R teamviewer
yaourt -S teamviewer
et voilà, your version 8 is here, without any problem. Not a sorcery and no need to downgrade to version 7.
And I have had no problem with the systemd service either… Systemd is now the ONLY official service manager for ArchLinux…
So, I would be very glad to see version 8 coming back ! :)
donny commented on 2012-12-08 15:26 (UTC)
dluciv:
> Having no running systemd, what can one do with it?
You should switch to systemd soon. Packages maintainers are going to start removing all initscripts parts from packages by january.
Read this: https://www.archlinux.org/news/end-of-initscripts-support/
Hilinus commented on 2012-12-07 10:27 (UTC)
You're right. I should create a teamviewer-beta package and push the testing version there: I have reuploaded the PKGBUILD for the stable version.
As always thanks for your feedback.
dluciv commented on 2012-12-07 07:07 (UTC)
Version 8 requires its daemon to be started.
In fact, daemon depends on either systemd or debian-like initV.
Having no running systemd, what can one do with it?
vwyodajl commented on 2012-12-06 20:17 (UTC)
@Hilinus I also do not get why you pushed a beta version on this. This should only be using the "stable" versions of teamviewer. If you want a "beta" version I think a new PKGBUILD would be more appropriate.
Can you roll this back to the stable version and wait until 8 is stable. I also have to second with this many votes on the package beta should be avoided.
Now on to issues:
I can not even install the new version.
(1/1) checking package integrity [---------------------] 100%
(1/1) loading package files [---------------------] 100%
(1/1) checking for file conflicts [---------------------] 100%
error: failed to commit transaction (conflicting files)
teamviewer: /opt/teamviewer exists in filesystem
Errors occurred, no packages were upgraded.
local database is up to date
I could force it to install but alas that is a dirty fix.
I vote roll this to stable and keep it only on stable.
roentgen commented on 2012-12-06 18:42 (UTC)
@Hilinus as a maintainer maybe you should check more throughly before pushing a beta beta version which clearly has some problems.
After all this has ~800 votes which probably means that people care to have it working.
Hilinus commented on 2012-12-06 18:29 (UTC)
I upgraded the PKGBUILD to install the new beta version. Please report any problems here.
Please be sure to read the installation note.
innn commented on 2012-12-06 18:06 (UTC)
please update this, I've managed to install by changing 7 with 8 all's fine but complains about a daemon teamviewerd not started and I don't know where to get that also.
eworm commented on 2012-12-04 19:04 (UTC)
Can we please wait with the update until version 8 is final for Linux? Thanks!
(Would be great to get a new package teamviewer-beta for testing purposes, though.)
ryley commented on 2012-11-07 11:23 (UTC)
Yeah, I have chrome installed. I probably should've looked closer at the file path... Still not sure why I repeatedly got the error when only trying to upgrade teamviewer, but whatever lol. Thanks for pointing that out and keeping the package up to date!
Hilinus commented on 2012-11-06 22:41 (UTC)
I don't think that is related to Teamviewer... Do you have Google Chrome installed?
ryley commented on 2012-11-06 01:33 (UTC)
Upgrading teamviewer to latest version on 32bit arch, I get the error "strip:./opt/google/chrome/nacl_irt_x86_64.nexe: File format not recognized" when yaourt is building the package. Can anyone recommend a fix?
Hilinus commented on 2012-10-31 17:15 (UTC)
Done.
scarecrow commented on 2012-10-31 06:56 (UTC)
New version released, please update:
pkgname=teamviewer
pkgver=7.0.9377
pkgrel=1
pkgdesc="All-in-one solution for accessing PC's using the internet"
arch=('i686' 'x86_64')
url="http://www.teamviewer.com"
license="nonfree"
makedepends=('binutils')
if [ $CARCH == 'i686' ]; then
source=("teamviewer_linux-${pkgver}.deb::http://www.teamviewer.com/download/version_7x/teamviewer_linux.deb" "teamviewer.desktop")
md5sums=('ab13157b1f68234e1887332cda93786a' 'b282ecbb72ff3cf82979defd8fc5a0c5')
depends=('libsm' 'libxext' 'freetype2' 'libxtst')
elif [ $CARCH == 'x86_64' ]; then
source=("teamviewer_linux_x64-${pkgver}.deb::http://www.teamviewer.com/download/version_7x/teamviewer_linux_x64.deb" "teamviewer.desktop")
md5sums=('bb63d2bd4879fc8956b754b227402a66' 'b282ecbb72ff3cf82979defd8fc5a0c5')
depends=('lib32-libsm' 'lib32-libxext' 'lib32-glibc' 'lib32-freetype2' 'lib32-gcc-libs' \
'lib32-alsa-lib' 'lib32-libx11' 'lib32-libxtst' 'lib32-libxdamage' 'lib32-libxfixes' \
'lib32-libxcb' 'lib32-libxi' 'lib32-libxau' 'lib32-libxdmcp')
fi
package() {
cd $srcdir
[ $CARCH == "i686" ] && ar x ${pkgname}_linux-${pkgver}*
[ $CARCH == "x86_64" ] && ar x ${pkgname}_linux_x64-${pkgver}*
tar xvf data.tar.gz
cp -R opt $pkgdir
cp -R usr $pkgdir
mkdir -p $pkgdir/usr/share/applications
install -Dm644 $startdir/teamviewer.desktop $pkgdir/usr/share/applications/teamviewer.desktop
}
roentgen commented on 2012-10-06 07:00 (UTC)
@ crichton
lib32-alsa-lib is in [multilib] repo which is necessary for x64 installs.
commented on 2012-10-04 21:53 (UTC)
Hmm, I have a problem with the dependency lib32-alsa-lib, the package doesn't seem to exist, or it can't be found by pacman (I see it in the package database)? Tried switching my mirror, but that didn't either.
Hilinus commented on 2012-10-01 16:51 (UTC)
You should download the entire tarball, not only the PKGBUILD:
https://aur.archlinux.org/packages/te/teamviewer/teamviewer.tar.gz
Next time click on "Archive" next to the "PKGBUILD" link, as you may miss important files contained in the SOURCE array of the PKGBUILD, such as the .desktop file in this case.
commented on 2012-09-23 14:30 (UTC)
download PKGBUILD, makepkg -s as non-root user, yields this result:
==> ERROR: teamviewer.desktop was not found in the build directory and is not a URL.
Hilinus commented on 2012-09-17 16:28 (UTC)
This version isn't supposed to be run with another version wine than the one it comes packaged with, I suppose.
ValdikSS commented on 2012-09-17 09:50 (UTC)
Not working with the latest wine.
Hilinus commented on 2012-07-20 12:24 (UTC)
Updated.
commented on 2012-07-20 12:06 (UTC)
Current checksums:
7ccea6a656c196eacd028774e0811fe3 teamviewer_linux.deb
00d08807be74cc88c12d280be3720d0b teamviewer_linux_x64.deb
commented on 2012-07-18 14:47 (UTC)
Validating md5 sum of teamviewer_linux_x64-7.0.9350.deb fails.
skuda commented on 2012-06-08 16:21 (UTC)
I get a wine fail with teamviewer_desktop.exe when i try to share my screen in a meeting, do meeting works for someone?
Hilinus commented on 2012-06-03 19:05 (UTC)
Fixed, thanks.
commented on 2012-06-03 14:36 (UTC)
The i686 checksum has to be changed with:
0af22c7d12f1559c9def98d2a572334f
eworm commented on 2012-06-03 10:36 (UTC)
Looks like checksum for i686 fails...
Hilinus commented on 2012-06-03 07:05 (UTC)
Upgraded. Sorry for the delay.
jose1711 commented on 2012-05-28 18:19 (UTC)
@tlm: why don't you write at aur-general list so that they will reassign the pkgbuild to you? jose
dserban commented on 2012-04-25 09:33 (UTC)
Version 7 definitely crashes more often than version 6 did.
jose1711 commented on 2012-04-25 09:29 (UTC)
> This package it's not working for me...
could you be a little more specific what was not working?
commented on 2012-04-25 09:25 (UTC)
This package it's not working for me... i tried to search with google something else about the resolution of this problem, but nothing to do.
My answer for this problem is:
1) Download the Windows Version of teamviewer
2) Install this with the local wine.
3) Enjoy teamviewer...
zeld
fhtagn commented on 2012-04-03 12:53 (UTC)
Works fine now.
Meanwhile, I used http://www.teamviewer.com/download/teamviewer_linux.tar.gz
However, it is nice being able to manage the installation with packer/manager of choice.
Thank you
Hilinus commented on 2012-03-30 16:50 (UTC)
Upgraded.
fhtagn commented on 2012-03-29 22:33 (UTC)
==> Validating source files with md5sums...
teamviewer_linux.deb ... FAILED
teamviewer.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
The build failed.
=/
MorningWood commented on 2012-03-15 18:39 (UTC)
I am having the most annoying bug with Teamviewer (both AUR releases). Whenever I connect to my Arch install it kicks the screensaver on literally every 2 seconds. Anyone else experiencing this? How do I fix it? I've even turned the screensaver off and no go.
Hilinus commented on 2012-02-03 19:30 (UTC)
That's NOT a bug. The linux version of Teamviewer, is actually the Windows version that runs under an embedded version of Wine, which is provided as a 32bit executable and therefore needs 32bit libs. As for the dependencies, it's assumed that, as a 64bit user, you have enabled the [multilib] repo.
timofonic commented on 2012-02-02 22:02 (UTC)
Dependency `lib32-alsa-lib' of `teamviewer' does not exist.
timofonic commented on 2012-02-02 22:01 (UTC)
There's a bug: it asks me 32bit libraries in a 64bit environment. There's a 64bit version of teamviewer...
Hilinus commented on 2012-01-26 18:52 (UTC)
Done!
eworm commented on 2012-01-26 12:30 (UTC)
Can you please change the source to
source=("teamviewer_linux-${pkgver}.deb::http://www.teamviewer.com/download/version_7x/teamviewer_linux.deb" "teamviewer.desktop")
and
source=("teamviewer_linux_x64-${pkgver}.deb::http://www.teamviewer.com/download/version_7x/teamviewer_linux_x64.deb" "teamviewer.desktop")
This way makepkg does not fail if an older version is in the cache directory. Thanks!
ottoshmidt commented on 2012-01-25 23:11 (UTC)
confirmed here as well.
artemklevtsov commented on 2012-01-25 18:03 (UTC)
I confirm that new version solved a problem with appearance of window.
Hilinus commented on 2012-01-25 17:38 (UTC)
Upgraded.
@ All of those having problems:
Try this version and report back.
commented on 2012-01-24 20:57 (UTC)
> When connection established from Archlinux to Windows, the window of remote desktop is created, but it can not be shown/opened.
It's the same for me, only that I tried to connect from Arch to a Mac. I use KDE as Desktop environment. Don't know if it's a KDE issue or wine issue... No error message when starting from terminal.
commented on 2012-01-18 23:19 (UTC)
@geraldoav: Works great for me (7.0.238 on Samsung Galaxy Nexus)...
geraldoav commented on 2012-01-16 11:18 (UTC)
Team Viewer for Android doesn't work with this package (because its in beta). It used to work with Team Viewer 6. Can you make a package with Team Viewer 6?
artemklevtsov commented on 2012-01-13 15:05 (UTC)
> When connection established from Archlinux to Windows, the window of remote desktop is created, but it can not be shown/opened.
Same here.
commented on 2012-01-02 12:00 (UTC)
Yea i was able to and it works fine. Just one feature i dont know how to do. Is it possible to close teamviewer in try at arch?
max-k commented on 2012-01-02 10:19 (UTC)
Hi, can you create a package withe temviewer 6 ?
commented on 2011-12-31 20:11 (UTC)
When connection established from Archlinux to Windows, the window of remote desktop is created, but it can not be shown/opened.
Teamviewer 7 on both systems.
Opposite direction works fine.
Suggestions?
ernetas commented on 2011-12-28 13:18 (UTC)
Because Teamviewer 6 can only be used with Teamviewer <=6.
eworm commented on 2011-12-27 12:21 (UTC)
Version 7 is still beta... Why don't you keep version 6 until the new one is released finally?
BTW, there's a package teamviewer-beta in AUR.
Hilinus commented on 2011-12-26 12:54 (UTC)
Fixed.
s.pantaleev commented on 2011-12-26 09:55 (UTC)
The .desktop file needs some changes after the upgrade to version 7.
-Exec=/opt/teamviewer/teamviewer/6/bin/teamviewer
-Icon=/opt/teamviewer/teamviewer/6/desktop/teamviewer.png
+Exec=/opt/teamviewer/teamviewer/7/bin/teamviewer
+Icon=/opt/teamviewer/teamviewer/7/desktop/teamviewer.png
Hilinus commented on 2011-12-26 08:56 (UTC)
Mmh... don't know how to fix those errors easily. If teamviewer was packaged differently, things could be worked out, but as it is, it's only a mere windows version running on a builtin version of wine, which, of course, uses its libraries but outside of a secure PATH (they are in /opt).
Don't know how serious this issue can be. Please refer to:
https://wiki.archlinux.org/index.php/Namcap
https://bugs.archlinux.org/14049
rwd2 commented on 2011-12-25 18:31 (UTC)
Not sure how important these are, but namcap shows lots of errors:
teamviewer E: Insecure RPATH '/lib32' in file ('opt/teamviewer/teamviewer/7/wine/drive_c/Program Files/TeamViewer/Version7/tvwine.dll.so')
teamviewer W: Dependency 'sh' on your system is a testing release
teamviewer E: ELF file ('opt/teamviewer/teamviewer/7/wine/lib/libwine.so.1.0') outside of a valid path.
teamviewer E: ELF file ('opt/teamviewer/teamviewer/7/wine/lib/wine/comdlg32.dll.so') outside of a valid path.
teamviewer E: ELF file ('opt/teamviewer/teamviewer/7/wine/lib/wine/ole32.dll.so') outside of a valid path.
(etc)
Hilinus commented on 2011-12-25 18:25 (UTC)
Upgraded.
arriagga commented on 2011-12-24 00:36 (UTC)
here the modified PKGBUILD for version 7.0.9300 (BETA):
http://pastebin.com/J0CMzKAZ
Burning_aces commented on 2011-12-20 16:24 (UTC)
There is a beta out.
Just change the link in the package build from "http://www.teamviewer.com/download/teamviewer_linux_x64.deb" to "http://www.teamviewer.com/download/version_7x/teamviewer_linux_x64.deb" for x64
For x32 "http://www.teamviewer.com/download/teamviewer_linux.deb" to "http://www.teamviewer.com/download/version_7x/teamviewer_linux.deb"
Simple.
Currently installing the beta now..
jose1711 commented on 2011-12-20 08:49 (UTC)
@anpieber: for windows only, however
anpieber commented on 2011-12-20 07:20 (UTC)
teamviewer7 had been released
Hilinus commented on 2011-12-01 17:18 (UTC)
Has this been flagged out of date because version 7 is out? It's windows only, AFAIK. Release date for linux version is due to Q1 2012, according to teamviewer website.
http://www.teamviewer.com/en/download/currentversion.aspx#note
commented on 2011-10-27 07:59 (UTC)
I installed it, works fine, but I didn't like that is over wine libs, but it has also a web version, that works ok. Maybe some of you wanna try web version first.
dserban commented on 2011-07-29 20:45 (UTC)
The issue I experienced may have had more to do with some instability in Nvidia's binary drivers than with TeamViewer. I don't know for sure.
deimos commented on 2011-07-29 19:44 (UTC)
I had delayed upgrading based on dserban's comment, but after using the latest version, I have experienced no "nastyware" issues. After upgrading there is a EULA prompt. The banner popup that I am used to appearing at the end of every session has only appeared once, so I can immediately reconnect to close the dialog box and disconnect without triggering another one. I also have not encountered any time limits.
dserban commented on 2011-07-15 14:05 (UTC)
TeamViewer has become nastyware.
I just ran a session and observed the nasty behavior.
At the end of the session, there is a popup on the viewer's side with a question if you want to buy a license. If you answer "No", the target computer's screen locks up (stops responding to mouse and keyboard) and the only way out is a hard reset.
Rest in peace, TeamViewer for Linux.
artemklevtsov commented on 2011-07-14 19:38 (UTC)
lib32-libxau > lib32-glibc
lib32-libxdamage > lib32-libxfixes
lib32-libxdmcp > lib32-libxcb > lib32-x11
lib32-libxtst > lib32-libxi, lib32-libxext
">" = require. therefore lib32-libxext, lib32-libxi, lib32-libxfixes, lib32-glibc, lib32-libx11 doesn't need any more in the depends array. You can test the resulting package with namcap and you get the same thing.
jose1711 commented on 2011-07-11 05:15 (UTC)
@zyghom: so we should better stick to 6.0.9224?
zyghom commented on 2011-07-08 22:04 (UTC)
free time with teaviewer finished - new version limits every connection :-(
Hilinus commented on 2011-07-08 17:41 (UTC)
Allright!
dpflug commented on 2011-07-08 13:46 (UTC)
Version 6.0.9258 is out. Just needs an md5sum change.
Hilinus commented on 2011-06-07 16:53 (UTC)
I have set the permission explicitly, as you requested. Please test the package and tell me if it works.
rwd2 commented on 2011-06-04 08:16 (UTC)
the permissions now depend on which umask root has. It is better to set the permissions explicitly so the result is always the same.
corvolino commented on 2011-04-15 20:55 (UTC)
indeed, teamviewer.desktop is grayed out for me too in this page, but it works normally while downloaded... strange. [2] :/
Hilinus commented on 2011-04-14 10:07 (UTC)
That file was already with 644 permissions on my system.
rwd2 commented on 2011-04-14 07:37 (UTC)
The menu-item is not visible because /usr/share/applications/teamviewer.desktop has the wrong permissions. Fixed with: sudo chmod 644 /usr/share/applications/teamviewer.desktop
Hilinus commented on 2011-04-02 07:27 (UTC)
Indeed, teamviewer.desktop is grayed out for me too in this page, but it works normally while downloaded... strange.
skunkie commented on 2011-04-01 15:50 (UTC)
Hey,
just installed yaourt and it worked fine with yaourt, no idea why makepkg isn't working with me. Is the teamviewer.desktop under Sources on this page also grayed out for you? I do not remember files being like that, more like blue (link) like the deb package. It's been a while since I have been to AUR.
Hilinus commented on 2011-04-01 15:07 (UTC)
Strange... I tried downloading the archive both manually and with yaourt, and the .desktop file is there...
skunkie commented on 2011-04-01 10:17 (UTC)
Hey guys!
I'm getting this error:
==> ERROR: teamviewer.desktop was not found in the build directory and is not a URL.
I'm running wmii so does i have to do with that or is it the fact that I cannot download this file from the Sources?
Any help appreciated!
MOhz
Hilinus commented on 2011-02-10 21:35 (UTC)
Uhm, md5 for the x64 deb is still the same... Maybe your file is corrupt.
[hilinus@archie ~]$ md5sum teamviewer_linux_x64.deb
40167ebe6f3e348928a7e28c941ccda1 teamviewer_linux_x64.deb
mkoskar commented on 2011-02-09 15:41 (UTC)
==> Validating source files with md5sums...
teamviewer_linux_x64.deb ... FAILED
teamviewer.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build teamviewer.
Still 6.0.9224 but new build ?
commented on 2010-12-14 21:37 (UTC)
@Bevan doh, thanks! :)
Bevan commented on 2010-12-14 21:36 (UTC)
@ zhobbs: You have to enable "multilib" respository in /etc/pacman.conf:
[multilib]
Include = /etc/pacman.d/mirrorlist
commented on 2010-12-14 21:27 (UTC)
Fails here (x86_64): this dep doesn't exist: lib32-libxtst
Hilinus commented on 2010-12-02 09:24 (UTC)
fixed. Thanks for the suggestion.
commented on 2010-12-01 22:53 (UTC)
please update the desktop file to point to new file location ./opt/teamviewer/teamviewer/6/bin/teamviewer or ./usr/bin/teamviewer6
commented on 2010-12-01 22:50 (UTC)
please update the desktop file to point to new file location ./opt/teamviewer/teamviewer/6/bin/teamviewer or ./usr/bin/teamviewer6
Hilinus commented on 2010-12-01 21:07 (UTC)
Upgraded =)
Janhouse commented on 2010-12-01 16:32 (UTC)
PKGBUILD for version 6 http://pastebin.com/raw.php?i=4cJuNHBL
coolpyrofreak commented on 2010-12-01 12:03 (UTC)
Linux version has been updated to 6.0.9224.
Hilinus commented on 2010-11-21 19:15 (UTC)
Yes, but i would like to stick to their pseudo linux version.
oliparcol commented on 2010-11-19 19:43 (UTC)
It's because the windows version is more recent I suppose...
Hilinus commented on 2010-11-17 19:54 (UTC)
Mmh? Why outdated?
Hilinus commented on 2010-09-29 10:36 (UTC)
It should be fine now.
ivenvd commented on 2010-09-29 06:15 (UTC)
Seems wrong md5sum of teamviewer_linux_x64.deb ?
Hilinus commented on 2010-09-28 18:36 (UTC)
Added. Thanks =)
xduugu commented on 2010-09-28 13:41 (UTC)
libxtst dependency is missing on i686.
mikes commented on 2010-09-13 05:26 (UTC)
i finaly disabled the if/fi section refering to multilib and everything is ok..
mikes commented on 2010-09-13 03:35 (UTC)
This package, since the last change is the only package i am unable to upgrade via yaourt. I also tried to build the package with makepkg but it seems that the new warning causes a problem and it stops. Although i have multilib repo enabled it keeps warning me to add it in /etc/pacman.conf. Anyone else having the same problem?
Hilinus commented on 2010-09-11 08:03 (UTC)
Added annoying reminder to make users add the [multilib] repo before installing on x86_64.
coolpyrofreak commented on 2010-09-10 20:11 (UTC)
@irpye: You need to enable the multilib repository in pacman.conf. Most of the lib32 and bin32 packages are now in that repo.
irpye commented on 2010-09-10 20:10 (UTC)
I tried to update teamviewer from AUR. I am on x86_64.
I have this message :
Erreur: 'lib32-alsa-lib': impossible de trouver ou de lire le paquet
(error : 'lib32-alsa-lib': impossible to find or read the package)
lib32-alsa-lib is listed in the dependancies, but i can not find it in AUR
What should i do ? Thanks.
commented on 2010-09-10 03:44 (UTC)
Installing lib32-libxtst solved problems in Arch amd64 :D
Bevan commented on 2010-09-07 21:34 (UTC)
lib32-libxtst is included in official multilib repository. See: http://www.archlinux.org/news/508/
petRUShka commented on 2010-09-07 19:23 (UTC)
I can't find lib32-libxtst in AUR:
"error: 'lib32-libxtst': could not find or read package"
And so I can't build teamviewer.
If I try to use previous version of PKGBUILD, I get an error with tvwine.dll.so...
Bevan commented on 2010-09-07 14:39 (UTC)
Works for me now! :-)
The only package that I didn't have installed before is lib32-libxtst.
@MASSER: Can you confirm that installing lib32-libxtst solves the problem?
Hilinus commented on 2010-09-07 14:06 (UTC)
Updated dependencies to include additional 32bit X libs. Let me know if it doesn't work.
Bevan commented on 2010-09-07 10:48 (UTC)
ldd /opt/teamviewer/teamviewer/5/wine/drive_c/Program\ Files/TeamViewer/Version5/tvwine.dll.so
not a dynamic executable
Hilinus commented on 2010-09-07 10:40 (UTC)
@All of you having problems: Could you paste the result of
ldd /opt/teamviewer/teamviewer/5/wine/drive_c/Program Files/TeamViewer/Version5/tvwine.dll.so
Here, on i686, it doesn't find only libwine.so.1, but it works.
@Bevan: the alsa-lib thing appears probably because lib32-alsa-lib doesn't appear as a dependency in the PKGBUILD. I've updated that now.
Bevan commented on 2010-09-07 09:37 (UTC)
I forgot to mention that I use x86_64 - seems to be important here. Namcap told me the following about the package:
teamviewer E: Dependency detected and not included (lib32-alsa-lib) from files ['opt/teamviewer/teamviewer/5/wine/lib/wine/winealsa.drv.so']
teamviewer W: Referenced library 'libwine.so.1' is an uninstalled dependency
But installing lib32-alsa-lib and wine doesn't solve the problem.
coolpyrofreak commented on 2010-09-07 05:22 (UTC)
I can't confirm any problems on x86_64. Works great over here.
masser commented on 2010-09-07 05:21 (UTC)
I confirm on amd64 platform is the same problem as with Beavan. On x86, everything works fine.
Bevan commented on 2010-09-06 20:22 (UTC)
Unfortunately the new version does not work for me. It fails during startup with "Could not load the GNU/Linux extension shared library tvwine.dll.so."
I don't know what the problem could be. The file can be found here: /opt/teamviewer/teamviewer/5/wine/drive_c/Program Files/TeamViewer/Version5
I already tried to remove my ~/.teamviewer folder but with no success.
Hilinus commented on 2010-09-06 19:11 (UTC)
They have released a new version, updated PKGBUILD.
bakerboy commented on 2010-09-06 16:25 (UTC)
Teamviewer seems to be failing to validate as of today, any ways round it?
Hilinus commented on 2010-08-30 20:54 (UTC)
Yes, please read last news about the [multilib] repo :)
Bevan commented on 2010-08-28 06:18 (UTC)
Seems like they have changed it again. Please ignore my last comment.
Bevan commented on 2010-08-27 00:24 (UTC)
Hi!
On x86_64 this package depends on lib32-gcc-libs. I think this package has been replaced by gcc-libs-multilib. lib32-gcc-libs is not available anymore. Could you please change the PKGBUILD?
Thanks for this package!
Michael
coolpyrofreak commented on 2010-08-25 22:26 (UTC)
My girlfriend uses Fedora, and Teamviewer works great from my Arch system to her Fedora computer, so I don't think it's from an incompatibility with X. Sounds more like the person walked away from their system and logged out or locked the screen without telling you.
Alain2 commented on 2010-08-25 21:01 (UTC)
Hi, just for my unbderstanding, this works only to control a windows machine or should it work between 2 arch computers ? I have the error "The connection was closed, because your partner's desktop was currently not available. This is probably due to fast user switching or a disconnected remote desktop session or the screen was simply locked." so I guess it's because it doesn't like to display an X session ?
Thanks
commented on 2010-08-25 14:06 (UTC)
Thanks for this great package - great work
Hilinus commented on 2010-06-02 08:48 (UTC)
How are you trying to use the PKBUILD? Download all the files required for the build, put them in a folder and then issue makepkg.
Or you can just use yaourt -S teamviwer.
commented on 2010-06-01 15:04 (UTC)
./PKGBUILD: line 10: [: ==: unary operator expected
./PKGBUILD: line 13: [: ==: unary operator expected
What is it?
commented on 2010-05-03 15:52 (UTC)
doesnt work on my system. :( nobody is able to connect
V3n3RiX commented on 2010-04-27 17:46 (UTC)
Thanks
Hilinus commented on 2010-04-23 08:25 (UTC)
Updated.
commented on 2010-04-23 02:11 (UTC)
32 bit does too, de966eeb243385e857a73a99613e2a72
commented on 2010-04-22 19:54 (UTC)
Seems 64 bits deb package has a new md5sum : 0612cb7b5d452d72ad94b930f87822d1
Hilinus commented on 2010-04-17 07:32 (UTC)
Corrected. Thanks!
msquared commented on 2010-04-17 07:24 (UTC)
There is a dependency bug for i686. Since the i686-versions should not rely on lib32-***.
You should try something like this:
[ $CARCH == 'x86_64' ] && depends=('lib32-libsm' 'lib32-libxext' 'lib32-glibc' 'lib32-freetype2' 'lib32-gcc-libs')
[ $CARCH == 'i686' ] && depends=('libsm' 'libxext' 'freetype2')
I stripped off glibc and gcc-libs for i686 since they are part of the base installation.
Regards, Matthias
commented on 2010-04-16 14:17 (UTC)
It's a redundant release. wine emulated release? no thanks.
Teamviewer should treat their Linux users like they do their Mac users. They got a native app. Heck, the iPhone has a native app.
commented on 2010-04-16 10:28 (UTC)
you should correct the second line of the build function. it should look like this:
ar x ${pkgname}_linux*
Hilinus commented on 2010-04-16 08:04 (UTC)
Added launcher.
Hilinus commented on 2010-04-16 07:52 (UTC)
Yes, but it is not native: if you see in /opt, it uses an embedded version of wine.
guisacouto commented on 2010-04-15 18:12 (UTC)
great app! never thought they were going to make a linux version..
tks!
Hilinus commented on 2010-04-15 10:30 (UTC)
First release.
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.