** Changed in: upstart
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode, instead of r
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/
** Changed in: upstart
Status: In Progress => 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/1174272
Title:
'reboot now' reverting to maintenance mode, instead of rebooting
To ma
reboot now works OK too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode, instead of rebooting
To manage notifications about this bug go to:
h
Thanks for implementing this fix. I have not had time to test it myself
yet
I do notice however that verification-needed has been removed already,
on the basis of 'reboot please' working. What about 'reboot now' -- does
this also work as expected? Remember that this bug report was
specifically ope
`$ 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
Bugs, which is subscribed to Ubuntu.
https://bugs.la
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
--
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:
** Branch linked: lp:ubuntu/trusty/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode, instead of rebooting
To manage notifications abou
When this fixed in 14.04 Trusty Tahr for 14.04.1 (24 July)?
Many "critical" bugs on ReleaseNotes Trusty Tahr page don't fixed presently:
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues
Installation bugs too:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066480
https://bugs
** 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/1174272
Title:
'reboot now' reverting to maintenance mode, instead of rebooting
To manage notifications about this
This bug was fixed in the package upstart - 1.12.1-0ubuntu10
---
upstart (1.12.1-0ubuntu10) utopic; urgency=medium
* Revert spurious +x -> -x change on daily upstart cron file.
* Cherrypick reboot command fix to not process REBOOTCOMMAND argument
when in runlevels 2-5 and with
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => In Progress
** Changed in: upstart
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: upstart
Importance: Undecided => High
** Description changed:
[Impa
** Branch linked: lp:~xnox/upstart/reboot-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode
To manage notifications about this bug go to:
h
** Description changed:
- A forum thread has been opened first, describing the problem. For
- reference, that forum thread can be found here:
- http://ubuntuforums.org/showthread.php?t=2139160&p=12624806
+ [Impact]
- Problem is described below:
+ * reboot(8) command was behaviour different fro
** Changed in: upstart (Ubuntu)
Importance: Undecided => Critical
** Changed in: upstart (Ubuntu)
Assignee: Phillip Susi (psusi) => Dimitri John Ledkov (xnox)
** Also affects: upstart (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Trusty)
** Branch linked: lp:~psusi/ubuntu/utopic/upstart/fix-reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode
To manage notifications about th
You are right, the man page does say it is only used with --force.
Interestingly, it seems the reboot command from the old sysvinit package
completely ignored this argument, not using it even with --force,
despite the man page saying so. Upstart's reboot command did the same
thing in precise. It
There is no need to keep commenting on this: once again, it is not a
bug, the reboot command does not take a time argument.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now'
This also affects 13.10 (Saucy Salamander). Extremely aggravating,
especially on a remote headless server. (Thus no screenshot.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot
Trusty is borked.
** Attachment added: "reboot_now_hang.png"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1174272/+attachment/4075567/+files/reboot_now_hang.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Changed in: upstart (Ubuntu)
Status: Invalid => 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/1174272
Title:
'reboot now' reverting to maintenance mode
To manage notification
same here - reboot now worked for me for years... now doesnt work after
upgrade to 13.04 desktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance m
reboot with no arguments reboots now. shutdown -h powers off, and
shutdown -r reboots, with an optional time argument. As always, Read
The Friendly Manual ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I just performed a fresh install of Ubuntu Server 13.04 i386. The
initial reboot was fine, but using "sudo reboot -h now" caused this to
happen. From single-user mode root I was able to run "shutdown -h now"
and it booted back up fine.
So, the preferred method is just "sudo reboot" from here on ou
It was an error in that release of upstart that has been corrected.
Classic sysvinit shutdown has behaved this way because that is how unix
systems have always done it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-40-generic-pae i686)
root@host1:~# reboot now
The system is going down for reboot NOW!
Welcome to Ubuntu 13.04 (GNU/Linux 3.9.0-030900rc8-generic i686)
root@host2:~# reboot now
The system is going down to maintenance mode NOW!
(the same for shutdown)
That is the point though. If retaining conventions of the past is such an
important factor, then I wonder why I could (until recently, at least) issue
'shutdown now' or 'reboot now' on any machine running debian/ubuntu, and it
would complete a full power-off, or reset, respectively, each time...
Because that is how shutdown has worked for 20+ years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'reboot now' reverting to maintenance mode
To manage notifications about this bug
Usage: shutdown [OPTION]... TIME [MESSAGE]
Bring the system down.
Usage: reboot [OPTION]...
Reboot the system.
Just out of curiousity. Why no 'time' for reboot? These commands are
similar in purpose, so one would expect that level of consistency
between them
I'll also be happy go back on my prev
"shutdown now" is supposed to switch to single-user mode (see bug
1065851).
"reboot now" is invalid - the shutdown command takes a time parameter
(such as "now"), but the reboot command does not (see the man page). By
specifying "reboot now" you are asking the system to reboot by running
the "now
Also happening to me - same symptoms. Updated server to 13.04.
MOTD still says "New release '13.04' available"
"reboot" command on its own works fine - it displays the following:
Rather than invoking init scripts through /etc/init.d, use ther service(8)
utility, e.g. service S35networking stop
ini
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
'r
Actually just exoerienced this same symptom on a machine running
12.04.2, on 'shutdown now' went into maintenance console. Is this normal
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
34 matches
Mail list logo
