Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=463728.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: upstart (Fedora)
Status: In Progress = Won't Fix
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Branch linked: lp:ubuntu/upstart
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ok, so here's my current working theory on this bug.
When you are in single-user mode, the rcS-default job is running: this
is what runs sulogin. Once sulogin finishes, this then runs
telinit to switch to the default runlevel.
If you type reboot inside the sulogin shell, that will run
shutdown
Though also thinking about it, we really want the rc-default job to be
run - and therefore the stopping event to know why it stopped ;)
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of
Moving the telinit code into post-stop and checking $UPSTART_EVENT looks
like it does the trick
** Changed in: upstart (Ubuntu)
Status: Confirmed = In Progress
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug
Actually, we have to check $1 as well - $UPSTART_EVENT is not reset if
the stop command is by exit, so it still contains runlevel because
that's what started the job.
if [ ${UPSTART_EVENT} = runlevel -a $1 != S ]
then
exit 100
fi
Seems right
--
entering
100 being for debugging, obv
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This bug was fixed in the package upstart - 0.3.10-2
---
upstart (0.3.10-2) karmic; urgency=low
* debian/upstart.postinst: Use telinit u to re-exec, rather than
kill just in case it's not Upstart that's running. LP: #92177.
* debian/event.d/system-services/tty*: Run getty in
Fedora bug looks like the same thing, just expressed differently
** Bug watch added: Red Hat Bugzilla #463728
https://bugzilla.redhat.com/show_bug.cgi?id=463728
** Also affects: upstart (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=463728
Importance: Unknown
Status:
** Changed in: upstart (Fedora)
Status: Unknown = In Progress
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
8.04.2 remote use of reboot -f leaves the user in server mode having to
make a journey to the on off button or find someone who can
not great when it is a test firewall but better than it being in
production
--
entering 'reboot' at the rescue console brings up gdm
In Ubuntu 8.10, the wording has been changed to reflect the actual
beahvior. It now reads press ctrl-D to resume boot. I don't think this
is a proper solution to the problem. IMHO there _have_ to be a way to
properly shutdown without continuing the boot. E.g. one might want to
make a copy of the
Still there in Ubuntu 8.04.1. I think its especially bad because fsck
tells me to reboot (I guess that's recommended after root file system
repair) and when I type reboot it starts up everything (which must be
not recommended for the same reasons).
--
entering 'reboot' at the rescue console
No, this is not printed. And in fact, ctrl-D won't reboot, either.
There is really, really no way to properly reboot at this stage.
reboot -f is _not_ a proper workaround, since it will not umount/sync
filesystems properly.
BTW: This bug still exists in 8.04rc. :-(
--
entering 'reboot' at the
Isn't it printed on the screen after dropping to maintenance console,
that after doing maintenance you have to press Control+D to reboot?
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of
Need to figure out what's causing this
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: upstart (Ubuntu)
Assignee: Scott James Remnant (keybuk) = (unassigned)
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Seeing the same in Gutsy. It does not start to shutdown after starting
gdm.
--
entering 'reboot' at the rescue console brings up gdm
https://bugs.launchpad.net/bugs/66002
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: upstart (Ubuntu)
Importance: Low = High
--
entering 'reboot' at the rescue console brings up gdm
https://launchpad.net/bugs/66002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Oh, right, the gettys would be running and thus save the system from
shutdown -- ho-hum :)
--
entering 'reboot' at the rescue console brings up gdm
https://launchpad.net/bugs/66002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Actually, sorry, scratch that last -- the reboot event can be issued
when processes are in start
--
entering 'reboot' at the rescue console brings up gdm
https://launchpad.net/bugs/66002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Caused by the fact that the rcS job is still running, reboot issues the
shutdown event but that won't actually complete until rcS and then rc2
have finished ... you'll probably find that the moment it hits gdm, it
starts shutting down again?
** Changed in: upstart (Ubuntu)
Importance:
Known, use reboot -f
--
entering 'reboot' at the rescue console brings up gdm
https://launchpad.net/bugs/66002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
no, I had to select 'reboot' at the gdm prompt.
Perhaps I was to fast pressing reboot, however (30seks).
--
entering 'reboot' at the rescue console brings up gdm
https://launchpad.net/bugs/66002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
26 matches
Mail list logo
