Comment 8 for bug 1198649

oh, that's actually a very interesting result, because 'telinit u' is pretty much the only substantial thing done by the upstart maintainer script on upgrade. So if calling 'sudo telinit u' directly does *not* trigger the problem, then it seems we need to look deeper.

BTW, it appears that your logs not only don't capture the bits that we need, but are actually corrupted. What filesystem are you using?

The other thing I notice in the logs is that the corruption always happens immediately after the message about 'Processing triggers for hicolor-icon-theme ...'. So it's possible the upstart package itself is not what's causing this problem.

Can you reproduce the hang by running 'sudo dpkg --configure upstart' from the commandline?