[Bug 1198649] Re: Update to 1.8-0ubuntu1.2 in raring causes system hang at configure
Stephan Frank
sfrank at cs.tu-berlin.de
Mon Jul 8 20:22:24 UTC 2013
On 07/08/2013 09:46 PM, Steve Langasek wrote:
> Unfortunately, if the system is locking up completely, the logs
> afterwards are not likely to be very useful (and these don't seem to
> be).
>
> To debug this, please try the following:
>
> - run 'sudo telinit u' from the commandline, and let us know whether this triggers the failure. (This is the most likely cause of the failure.)
Does not freeze, but does not produce any output
> - if it does:
> - please send us the output of 'initctl version'
init (upstart 1.8)
> - switch out to a text console (Ctrl+Alt+F1), log in, and run 'sudo telinit u' again. If there is any output on the screen, take a picture and attach it to this bug.
Does not switch to the console (a problem with the FGLRX driver? I would
have sworn that worked recently).
Altogether no very helpful, my apologies.
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
More information about the foundations-bugs
mailing list