On 07/08/2013 10:38 PM, Steve Langasek wrote:
> 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?
file system is ext4
> 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?
>
That went through; it was the pending downgrade from my previous tries.
After that the upgrade to the new version 1.8-0ubuntu1.2 went
successfully as well. So unfortunately, I can't reproduce the problem
any more.
On 07/08/2013 10:38 PM, Steve Langasek wrote:
> 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?
file system is ext4
> 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?
>
That went through; it was the pending downgrade from my previous tries.
After that the upgrade to the new version 1.8-0ubuntu1.2 went
successfully as well. So unfortunately, I can't reproduce the problem
any more.
Regs,
Stephan