teamviewer - aka running deamons

[retos]

Has anyone accomplished to launch teamviewer?

[dnschneid]

Does it not work with the standard approach?

[retos]

Nope, unfortunately not. I did the following:

Downloaded the newest 64-bit version from the teamviewer homepage.
(Since the shell command "uname -m" gave me "x86_64" back)

double clicked in file manager to open it with the package installer. Installation went trough, it appeared in the "Applications Menu" under "Internet". But clicking on it brings the error message: "Error. The Teamviewer deamon is not running..." Tried starting it with "sudo teamviewer --deamon start". Didn't work, system didn't know what I want.

I removed the installation and tried again. This time it mentioned something different:"wine: /home/retos/.config/teamviewer8 is not owned by you". Don't know what was different this time, might be because I tried to install VMWare Player in between?

Then I removed the package again. Installed wine with: "sudo apt-get install wine". And installed teamviewer again. Same message appeared when I tried to start the application(deamon not running).

Starting the deamon without the sudo, also does not do the trick. But gives me more errors:

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)
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

ps: Forgive me if the formatting of this post looks bad, it's my very first post on gitbub! And last but not least: crouton rocks! Thanks a lot!

[dnschneid]

You probably ran something as sudo that wasn't supposed to be and now file permissions are funny; sudo chown -R 1000:1000 ~/.config/teamviewer8 should correct that.

Try adding /usr/bin/teamviewer --daemon start to /etc/rc.local, then exiting and entering the chroot.

[retos]

Hmm, didnt work. After that I tried:

reto@localhost:~$ sudo sh /etc/rc.local 
[sudo] password for reto: 

initctl start teamviewerd
initctl: Unknown job: teamviewerd
fail

reto@localhost:~$ 

The output when starting the deamon manually still looks the same.

[retos]

If I want to remove the whole thing and start fresh. It would be the command sudo delete-chroot evilchroot right?
Because that didn't work:

chronos@localhost / $ sudo delete-chroot evilchroot
/usr/local/chroots/evilchroot not found.

[michaelorr]

evilchroot should be replaced with the name of the chroot you gave when you first created it. If you didn't specify one, the name will be the release version of ubuntu (which is precise by default). If you want to be certain of the name, just look at the output from ls /usr/local/chroots. By default crouton installs each chroot here in a separate directory based on the name.

[dnschneid]

Oh, it looks like teamviewer is trying to start its daemon via upstart, which won't work in crouton due to some pretty fundamental design choices with upstart (see relevant bugs for the issues involved).

Look inside /etc/init/teamviewerd for the commands it needs to run to launch, then try running them manually (as root).

[artemkolotilkin]

Just for future reference the command you need to run to launch TeamViewer is:

sudo /opt/teamviewer8/tv_bin/teamviewerd -f

[retos]

Thank you.

On 10 September 2013 13:42, Artem Kolotilkin notifications@github.comwrote:

Just for future reference the command you need to run to launch TeamViewer
is:

sudo /opt/teamviewer8/tv_bin/teamviewerd -f

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-24153347
.

[superlou]

Using sudo /opt/teamviewer9/tv_bin/teamviewerd -f I was able to start the TeamViewer 9 daemon, and get the GUI to start. However, it says "Not ready. Please check your connection" and doesn't let me connect to an account. The sign in button seems disabled. Has anyone had any luck with TeamViewer 9?

[duuster]

I was also able to get Teamviwer 9 running, but when the GUI starts I also get the "Not ready. Please check your connection" error.

[superlou]

I installed TeamViewer 8, and that has a "Ready to connect" message rather than the "check your connection" message. However, in the Computers and Contacts dialog, the Sign In box is still broken. If I click the Sign Up link, and select use an existing account, the Next button does not seem to do anything after I've entered my credentials.

[excel4]

I prefer the "instant support" / uninstalled versions of teamviewer. After installing wine I was unable to get teamviewer9 to work. teamviewer8 failed with a missing library. However, teamviewer7 seems to work. My environment is trusty/unity on a C710.

[nashtag]

I can get teamviewer to work, but like you, I can't connect or sign in.

"I installed TeamViewer 8, and that has a "Ready to connect" message rather than the "check your connection" message. However, in the Computers and Contacts dialog, the Sign In box is still broken. If I click the Sign Up link, and select use an existing account, the Next button does not seem to do anything after I've entered my credentials."

[AlexanderKomarov]

@excel4 thank you for your advice! It's a good point! Teamviewer7 works.

[forresthopkinsa]

Can confirm that initctl still shows Unknown job: teamviewerd when trying to install Teamviewer 10

[dnschneid]

Nothing has changed with upstart support; you still have to run the commands manually.

[forresthopkinsa]

Even then, doesn't work. I have yet to get Tv10 working on Crouton running Trusty.

[nevynduarte]

went through the folders using a file manager and found the file, added a shortcut to the desktop and works like a charm.

[forresthopkinsa]

It's okay. We don't need to use Crouton for Teamviewing anymore. Teamviewer 11 is now compatible directly with Chrome OS.

[kajodowe]

forresthopkinsa -- Amen to that! Teamviewer 11 works wonderfully on the Chrome OS side to control a remote computer. I had the same issues as all users above and was not successful except to run it in Chrome.

[kajodowe]

Oh and one more comment! I am always using my Chromebook on the crouton side so having Teamviewer running on the Chrome OS side is great because keeps the remote system out of my hair (so to speak) except for when I want to control my desktop remotely.

[ikey4u]

Also I install teamview 11.0 on my ubuntu 14.04 x64, when i run commmand teamviewer --daemon start,it gives me errors like:initctl start teamviewerd initctl: Unknown job: teamviewerd fail
,so i just run the command with sudo sudo teamviewer --daemon start,it works fine and is able to connect to the network.One reason causing this error is that you login in as root user,and if you do not run the command with sudo,teamviewer may think you are not ROOT,really weird things!
May this help someone.

[forresthopkinsa]

I'm not totally understanding what you're saying @ikey4u but have you tried using sudo -h?

[ikey4u]

@forresthopkinsa When you login in your system as root user,you may think you can run any commands in root privileges by default,but its not true.In some cases,you should use sudo to explicitly declare that you wanna to run the command in root privileges.For example ,you should run teamview with the command sudo teamviewer --daemon start but not the command teamviewer --daemon start even though you are root user.

[DennisLfromGA]

@ikey4u - You login into your system from crosh using sudo so 'root' can set things up, mounting directories, etc. But, you are logged into your user account, the one you specified when you installed your chroot. Therefore, you don't have root permissions and need to prefix commands/applicaitons that need root priveleges with sudo.

[ikey4u]

@DennisLfromGA Wow! Excellent Explanation. Thank u ~

[wallace11]

Just for future reference, I was able to run Team Viewer inside chroot by using the "Unofficially supported" tar.xz version (v12.0.76279) by simply dl, extract and run the teamviewer executable. No extra libs required for me, worked right away.
Hope this helps someone in the future ;)