*** This bug is a duplicate of bug 104038 ***
https://bugs.launchpad.net/bugs/104038
I can confirm the bug occuring on two distinct machines (a desktop and a
Toshiba laptop) after upgrading from Edgy to Feisty (actually this was
two consecutive upgrades: Dapper - > Edgy, Edgy -> Feisty, with problem-
fixing between them - I've rebooted and verified that installation of
Edgy works properly before proceeding with the next upgrade).
Here's the contents of two sample files:
[EMAIL PROTECTED] ~ 11:34:26]$cat /etc/event.d/tty1
# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
/sbin/getty 38400 tty1exec /sbin/getty 38400 tty1
[EMAIL PROTECTED] ~ 11:34:33]$cat /etc/event.d/tty2
# tty2 - getty
#
# This service maintains a getty on tty2 from the point the system is
# started until it is shut down again.
start on runlevel 2
start on runlevel 3
stop on runlevel 0
stop on runlevel 1
stop on runlevel 4
stop on runlevel 5
stop on runlevel 6
respawn
/sbin/getty 38400 tty2exec /sbin/getty 38400 tty2
When I change tty1 contents to the following, login on tty1 starts working:
# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
exec /sbin/getty 38400 tty1
--
can't login because of bug in /etc/event.d/ttyn
https://bugs.launchpad.net/bugs/104306
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
