This problem affects those systems hosting chroots but also affects those with sbuild/pbuilder installed. The failure process is as follows:
- user builds a package in the sbuild/pbuilder env. - upstart gets updated within the sbuild/pbuilder chroot as part of the package build. - as part of the upgrade, the Upstart maintainer script gets called which calls "initctl version" crucially *before* ischroot gets called. - at this stage an upstart session now exists for the chroot on the host system. - the version of upstart gets upgraded on the host system (*) - the upgrade triggers a stateful re-exec. - seemingly on deserialisation, if sessions exist in the meta-data, a crash results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1199778 Title: upstart crashes if re-exec'ed with active chroot sessions To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1199778/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
