After upgrading from edgy to feisty, no login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
I have a Dapper machine I was upgrading to edgy, then feisty, then gutsy. This problem showed up after I dist-upgraded from edgy to feisty, then rebooted.
The symptom is no login prompt being presented. The last line printed to the console is "Running local boot scripts [OK]" (though if upstart is booting scripts concurrently, it is possible that this isn't the last line for some people, it'll be something else)
Upon reboot:
init: /etc/event.
repeated for Tty1 through 6. Looking at /etc/event.d/tty* you can see that the last two lines of these files are:
respawn
/sbin/getty 38400 tty1exec /sbin/getty 38400 tty1
There are three problems here:
1) the last line is repeated without a newline
2) the first repetition doesn't contain exec
3) it shouldn't be repeated
This was with a brand new install of dapper, nothing was modified by hand. I was doing this specifically to test for problem cases before upgrading dapper to hardy on semi-production machines.
This is on an amd64 machine
This is related, but not an exact duplicate of https:/
I say it is not a duplicate because this seems to only happen on an upgrade from edgy to feisty, and the problem with the ttyX files is different.
I should also add that this is fixed by changing the last two lines of these event.d files to:
respawn
/sbin/getty 3840 tty1
(or tty<whatever>)