global environment table is not serialised

Bug #1238078 reported by James Hunt on 2013-10-10
This bug affects 15 people
Affects Status Importance Assigned to Milestone
James Hunt
upstart (Ubuntu)

Bug Description

Calls to "initctl set-env -g" will not persist across a re-exec since the global environment table is not being serialised.

Related branches

James Hunt (jamesodhunt) on 2013-10-10
Changed in upstart:
importance: Undecided → High
Steve Langasek (vorlon) on 2013-10-10
Changed in upstart (Ubuntu):
importance: Undecided → High
Revision history for this message
James Hunt (jamesodhunt) wrote :

This may explain bug 1234731.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upstart (Ubuntu):
status: New → Confirmed
James Hunt (jamesodhunt) on 2013-10-11
Changed in upstart:
assignee: nobody → James Hunt (jamesodhunt)
James Hunt (jamesodhunt) on 2013-10-15
Changed in upstart:
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package upstart - 1.11-0ubuntu1

upstart (1.11-0ubuntu1) trusty; urgency=low

  [ Dmitrijs Ledkovs ]
  * Run as much test-suites as possible, before exiting with failure.

  [ James Hunt ]
  * New upstream release.
    - the global environment is now serialized on re-exec. LP: #1238078.
    - fixes support for upstart-file-bridge detecting directory creation.
      LP: #1221466.
    - Fixes upstart user session to not override the user's configured
      umask. LP: #1240686.
    - Makes the session init available on the session dbus.
      LP: #1203595, #1235649.

  [ Steve Langasek ]
  * Document the authoritative Vcs branch in debian/control.
  * Update Standards-Version to 3.9.5, no changes required.
 -- James Hunt <email address hidden> Fri, 15 Nov 2013 13:16:56 +0000

Changed in upstart (Ubuntu):
status: Confirmed → Fix Released
James Hunt (jamesodhunt) on 2014-04-15
Changed in upstart:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers