[Bug 1198649] Re: Update to 1.8-0ubuntu1.2 in raring causes system hang at configure

[Stephan Frank]

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1198649

Title:
  Update to 1.8-0ubuntu1.2 in raring causes system hang at configure

Status in Upstart:
  Invalid
Status in “upstart” package in Ubuntu:
  New

Bug description:
  Hi,

  the recent upgrade to upstart 1.9.1 seems to have introduced a bug
  that causes a hang during the package configuration phase. The package
  has been extracted by the system updater and once configuration starts
  the systems freezes completely (mouse pointer disappears, no remote
  login possible, system does not seem to respond in any way).

  Dpkg is now in a state where I am demanded to execute 'dpkg
  --configure -a', however since this freezes the system immediately
  again, I have no idea how or where to analyze the problem or how to
  proceed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1198649/+subscriptions