The bug is produced by the process teamviewerd how Kevin Normoyle
writed, this process is stated by upstart with the configuration found
in /etc/init/teamviewerd.conf
$cat /etc/init/teamviewerd.conf
description "TeamViewer remote control daemon"
exec /opt/teamviewer8/tv_bin/teamviewerd -f
# lightdm: Ubuntu
# mdm: Mint (does not support upstart signals)
# prefdm: RedHat 6
start on (login-session-start or
starting gdm or
starting kdm or
starting lightdm or
starting lxdm or
starting prefdm or
starting xdm)
stop on (stopping gdm or
stopping kdm or
stopping lightdm or
stopping lxdm or
stopping prefdm or
stopping xdm)
respawn
respawn limit 5 60
For a workaround I stoped the service from autostart with
# echo "manual" > /etc/init/teamviewerd.override
Witch disabled the service, but teamViwer don't start unless you do an
$ sudo service teamviewerd start
If someone can check with "expect" or another command can use the
"/etc/init/teamviewerd.conf " to work It will be very useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094218
Title:
lsb_release crashed with IOError in getstatusoutput(): [Errno 10] No
child processes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1094218/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
