So it turns out that mdz hijacked an unrelated bug; sorry zigi, your bug
that getty is started before rc.local is still valid :p
I've opened bug 98955 to track the logd problem
** Summary changed:
- Starting of the getty
+ getty started before rc.local
--
getty started before rc.local
https://
This requires new features in upstart, so it is not fesible for 7.04;
removing milestone.
** Changed in: upstart (Ubuntu)
Target: ubuntu-7.04 => None
--
getty started before rc.local
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
And I note that you deliberately ignored what edgy did -- this was a
dapper-edgy regression, not an edgy-feisty regression, so I disagree it
can be suddenly release critical at this point.
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
There's no way to fix this for 7.04
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "Ubuntu 6.10 server login prompt"
http://librarian.launchpad.net/6893723/edgy.png
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "Feisty server login prompt"
http://librarian.launchpad.net/6893735/feisty.png
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is a regression from 6.10 and should be fixed for 7.04.
** Changed in: upstart (Ubuntu)
Target: None => ubuntu-7.04
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
Confirmed in Feisty Fawn Herd 4.
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: upstart (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Confirmed
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
You can simulate this bug if you delete the kernel parameter splash
before boot.
** Attachment added: "screenshot of the bug"
http://librarian.launchpad.net/5420502/screenshot.jpg
** Description changed:
I don't know when the virtual consoles are started but for the tty1 it
is early. See
The screenshot you linked to doesn't seem to work.
Could you attach it to the bug?
** Changed in: upstart (Ubuntu)
Status: Unconfirmed => Needs Info
--
Starting of the getty
https://launchpad.net/bugs/75830
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
** Description changed:
I don't know when the virtual consoles are started but for the tty1 it
is early. See this "screenshot":
http://img224.imageshack.us/my.php?i...sc00410xs4.jpg . The user then
- doesn't know if isn't something wrong in /etc/rc.local and so the system
- is ready for logi
12 matches
Mail list logo
