Teamviewer not ready check your connection

Project Discussion
1

I tried to use teamviewer outside a toolbox:

rpm-ostree install teamviewer_14.6.2452.x86_64.rpm
systemctl restart teamviewerd.service
Failed to restart teamviewerd.service: Unit teamviewerd.service not found.

and failed. Inside a toolbox, the following error message appears:

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

Any advice? Appreciate.

2

I think you need to reboot the system after the package install. Then you use systemctl to start the service.

3

Thanks! I did that but

$ teamviewer daemon status

returns

systemctl status teamviewerd.service
Unit teamviewerd.service could not be found.
fail

4

sudo teamviewer daemon enable
sudo systemctl enable teamviewerd.service
sudo systemctl start teamviewerd.service

works and reports

systemctl status teamviewerd.service
● teamviewerd.service - TeamViewer remote control daemon
Loaded: loaded (/usr/lib/opt/teamviewer/tv_bin/script/teamviewerd.service; ena>
Active: active (running) since Sat 2019-09-28 10:34:47 CEST; 2min 21s ago
Process: 1661 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, sta>
Main PID: 1691 (teamviewerd)
Tasks: 28 (limit: 4915)
Memory: 19.2M
CGroup: /system.slice/teamviewerd.service
└─1691 /opt/teamviewer/tv_bin/teamviewerd -d

Sep 28 10:34:47 freckle systemd[1]: Starting TeamViewer remote control daemon…
Sep 28 10:34:47 freckle systemd[1]: teamviewerd.service: Can’t open PID file /run>
Sep 28 10:34:47 freckle systemd[1]: Started TeamViewer remote control daemon.

but still Teamviewer not ready - check your connection. I am not inside a toolbox here.

5

I use Teamviewer for work but also wanted to try Silverblue. For anyone needing this mix of software, this is how I got it to work for me on Silverblue 33 and Teamviewer 15.11.6. I have only tested this with my computer being the guest/local, I haven’t tested the Silverblue platform as the host/remote.

Install teamviewer and reboot:

sudo rpm-ostree install teamviewer*.rpm
sudo systemctl reboot

I think because Silverblue’s directory tree is a bit unusual the service files don’t get installed correctly, but asking the teamviewer application to enable the daemon installs them successfully.

sudo teamviewer daemon enable
sudo systemctl start teamviewerd

Verify it is running:

sudo systemctl status teamviewerd

The error about the PID and permission denied is a red-herring. The actual hindrance is SELinux:

type=AVC msg=audit(1611458278.466:6954): avc:  denied  { name_connect } for  pid=1353 comm="teamviewerd" dest=80 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=0

Running audit2why suggests this solution:

sudo setsebool -P nis_enabled 1

After this, I would get a green connection and could connect to my remote hosts; I do not know the entirety of the security implications of this action. These SELinux errors do not occur in Workstation.

There is some other SELinux error related to the framebuffer, but that did not stop me from performing work on the remote machine.

type=AVC msg=audit(1611458281.540:6976): avc:  denied  { read write } for  pid=1353 comm="teamviewerd" name="fb0" dev="devtmpfs" ino=440 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:framebuf_device_t:s0 tclass=chr_file permissive=0
2 Likes
6

Thank you very much!

I can use Teamviewer on Silverblue following your post.

1 Like
7

May u add that your issue is solved?

Thx :wink:

v/r
Andi

8

I am not the OP. Just that I have the same find this topic helpful.

9

ah okay I see! Sry for miss understanding it!

@ng0177
Has your problem with Teamviewer be solved as well?

1 Like
10

Alternatively one could download the Archive listed under ’ Other systems (not officially supported)’ and extract it e.g. to ~/bin

It includes a .desktop file as well, which can be copied to ~/.local/share/applications/

1 Like