I can confirm that the code for the upstart jobs in 14.04 behaves as you
describe. However, this seems to be the first time since 14.04
released, two years ago, that someone has noticed this behavior and
considered it to warrant a bug report.
While switching to runlevel 1 and back *should* restore the consoles,
this is not at all a common maintenance operation. Ubuntu users will
normally reboot instead of switching between runlevels in this manner.
Added to this that you have marked this bug as 'medium' severity, thus
meaning that it does not rise to the level of a stable release update;
and the fact that fixing this in 14.04 would be non-trivial; I am
declining this bug as 'wontfix'.
For Ubuntu 16.04, consoles are implemented differently via systemd. If
you see any bugs in the handling of runlevel switches with systemd, it
would be useful to know this so that we might fix them before 16.04 GA.
** Package changed: ubuntu => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557990
Title:
[upstart] console access of the server is lost when trying to change
runlevel 3 from runlevel 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1557990/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
