How to fix TeamViewer: Not ready. Please check your connection

If you run TeamViewer you will see the following output

Init...

CheckCPU: SSE2 support: yes

Checking setup...

Launching TeamViewer ...

Starting network process (no daemon)

Network process already started (or error)

Launching TeamViewer GUI ...

If you have an eternal loading, you will see the following window:


To solve it, and could to connect to a remote computer you must run teamviewer as daemon as follows:

sudo teamviewer --daemon enable

Action: Installing daemon (15.5.3) for 'systemd' ...

installing /etc/systemd/system/teamviewerd.service (/opt/teamviewer/tv_bin/script/teamviewerd.service)

Try: systemctl enable teamviewerd.service

systemctl start teamviewerd.service

Now, execute again teamviewer as follows:

teamviewer                    

Init...

CheckCPU: SSE2 support: yes

Checking setup...

Launching TeamViewer ...

Launching TeamViewer GUI ...

Enjoy it!


Comments

Post a Comment

Popular posts from this blog

How to fix Android when developer options are not available for this user

Image
I have an Android One with Oreo version and suddenly my Android rebooted and after that it started to behave strangely: 1) Notification section doesn't work. I can't see notifications from my apps and the arrow and the screw icon to settings access don't work. 2) As I can't access to the notification area, I can't enable Use USB to Transfer Files to access to my phone memory. 3) I can't access to developer mode (I before active it with a lot of taps over Build number). Clicking on developer options just shows developer options are not available to this user. 4) I can't update or install the apps on google play. They freeze on Download pending... message 5) Home and Switch buttons don't work. They light up and vibrate when I tap them but they do nothing. This issue is apparently related to a deconfiguration of user accounts. To fix it, you need re-setup the users. As you can't access to the user manager (you are in guest mode
Read more

Exception: Could not find a default OpenFlow controller in Mininet

If you try to run a mininet script like this  , maybe you will get this problem if you are under Ubuntu. Exception: Could not find a default OpenFlow controller  This is trigger because your system don't find a default controller . To enable it just add the first line and add the controller argument to net variable like the second line: from mininet.node import OVSController net = Mininet(topo=topo,host=CPULimitedHost, link=TCLink,controller = OVSController) Now, you will get the following error: c0 Cannot find required executable ovs-controller. Please make sure that it is installed and available in your $PATH: (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin) ovs-controller is a legacy name. You need to be sure that you has it. sudo apt-get install openvswitch-testcontroller sudo cp /usr/bin/ovs-testcontroller /usr/bin/ovs-controller If you run it again, you should kill ovs-testcontroller first to avoid this: Exception: Please shut d
Read more

v4l2: open /dev/video0: Permission denied

If you try to stream using your webcam throught vlc or xawtv vlc v4l2:///dev/video0 or xawtv -c /dev/video0 probably you will have this issue. To solve it, you must add your user to the video group as follows: sudo adduser username video sudo usermod -a -G video username where username is your user (whoami) Now restart your computer Enjoy it!
Read more