[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2015-07-09 Thread Bady
** Changed in: upstart
 Assignee: Dimitri John Ledkov (xnox) = (unassigned)

-- 
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2014-07-22 Thread Launchpad Bug Tracker
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 x...@ubuntu.com   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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2014-07-18 Thread david
Hello everyone, I tested the proposed package using the test case provided
Ubuntu Trusty amd64
upstart (12.1.1-0ubuntu4.2)
machine rebooted OK, without dropping to runlevel 1

I haven't tested the package in any other ways, so i'm not sure about
regression and 'll keep verification-needed tag

-- 
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:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Committed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2014-07-18 Thread Dimitri John Ledkov
`$ sudo reboot please` now correctly reboots machine, instead of
erroneously dropping to runlevel 1.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Committed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2014-07-18 Thread david
reboot now works OK too

-- 
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:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Committed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting

2014-07-17 Thread Colin Watson
Hello Dimitri, or anyone else affected,

Accepted upstart into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/upstart/1.12.1-0ubuntu4.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: upstart (Ubuntu Trusty)
   Status: In Progress = Fix Committed

** Tags added: verification-needed

-- 
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:
  In Progress
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Trusty:
  Fix Committed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp