Comment 2 for bug 1440180

The error in the log is:

Setting up initscripts (2.88dsf-41ubuntu18) ...
insserv: warning: script 'S99teamviewer' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cron'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `cron'
insserv: warning: script 'teamviewer_start' missing LSB tags and overrides
insserv: There is a loop between service rc.local and procps if started
insserv: loop involving service procps at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop at service rc.local if started
insserv: Starting teamviewer_start depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting teamviewer_start depends on rc.local and therefore on system facility `$all' which can not be true!
<snip>
insserv: Max recursions depth 99 reached
insserv: loop involving service hddtemp at depth 1
<snip>
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

This is caused by a non-Ubuntu init script on your system, /etc/init.d/teamviewer_start, which is not an LSB init script, which prevents the system from calculating boot ordering on upgrade.

So your non-Ubuntu init script is archaic and doesn't work right on a recent system - however, Ubuntu should handle this more gracefully on upgrade, rather than breaking the upgrade in the middle.

Dimitri, do you have any insight into how this should be handled? I'm sure it wasn't the intention to have systems with non-Ubuntu init scripts fail to upgrade, but I don't remember what the plan was for handling this case.