Fix This! – Getting TeamViewer to run on startup

If the above error looks familiar, it’s because it should.  Just about every Linux install of Team viewer encounters this error.  Why?  I can only assume that while the Windows/Mac OS X install assumes you would obviously want team viewers service running the background, LINUX users, well shit, they can figure it out!  This quite hilarious predicament leaves us with running this to enabled the service:

sudo teamviewer --daemon start

Is this acceptable?  No!  Start a revolutions.  BUT, like the philosophy of Linux, we solve problems, and that is our code, our DNA, and what we do.  Luckily this one is a simple one:

sudo teamviewer --help

Holy cow, what do we have here, actual relevant information!  Pardon my sarcasm, but I should not have to run into the help file to fix something that should be on by default, and is* on by default in other Operating Systems.  There are several options, but this is the one we are looking for:

sudo teamviewer --daemon enable

Problem solved!!!  Hope this fix helped you get on your way and on with life, ya know, to better things like configuring Apache sites 🙂

Till next time,



About professorkaos64

Posted on 20130622, in Fix This! and tagged , , , . Bookmark the permalink. 2 Comments.

  1. I get this error when running the start command. Debian x64 Wheexy

    initctl start teamviewerd
    initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

  2. i have enable the daemon but when i check the status is still stop/waiting

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s