Package Details: teamviewer-beta 15.31.5-1

Git Clone URL: https://aur.archlinux.org/teamviewer-beta.git (read-only, click to copy)
Package Base: teamviewer-beta
Description: All-In-One Software for Remote Support and Online Meetings
Upstream URL: https://www.teamviewer.com/en-us/download/linux/
Licenses: custom
Conflicts: teamviewer
Provides: teamviewer
Submitter: eworm
Maintainer: SimPilotAdamT
Last Packager: SimPilotAdamT
Votes: 71
Popularity: 0.23
First Submitted: 2015-11-17 13:22 (UTC)
Last Updated: 2022-07-09 22:31 (UTC)

Latest Comments

severach commented on 2022-06-06 15:23 (UTC)

See mailing lists aur-requests. Deletion request filed by kalipus, not me.

SimPilotAdamT commented on 2022-06-06 13:28 (UTC)

@MarsSeed email sent, we'll see how it goes...

MarsSeed commented on 2022-06-06 13:24 (UTC)

@SimPilotAdamT, I believe @severach, the former maintainer of this package has submitted a deletion request for it.

You can reply to that on some mailing list if you want to let your voice heard that you want to keep this package. (Unfortunately I am not yet subscribed so I cannot help you with that as of now.)

Though bear in mind that if a Trusted User goes through with the deletion of this package, you can immediately recreate it by pushing a new commit to the same AUR git repo as you did just now. Only the votes and the comments will be lost but the package will live.

MarsSeed commented on 2022-05-12 13:11 (UTC)

@CyberShadow right, I'm sorry for the unintended spam ´:-)

CyberShadow commented on 2022-05-12 13:08 (UTC)

MarsSeed, there is an edit button on the right. We still get one email each time you repost your comment.

MarsSeed commented on 2022-05-12 13:07 (UTC)

It seems there are no more public beta downloads available from TeamViewer website, only via the installed public version of the application:

https://community.teamviewer.com/English/kb/articles/4086-teamviewer-insider-builds

Information about preview (beta) releases are only available after logging in with an account:

https://community.teamviewer.com/English/categories/insider-builds-channel

freebench commented on 2022-01-21 02:50 (UTC)

recently refused to work. forced to sign up for a free account. even after sign up it didn't work - Unknown error on connection attempt. had to switch to https://aur.archlinux.org/pkgbase/teamviewer/. It could be that I didn't activate it after signing up.

CyberShadow commented on 2019-08-25 22:38 (UTC)

It is created again on the next boot, just like it was created the first time on the first boot.

It is created with a different value, no? So, software which depends on the value being consistent on the same machine will be affected.

CyberShadow commented on 2019-08-25 22:37 (UTC)

You're talking Windows Uninstaller talk. Removing a package should restore the system to as close to the clean original as possible.

What makes you say that?

Can you provide some examples of core Arch Linux packages which delete files created by the packaged software during uninstallation?

severach commented on 2019-08-25 22:35 (UTC) (edited on 2019-08-25 22:39 (UTC) by severach)

You're talking Windows Uninstaller talk. Removing a package should restore the system to as close to the clean original as possible. All deleted files are TeamViewer files of which the user has no interest. TeamViewer removal leaves a lot of junk files around. I notify the user to they can delete them. I can take the rm off.

You should definitely not be deleting a systemd file just because TeamViewer happens to read it.

"You" the package isn't deleting it. It is completely safe for "You" the user to delete it. It is created again on the next boot, just like it was created the first time on the first boot.

CyberShadow commented on 2019-08-25 18:17 (UTC)

I can delete anything that Teamviewer creates in system folders.

I don't think packages should do anything of the sort, unless the files are created during installation. Uninstalling and reinstalling a package should have no net effect on the system. The only exception are configuration files, as indicated by the backup=(...) array in PKGBUILD files, and when pacman -R is invoked also with -n.

tmpfiles.d allows declaring a list of files and directories created by programs at runtime, including log directories, if that's what you're looking for.

Google TeamViewer Linux "machine-id" to see what it has to do with TeamViewer.

You should definitely not be deleting a systemd file just because TeamViewer happens to read it. It will affect much more than just TeamViewer. If you are going to advise your package's users to delete it, at least add a warning that it may have significant consequences.

I can show you what to clean up to fully remove the package.

I think that's a good idea, but it should probably come with some explanation comments.

severach commented on 2019-08-25 17:58 (UTC)

I was in a hurry to get something that worked. I'll switch to getting home dirs from getent. I can delete anything that Teamviewer creates in system folders. A package can't remove stuff from user dirs. I can show you what to clean up to fully remove the package. Google TeamViewer Linux "machine-id" to see what it has to do with TeamViewer.

CyberShadow commented on 2019-08-25 01:34 (UTC)

Hi, what is with the post_remove hook added in the last "autu" commit? Why is it globbing /home/* instead of using the user database? Why does it remove some things, but only prints commands to remove other things? And how is /etc/machine-id related at all here, considering it's a systemd file and has nothing to do with Teamviewer?

severach commented on 2018-11-11 21:08 (UTC)

A message to enable the server is output if it's not already enabled. Do you want a separate message for only temporarily enabling?

CyberShadow commented on 2018-11-11 17:45 (UTC) (edited on 2018-11-11 19:12 (UTC) by CyberShadow)

which they probably rarely have to do when most other services all are enabled and started by default

Please name some services for network software (which listens on all interfaces) packaged in Arch Linux that are automatically configured to start upon installation. I'm not aware of any.

(Someone else please correct me if I'm wrong.)

You can do both actions in one command using:

sudo systemctl enable --now teamviewerd

but I dnon't think it's obvious that if someone knows how to run 'yaourt -S', which they do hundreds of times, that they would know how to start a service

IMHO, Arch Linux is not the best Linux distribution for those users.

wjhk23 commented on 2018-11-11 17:38 (UTC) (edited on 2018-11-11 17:38 (UTC) by wjhk23)

How about just some output after the install (from the command line at least) which shows the next steps for enabling the server (for those who want it). Although it appears that it's not hard to enable the service, but I dnon't think it's obvious that if someone knows how to run 'yaourt -S', which they do hundreds of times, that they would know how to start a service, which they probably rarely have to do when most other services all are enabled and started by default, without googling (which is easy, but just stating the commands would save time and be easier). For those who came here first expecting a bug than googling how to start (like me), the commands you need are:

sudo systemctl start teamviewerd

sudo systemctl enable teamviewerd

(Someone else please correct me if I'm wrong.)

CyberShadow commented on 2018-10-18 06:00 (UTC)

All my tests show that the client doesn't run without the server running.

If that's true, that must be new - I've definitely used the client before without having to run any server.

severach commented on 2018-10-18 05:58 (UTC)

I disabled autostart. All my tests show that the client doesn't run without the server running.

CyberShadow commented on 2018-10-18 03:58 (UTC)

"not autostarting TeamViewer makes remote support impossible"

What does that mean? Presumably, if you can install a package from AUR, you can enable/start TeamViewer, right?

Auto-starting proprietary code, with a history of vulnerabilities, which runs unsandboxed... seems like a pretty bad idea.

As I understand, this package includes both the client and server, and many people (incl. myself) won't need the server component at all, nor do they want it running at any time.

maximbaz commented on 2018-10-17 18:19 (UTC)

This is a weird argument, if a person doesn't want to learn how to start systemd services or even how to copy-paste the command from post_install notice, maybe they shouldn't be using Arch Linux in the first place.

severach commented on 2018-10-17 16:47 (UTC)

Supporting you is easy. I can be sure that you'll get the 40 character command right. I want a teamviewer package with which I could remote support your mom. Part of Arch best practice is knowing when not to follow it. I can make a separate package if you like.

anonfunc commented on 2018-10-17 08:59 (UTC)

I strongly disagree with the decision to auto-enable teamviewerd.service in .install, Arch best-practise is to not enable services with install, even if they are needed to run/are the installed program.

Louis commented on 2018-09-02 20:44 (UTC)

I've decided to disown this package because the teamviewer aur package has been upgraded to version 13. If anyone wants to maintain this package please do so.

joelostblom commented on 2018-04-04 12:26 (UTC)

Regarding using teamviewer without a display manager, I just received a reply from one of the teamviewer developers (in the forum thread I linked previously):

"it will not happen this year. However, a part of TeamViewer is currently rewritten that will make it simpler to implement it in the future."

joelostblom commented on 2018-04-02 03:58 (UTC)

I am experiencing the same issue as several others here, I can't start TV without launching X via a display manager. There are several threads about this on the TV community forum, e.g. https://community.teamviewer.com/t5/Linux/uninstalled-tar-package-running-without-display-manager/m-p/26866, but no solution available so far.

FabioLolix commented on 2018-03-31 23:08 (UTC)

There is a duplicate of this package https://aur.archlinux.org/packages/teamviewer13/

DoesntLikeSand commented on 2018-03-14 21:50 (UTC) (edited on 2018-03-14 21:51 (UTC) by DoesntLikeSand)

@JJK I was having the exact same problem. I solved it by installing lightdm, lightdm-greeter-gtk, and lightdm-greeter-gtk-settings; sudo systemctl enable lightdm. Once I rebooted and logged in, TeamViewer GUI launched successfully for the first time and now I have everything up and running. I'm using XFCE fwiw. Hope this helps, sorry if it doesn't.

Tldr: install a greeter and reboot

francoism90 commented on 2018-03-12 16:10 (UTC)

Bit of an odd question, but could we add a patch to remove the NetworkManager-wait-online.target in After of the systemd service?

It's not needed/wanted, when running systemd-networkd and it should work fine with NetworkManager-wait-online.target` as well. But maybe someone can confirm this first.

JJK commented on 2018-03-06 10:15 (UTC) (edited on 2018-03-06 10:18 (UTC) by JJK)

The GUI is refusing to start for me.

Output teamviewer:

Init...
CheckCPU: SSE2 support: yes
Checking setup...
Launching TeamViewer ...
Starting network process (no daemon)
Network process already started (or error)
Launching TeamViewer GUI ...

After this, I cannot find the process running using ps -aux

Output after systemctl start teamviewerd:

● teamviewerd.service - TeamViewer remote control daemon
   Loaded: loaded (/usr/lib/systemd/system/teamviewerd.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-03-06 11:13:48 CET; 2s ago
  Process: 11428 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
 Main PID: 11430 (teamviewerd)
    Tasks: 16 (limit: 4915)
   CGroup: /system.slice/teamviewerd.service
           └─11430 /opt/teamviewer/tv_bin/teamviewerd -d

Mar 06 11:13:48 JJK-Laptop0 systemd[1]: Starting TeamViewer remote control daemon...
Mar 06 11:13:48 JJK-Laptop0 systemd[1]: teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after>
Mar 06 11:13:48 JJK-Laptop0 systemd[1]: Started TeamViewer remote control daemon.

Log file:

2018/03/06 11:13:48.790 11430 140636593351616 S   Logger started.
2018/03/06 11:13:48.796 11430 140636593351616 S   Found 0 core dump files ...
2018/03/06 11:13:48.797 11430 140636554204928 S+  Thread: SystemBusIO1
2018/03/06 11:13:48.798 11430 140636562597632 S+  Thread: SystemBusIO0
2018/03/06 11:13:48.800 11430 140636593351616 S   systemd: logind service available
2018/03/06 11:13:48.804 11430 140636593351616 S   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c1', canGraphical=1, canTTY=1, canMultiSession=1]
2018/03/06 11:13:48.806 11430 140636593351616 S+  DBus: optional property DefaultControlGroup not found
2018/03/06 11:13:48.806 11430 140636593351616 S+  DBus: optional property KillProcesses not found
2018/03/06 11:13:48.806 11430 140636593351616 S   LogindSessionInfo: New session LogindSessionInfo [id=c1 user=jjk state=user active=1 reliable=1 infoId=1591159457] [path=/org/freedesktop/login1/session/c1 TTY=tty1 seat=seat0 display= vtnr=1 owner=[SysUser: jjk [uid=1000, gid=1000 home=/home/jjk gecos= shell=/bin/zsh]] idle=0(1520330066490266) active=1 type=tty class=user state=active timestamp=1520330068819469 service=login defaultCG= leader=659 audit=0 remote=0 rHost= rUser= killProc=0]
2018/03/06 11:13:48.809 11430 140636535248640 S+  Thread: IOServiceWorker_0
2018/03/06 11:13:48.809 11430 140636526855936 S+  Thread: IOServiceWorker_1
2018/03/06 11:13:48.809 11430 140636593351616 S   SysSessionInfoManager: observing sessions from logind is marked as reliable
2018/03/06 11:13:48.809 11430 140636593351616 S+  logind: session info 'c1' is for VT 1, skipping.
2018/03/06 11:13:48.809 11430 140636593351616 S   SysSessionInfoManager: Session Information provided by VT [priority: 2]
2018/03/06 11:13:48.810 11430 140636510070528 S+  Thread: IOServiceWorker_3
2018/03/06 11:13:48.810 11430 140636518463232 S+  Thread: IOServiceWorker_2
2018/03/06 11:13:48.813 11430 140636593351616 S   Starting as daemon
2018/03/06 11:13:48.815 11430 140636593351616 S!  AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2018/03/06 11:13:48.818 11430 140636593351616 S   UpdateOnlineState newOnlineValue 0
2018/03/06 11:13:48.818 11430 140636593351616 S+  tvnetwork::Offline: online state 0
2018/03/06 11:13:48.818 11430 140636593351616 S!  AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2018/03/06 11:13:48.910 11430 140636593351616 S   System uptime: 1174 seconds
2018/03/06 11:13:48.911 11430 140636593351616 S   SystemID m=1 s=1 daa0e3c69d4944bea317b5303d4e9203



Start:              2018/03/06 11:13:48.911 (UTC+1:00)
Version:            13.0.9865 
ID:                 353538501
Loglevel:           Info (100)
License:            10000
Server:             master6.teamviewer.com
IC:                 -365577617
CPU:                Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
CPU extensions:     l9
OS:                 Lx Arch Linux (x86_64)
IP:                 130.89.229.180
MID:                ldaa0e3c69d4944bea317b5303d4e9203:f894c2b38d5f:7656afa32152466c827b915f2897eab5
MIDv:               1
Proxy-Settings:     Type=0 IP= User=

2018/03/06 11:13:48.925 11430 140636593351616 S   NetWatchdog: Internet is now connected
2018/03/06 11:13:48.926 11430 140636593351616 S   NetWatchDogLinux: initialized network manager connection
2018/03/06 11:13:48.926 11430 140636593351616 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/03/06 11:13:48.926 11430 140635977787136 S   RemoteSettingsStore: Cleanup all policies.
2018/03/06 11:13:48.927 11430 140636593351616 S   RemoteSettingsStoreListener: Establish connection.
2018/03/06 11:13:48.927 11430 140635977787136 S   RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty
2018/03/06 11:13:48.927 11430 140636593351616 S   Using IPC-Port 5939
2018/03/06 11:13:48.927 11430 140635977787136 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/03/06 11:13:48.930 11430 140636593351616 S   SysSessionInfoManager: own session cache set to '4294967295'
2018/03/06 11:13:48.930 11430 140636593351616 S   Updated sessions:  [ F (3510599056)   L root ] 
2018/03/06 11:13:48.930 11430 140636593351616 S   UpdateOnlineState newOnlineValue 0
2018/03/06 11:13:48.930 11430 140636593351616 S   UpdateOnlineState newOnlineValue 0
2018/03/06 11:13:48.931 11430 140635541595904 S   Using systemd-logind for suspend/resume monitoring

dcarter9 commented on 2018-02-16 21:33 (UTC)

@p.klotz that was it! Here's what ldd had:

ldd /opt/teamviewer/tv_bin/TeamViewer | grep libQt5WebKit                                                                                                                                                                                                                                                                                                           
        libQt5WebKitWidgets.so.5 => /usr/lib/libQt5WebKitWidgets.so.5 (0x00007fd4676a7000)
        libQt5WebKit.so.5 => not found
        libQt5WebKit.so.5 => not found

A simple re-install of qt5-webkit via pacman did the trick, as there were missing files in /usr/lib, such as libQt5WebKit.so.5.

Thanks so much for your assistance. Still learning about all the ways to troubleshoot issues like this.

p.klotz commented on 2018-02-16 20:02 (UTC) (edited on 2018-02-16 20:05 (UTC) by p.klotz)

@dcarter9

What does ldd say? It should look like this:

[user@host home]$ ldd /opt/teamviewer/tv_bin/TeamViewer | grep libQt5WebKit
        libQt5WebKitWidgets.so.5 => /usr/lib/libQt5WebKitWidgets.so.5 (0x00007f2a78f2b000)
        libQt5WebKit.so.5 => /usr/lib/libQt5WebKit.so.5 (0x00007f2a745d9000)

Maybe the symbolic link is missing. A "sudo ldconfig" call may help in this case.

dcarter9 commented on 2018-02-14 18:13 (UTC)

@Louis I thought the same when I first saw that error in gui.log but I'm pretty certain I have all the necessary dependencies. pkgfile output:

$ sudo pkgfile libQt5WebKit.so.5                                                                                                                                                                              
extra/qt5-webkit

I installed this package via yaourt - yaourt -S teamviewer-beta.

Louis commented on 2018-02-14 15:22 (UTC)

It seems that "qt5-webkit" isn't installed on your system. What's the output of "pkgfile libQt5WebKit.so.5" ?

How did you install this package?

dcarter9 commented on 2018-02-10 01:10 (UTC) (edited on 2018-02-10 01:53 (UTC) by dcarter9)

Apologies for the potential noob question as I am new to Arch but am really enjoying it. I'm unable to bring up the GUI and my logs don't appear to have anything major as an issue; no missing dependencies. Just to ensure, I've done a systemctl daemon-restart, systemctl enable teamviewerd and systemctl restart teamviewerd. Here's my log files:

$ cat gui.log

/opt/teamviewer/tv_bin/TeamViewer: error while loading shared libraries: libQt5WebKit.so.5: cannot open shared object file: No such file or directory

$ cat startup.log

Init...
TeamViewer:        13.0.6634 - DEB
Profile:           /home/<userid> (<userid>)
Desktop:           DS: '/usr/share/xsessions/plasma'  XDG: 'KDE'
XServer TTY:       1

ok (info)

CheckCPU: SSE2 support: yes
ok (profile)

$ cat TeamViewer13_Logfile.log

2018/02/09 17:36:08.478  5100 140273138641856 S   Logger started.
2018/02/09 17:36:08.481  5100 140273138641856 S   Found 0 core dump files ...
2018/02/09 17:36:08.481  5100 140273107900160 S+  Thread: SystemBusIO0
2018/02/09 17:36:08.481  5100 140273099507456 S+  Thread: SystemBusIO1
2018/02/09 17:36:08.482  5100 140273138641856 S   systemd: logind service available
2018/02/09 17:36:08.483  5100 140273138641856 S   systemd: New seat seat0 [path=/org/freedesktop/login1/seat/seat0, activeSession='c2', canGraphical=1, canTTY=1, canMultiSession=1]
2018/02/09 17:36:08.483  5100 140273138641856 S+  DBus: optional property DefaultControlGroup not found
2018/02/09 17:36:08.483  5100 140273138641856 S+  DBus: optional property KillProcesses not found
2018/02/09 17:36:08.483  5100 140273138641856 S   LogindSessionInfo: New session LogindSessionInfo [id=c2 user=<userid> state=user active=1 reliable=1 infoId=3353246491] [path=/org/freedesktop/login1/session/c2 TTY= seat=seat0 display=:0 vtnr=1 owner=[SysUser: <userid> [uid=1000, gid=1000 home=/home/<userid> gecos=<User Name> shell=/bin/bash]] idle=0(0) active=1 type=x11 class=user state=active timestamp=1518215216082318 service=sddm defaultCG= leader=976 audit=0 remote=0 rHost= rUser= killProc=0]
2018/02/09 17:36:08.484  5100 140273065686784 S+  Thread: IOServiceWorker_1
2018/02/09 17:36:08.484  5100 140273074079488 S+  Thread: IOServiceWorker_0
2018/02/09 17:36:08.484  5100 140273057294080 S+  Thread: IOServiceWorker_2
2018/02/09 17:36:08.485  5100 140273138641856 S   SysSessionInfoManager: observing sessions from logind is marked as reliable
2018/02/09 17:36:08.485  5100 140273048901376 S+  Thread: IOServiceWorker_3
2018/02/09 17:36:08.485  5100 140273138641856 S+  LateBinding [libX11.so.6]: Loaded library
2018/02/09 17:36:08.485  5100 140273138641856 S   SysSessionInfoManager: Session Information provided by VT [priority: 2]
2018/02/09 17:36:08.486  5100 140273138641856 S   Starting as daemon
2018/02/09 17:36:08.487  5100 140273138641856 S!  AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2018/02/09 17:36:08.487  5100 140273138641856 S   UpdateOnlineState newOnlineValue 0
2018/02/09 17:36:08.487  5100 140273138641856 S+  tvnetwork::Offline: online state 0
2018/02/09 17:36:08.487  5100 140273138641856 S!  AsioSettings::FindExternalIP: found 0 external IPs instead of 1!
2018/02/09 17:36:08.488  5100 140273138641856 S   Generating new RSA private/public key pair
2018/02/09 17:36:08.512  5100 140273138641856 S   System uptime: 11375 seconds
2018/02/09 17:36:08.512  5100 140273138641856 S   SystemID m=1 s=0 932101dd40904669aedec0f525d5b32c



Start:              2018/02/09 17:36:08.513 (UTC-8:00)
Version:            13.0.6634 
ID:                 0
Loglevel:           Info (100)
License:            0
Server:             master5.teamviewer.com
IC:                 784793821
CPU:                Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz
CPU extensions:     l9
OS:                 Lx Manjaro Linux (x86_64)
IP:                 10.146.66.135
MID:                784793821_3b3ab30af_880ef2a283986696
MIDv:               0
Proxy-Settings:     Type=0 IP= User=

2018/02/09 17:36:08.529  5100 140273138641856 S   NetWatchdog: Internet is now connected
2018/02/09 17:36:08.529  5100 140273138641856 S   NetWatchDogLinux: initialized network manager connection
2018/02/09 17:36:08.529  5100 140273138641856 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/02/09 17:36:08.529  5100 140272910440192 S   RemoteSettingsStore: Cleanup all policies.
2018/02/09 17:36:08.529  5100 140273138641856 S   RemoteSettingsStoreListener: Establish connection.
2018/02/09 17:36:08.529  5100 140272910440192 S   RemoteSettingsStore::LoadLastReceivedPolicies : Storage Entry Remote_Settings_TVClientSetting_Policy empty
2018/02/09 17:36:08.529  5100 140272910440192 S   RemoteSettingsMDRelationshipWatchDog: DEVICE ISN'T A MANAGED DEVICE
2018/02/09 17:36:08.529  5100 140273138641856 S   Using IPC-Port 5939
2018/02/09 17:36:08.530  5100 140273138641856 S   SysSessionInfoManager: own session cache set to '4294967295'
2018/02/09 17:36:08.530  5100 140273138641856 S   Updated sessions:  [ X0 (3353246491) CA  <userid> ]  [ F (3510599056)   L root ] 
2018/02/09 17:36:08.530  5100 140273138641856 S   UpdateOnlineState newOnlineValue 0
2018/02/09 17:36:08.530  5100 140273138641856 S   Updated sessions:  [ X0 (3353246491) CA  <userid> ]  [ F (3510599056)   L root ] 
2018/02/09 17:36:08.530  5100 140273138641856 S   UpdateOnlineState newOnlineValue 0
2018/02/09 17:36:08.530  5100 140273138641856 S   UpdateOnlineState newOnlineValue 0
2018/02/09 17:36:08.531  5100 140272138704640 S   Using systemd-logind for suspend/resume monitoring
2018/02/09 17:36:08.531  5100 140272138704640 S   SessionLogon: session 3353246491, desktop switched 0, last desktop session 4294967295
2018/02/09 17:36:08.531  5100 140272138704640 S   StartProcessesAsync: Session ready after 0s

maximbaz commented on 2018-02-09 11:29 (UTC)

@DuBistKomisch see this and this

DuBistKomisch commented on 2018-02-09 11:08 (UTC) (edited on 2018-02-09 11:08 (UTC) by DuBistKomisch)

I'm using startx + i3 and TV13 doesn't start, it just exits after saying it's launching the GUI in the command line, no error message. TV12 works fine though. Maybe it's also to do with no display manager? I don't really want to have to install one though.

tulleydr commented on 2018-02-03 17:11 (UTC) (edited on 2018-02-04 01:32 (UTC) by tulleydr)

Client will connect to host on arch linux (both devices), but screen will not refresh on client. The only screen you can see is the first load. If both devices are view-able, you can see the mouse moving and packages opening on host, but client only sees first screen that is loaded.

OS: Arch Linux Kernel: x86_64 Linux 4.14.15-1-ARCH Shell: bash 4.4.18 Resolution: 1440x900 DE: KDE 5.42.0 / Plasma 5.11.5 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core2 Duo P8600 @ 2x 2.401GHz [50.0°C] GPU: intel RAM: 715MiB / 3843MiB

[EDIT] The problem was that I was using xf86-video-intel drivers.

To fix I installed vesa drivers and removed intel drivers:

pacman -S xf86-video-vesa

pacman -Rs xf86-video-intel

reboot

gbr commented on 2018-01-31 22:11 (UTC) (edited on 2018-01-31 22:16 (UTC) by gbr)

Does anybody know why starting teamviewerd via systemctl takes so long? If I manually start it it's blazing fast:

$ time sudo systemctl start teamviewerd
sudo systemctl start teamviewerd  0,01s user 0,01s system 0% cpu 26,765 total

versus:

$ time sudo /opt/teamviewer/tv_bin/teamviewerd -d
sudo /opt/teamviewer/tv_bin/teamviewerd -d  0,01s user 0,01s system 98% cpu 0,020 total

guiguan commented on 2018-01-28 12:31 (UTC)

@zesaver also needed to restart system

zesaver commented on 2018-01-24 11:35 (UTC)

I've got "No connection." error after upgrading from stable (tv12). It was resolved by running systemctl start teamviewerd.service Now it is working well for me (Arch Linux, LightDM, xfce4).

oranje25 commented on 2018-01-23 14:00 (UTC)

@c84 @yair

I had the same error - was starting KDE manually w/o display manager. I setup one (SDDM) and now TV13 works, no issues.

kiwiarch commented on 2018-01-17 01:20 (UTC) (edited on 2018-01-17 01:43 (UTC) by kiwiarch)

I have an issue where teamviewer 13 crashes Mate Notifications applet. Anyone had this issue? If the you have please let me you how you fixed it. There is nothing in the teamviewer logs and cant find where the mate notifications app would log it.

journalctl output

https://pastebin.com/iR8wnwuA

yair commented on 2018-01-15 12:19 (UTC)

@c84 noted i can confirm. i had the same error message

had to set up a desktop manager for i3wm (i used lightDM) .

that solved the issue. tv13 now works.

severach commented on 2018-01-03 17:39 (UTC)

No more wine. When wine was used it was mostly supplied. All that was needed was some extra libraries.

snqlby commented on 2018-01-03 17:15 (UTC)

Does this version not require wine?

forbi commented on 2017-12-28 16:10 (UTC)

I can confirm the behavior that @c84 reports. When I launch startx tv does not work. But after installing Slim, tv works just fine.

Somehow TV manages to break my Mate Notification Area plugin. So, back to TV 12...

severach commented on 2017-12-27 08:48 (UTC) (edited on 2017-12-27 08:51 (UTC) by severach)

I finally got it all working. On one machine (Antergos) it said "No connection." Settings refused to save. The tgz did work so I switched the PKGBUILD to rpm and fixed that one. On another (Arch) that didn't show a GUI I found that a greeter is required. startx and startxfce4 from a text login does not work. systemctl enable --now lightdm also doesn't work. The system must boot to the greeter.

lucasbrynte commented on 2017-12-21 22:16 (UTC)

After realizing I need to start the daemon teamviewerd.service, this is working great for me! Such a relief, since my remote part requires my local teamviewer to be version 13.

So grateful to you guys for packaging this, someday I will make the effort and learn about the process as well.

c84 commented on 2017-12-21 09:50 (UTC)

I found something which could be related to my issue: https://community.teamviewer.com/t5/Linux/Teamviewer-13-amp-Debian-Stable-9-2-no-GUI/td-p/24817

According to them, it could be due to the fact that I'm not using a display manager.

I'm still not sure I want to use one - if I decide to try I will let you know the result.

c84 commented on 2017-12-20 11:51 (UTC) (edited on 2017-12-20 20:27 (UTC) by c84)

@Louis, sure, here they are:

[user@host ~]$ cat ~/.local/share/teamviewer13/logfiles/startup.log

https://pastebin.com/jt673GTj

[user@host ~]$ cat ~/.local/share/teamviewer13/logfiles/TeamViewer13_Logfile.log

https://pastebin.com/zQcCDrHA

Louis commented on 2017-12-20 11:33 (UTC)

@c84 Can you post the output of ~/.local/share/teamviewer13/logfiles/startup.log and ~/.local/share/teamviewer13/logfiles/TeamViewer13_Logfile.log?

c84 commented on 2017-12-20 09:06 (UTC) (edited on 2017-12-20 09:07 (UTC) by c84)

Unluckily it doesn't start on my machine, could not find any reason for that, exception following error message:

2017/12/20 10:03:51.537 2461 140346522287232 G!!!Own session could not be resolved, unable to startup

2017/12/20 10:03:51.537 2461 140346522287232 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 5 failed with error 2

2017/12/20 10:03:51.537 2461 140346522287232 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 6 failed with error 2

2017/12/20 10:03:51.537 2461 140346522287232 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 9 failed with error 2

2017/12/20 10:03:51.537 2461 140346522287232 G!! ConfigurationHub::HandleRegistrationResponse(): registering for feature 10 failed with error 2

2017/12/20 10:03:51.537 2461 140346522287232 G interprocessbase::SecureNetwork destroyed

2017/12/20 10:03:51.545 2461 140346522287232 G Shutting down System DBus

Someone an idea about that?

alecmev commented on 2017-12-18 21:28 (UTC)

@Louis Can you publish it, please?

Louis commented on 2017-12-16 21:23 (UTC)

@gun26 thx it works perfectly now

gun26 commented on 2017-12-14 14:39 (UTC) (edited on 2017-12-15 05:08 (UTC) by gun26)

@Nachoc, @Louis - I had the same problem, and after looking at TeamViewer13_Logfile.log, figured out that I was missing a dependency. Turned out to be qt5-quickcontrols, which should maybe be added into the PKGBUILD's dependencies. Now Teamviewer 13 displays, although I haven't had a chance to actually use it yet.

Edit (after trying it in action, remote controlling a Windows Teamviewer 13 host): Nope, although Teamviwer can connect to the host, after connecting the Teamviewer menu attached to the host window's titlebar is missing. This is the white menu with the big X at the left end. So, I'm still missing dependencies, probably qt5-related.

Edit 2: After reading this thread at Teamviewer's Community board https://community.teamviewer.com/t5/Linux/Update-TeamViewer-13/td-p/24537 I realize that what I'm talking about is the Teamviewer "toolbar" and it's simply not implemented yet. And without it, you can't do things like send "Ctrl-Alt-Del" or, in my case, use the Communicate, Switch Sides functionality. The toolbar is "coming soon" according to that thread.

Nachoc commented on 2017-12-14 03:24 (UTC)

@Louis Did you check the log files located in ~/.local/share/teamviewer13/logfiles

Louis commented on 2017-12-13 17:31 (UTC)

@Nachoc It installed fine for me, but if I start it under Gnome X11 only the tray icon shows up. If I click on "Show Teamviewers", "Show computers and contacts" and the other entries on there nothing happens

Stempit commented on 2017-12-12 07:32 (UTC)

Thanks @Nachoc! I was commented line #18, run "sudo systemctl daemon-reload" and "sudo systemctl restart teamviewerd" and now works great!

Nachoc commented on 2017-12-10 20:35 (UTC)

PKGBUILD for version 13.0.5693: https://pastebin.com/pv6pGpJL

dano5 commented on 2017-12-02 11:55 (UTC)

tw13 beta full version is out: https://community.teamviewer.com/t5/Linux/Update-TeamViewer-13/m-p/24537#M1131 uses qt5 instead of wine

bobpaul commented on 2017-11-17 22:10 (UTC)

It installs if pkgver=12.0.85001 and the hashes are updated with makepkg -g However, the GUI never opens for me, even if I have the teamviewerd service running. I tried manually installing the *.tar.xz from their website and had the same problem.

nashley commented on 2016-12-14 12:58 (UTC) (edited on 2016-12-14 14:11 (UTC) by nashley)

Should depend on the following to function correctly as the remote: - `lib32-xtst` for keyboard and mouse input to work - `lib32-libxrandr` for multiple monitors to display separately There are some bugs (features?) that I have yet to work out. I'll update if I find required libraries for these: - teamviewer isn't running unless the GUI is (even if the systemd service is) - The window that shows incoming session information is displayed at the bottom left of the monitor and forces windows to move up (instead of showing up at the bottom right on top of other windows) in i3 Digging through the logs, it looks like the following are related, but I'm not sure why yet: - xsm

Ferik commented on 2016-11-27 12:09 (UTC)

ln -s /opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop \ "${pkgdir}"/usr/share/applications/teamviewer.desktop ln -s /opt/teamviewer/doc/License.txt \ "${pkgdir}"/usr/share/licenses/teamviewer/LICENSE

bit_shifter commented on 2016-11-17 18:53 (UTC)

For the current 12 Beta (v12.0.69753): $ diff teamviewer_beta_pkgbuild.sh teamviewer_beta_pkgbuild_updated.sh 8c8 < pkgver=11.0.52520 --- > pkgver=12.0.69753 32,33c32,33 < sha256sums_x86_64=('d862fe3f26bf05e7b7f5fd5972873b5d859e40059c7f41783865594fc58d38fd') < sha256sums_i686=('66f2444b660b87f2fdc1d19949b94bbd840982d51c3405e4a53799cd6a6c6090') --- > sha256sums_x86_64=('d4997c9f3ac7ec996e4b890bb3dcbd900ffe8fb9491632e51d61028e835e23c7') > sha256sums_i686=('6110e5ba521f7ffb429d7d0bf5f03dad7a18994dc6b62a6901353f1da7dbc744')

dpeukert commented on 2016-11-09 18:28 (UTC) (edited on 2016-11-09 18:28 (UTC) by dpeukert)

TeamViewer 12 Beta is out now: https://www.teamviewer.com/en/download/linux/

funilrys commented on 2016-08-09 13:40 (UTC)

Did this use wine !?

eworm commented on 2015-12-01 16:26 (UTC)

Yes, 11.0.52520 is stable. But it does not make sense to keep old beta versions while there's no beta available, no? ;)

wcasanova commented on 2015-12-01 15:18 (UTC)

is no beta, teamviewer_11.0.52520_amd64.deb is release stable.

Wieschie commented on 2015-11-23 20:53 (UTC)

@eworm You're right, there are some icons that aren't drawn. The quick connect button on the home page isn't drawn and doesn't appear to be clickable, and the 4 icons on the top of the "Computers and Contacts" window aren't drawn but are still usable. I can still use it for everything I need, but I'll edit my original reply as to not mislead others.

eworm commented on 2015-11-23 15:26 (UTC)

Wieschie, you are sure that everything is painted as expected? The Teamviewer logo for example? Or the connect button?

Wieschie commented on 2015-11-23 15:10 (UTC) (edited on 2015-11-23 20:53 (UTC) by Wieschie)

For what it's worth, I just edited the PKGBUILD to require lib32-libpng (the version currently available in the Arch Repos) it builds and runs. Some icons aren't drawn however, but it's usable enough for me.

eworm commented on 2015-11-20 06:23 (UTC)

Ah, right. This requires (lib32-)libpng12 now... What the hell?!

dixi_minga commented on 2015-11-19 22:46 (UTC)

@myself: I need to install lib32-libpng12, should be a dependency now it works like a charm for my purposes

dixi_minga commented on 2015-11-19 22:34 (UTC)

Thanks eworm, but I have the problem: No "Connect to partner" Button, no "sign up" button. teamviewerd.service is running. Other teamviwers can connect me, but I`m not able to connect to other teamviewers