touch-packages team mailing list archive

[Launchpad Bug Tracker <1174272@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package upstart - 1.12.1-0ubuntu4.2

---------------
upstart (1.12.1-0ubuntu4.2) trusty; urgency=medium

  * Safe guard against SESSIONTYPE-less sessions. (LP: #1343905)

upstart (1.12.1-0ubuntu4.1) trusty; urgency=medium

  [ James Hunt ] LP: #1317727
  * debian/manpages/upstart-events.7: Correction for 'rotate-logs'.
  * debian/upstart.cron.daily: Specify full path to initctl.
  * init/man/init.8: Add missing information on '--chroot-sessions'.
  * debian/upstart.apport: Sort system and session jobs.

  [ Iain Lane ]
  * xsession-init: Set $GNOME_DESKTOP_SESSION_ID if we are launching a
    gnome-session session. Some applications (Qt4) require this to be set to
    any value to detect the environment in use. It was historically set by
    gnome-session but now this is no longer the root of the session so not all
    user processes are guaranteed to have it. (LP: #1305294)

  [ Dimitri John Ledkov ]
  * Cherrypick reboot command fix to not process REBOOTCOMMAND argument
    when in runlevels 2-5 and without using force flag. (LP: #1174272)
 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>   Fri, 18 Jul 2014 10:27:27 +0100

** Changed in: upstart (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1174272

Title:
  'reboot now' reverting to maintenance mode, instead of rebooting

Status in Upstart:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * reboot(8) command has behaviour different from the documented one,
  in particular when passing optional REBOOTCOMMAND argument, whilst not
  in runlevel 0 or 6 and without passing --force, shutdown(8) was not
  invoked with the appropriate arguments. Actual behaviour was dropping
  to runlevel 1, instead of the expected reboot.

  [Test Case]

   * Whilst booted normally to runlevel 2, after executing:

     $ sudo reboot please

   * machine should complete reboot.

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