I took a stab at fixing this by cherry-picking, but was hitting
segfaults in the test suite and ran out of time to resolve this. Now
that 13.10 is out, it's even more unlikely that I'll have time to get to
it. So I'm marking this bug as 'wontfix'. I've pushed my work-in-
progress branch to lp:~v
** Branch linked: lp:~jamesodhunt/ubuntu/saucy/upstart/1.10
--
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 notifica
** Changed in: upstart
Status: Fix Committed => Fix Released
--
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
This bug was fixed in the package upstart - 1.9.1-0ubuntu3
---
upstart (1.9.1-0ubuntu3) saucy; urgency=low
* Fix stateful re-exec with multiple stale chroot sessions (LP: #1199778)
-- Dmitrijs LedkovsSat, 20 Jul 2013 00:17:07
+0100
** Changed in: upstart (Ubuntu Saucy)
This is still happening with 1.9.1-0ubuntu2. Trivial reproducer:
15:10 < infinity> schroot (with overlay)
15:10 < infinity> initctl show-config (in chroot)
15:10 < infinity> exit chroot
15:10 < infinity> sudo telinit u
15:10 < infinity> Boom.
15:10 < infinity> Not 100%, though. I had to try a fe
This bug was fixed in the package upstart - 1.9.1-0ubuntu2
---
upstart (1.9.1-0ubuntu2) saucy; urgency=low
[ Dmitrijs Ledkovs ]
* Upload to saucy.
[ James Hunt ]
* Fix stateful re-exec with active chroot sessions (LP: #1199778)
[ Colin Watson ]
* Alternatively try new an
** Branch linked: lp:ubuntu/upstart
--
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
** Changed in: upstart
Status: In Progress => Fix Committed
** Also affects: upstart (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Saucy)
Importance: High
Assignee: Dmitrijs Ledkovs (xnox)
Status: In Progress
--
You received t
** Changed in: upstart
Status: New => In Progress
** Changed in: upstart (Ubuntu)
Status: New => In Progress
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Failure message, for reference:
conf.c:1510: Assertion failed in conf_source_deserialise_all:
NIH_LIST_EMPTY (conf_sources)
--
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 cras
** Branch linked: lp:~jamesodhunt/upstart/bug-1199778
--
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
Correction to the process above: a session only gets created when a job
is queried so a maintainer script is probably invoking
status/start/stop/restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
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
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
--
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 not
14 matches
Mail list logo
