casper corrupts virtual consoles creation events (/etc/event.d/tty1 - tty6)

casper (1.83) feisty; urgency=low

  * Fix usplash version in Conflicts.
  * Add XS-Vcs-Bzr field to debian/control.
  * scripts/casper-bottom/25configure_init: Support for "respawn COMMAND"
    has been dropped from upstart jobs; cope with /etc/event.d/tty* using
    "respawn" plus "exec COMMAND" now instead (LP: #92928).

 -- Colin Watson <email address hidden> Mon, 19 Mar 2007 16:44:22 +0000

Feisty upgraded 'til today packages, casper1.83, but the problem still exists:
https://launchpad.net/ubuntu/+source/upstart/+bug/95210

@Flapane:

casper is used in livecd, only. You have to rebuild your livecd to use this fix. However, after Feisty is installed tty's are ok (at least for me).

@Colin Watson:

I've tested your change to scripts/casper-bottom/25configure_init (manually applied to filesystem.squashfs in Feisty Beta i386 desktop livecd), but the problem is still there. "respawn" is detected as an "unknown stanza", and you end up with no tty's when booting livecd.
I've tried removing the "respawn" line from /etc/event.d/tty*, and i got no errors and all tty's working when using casper (although no respawn, obviously), so i think there's something else needing a fix.
After installing Feisty, tty's are ok.
If you need more info or testing please let me know.

My problem is on the installed feisty, not te live one

Then it should be related to upstart. Make sure you're using the latest version.
Try modifying /etc/event.d/tty*. First, try removing the "respawn" line. That should help to get tty's working, but no respawn.
According to https://launchpad.net/upstart/main/0.3.7, the "respawn" stanza should be declared after "exec". I'm not sure if that makes a difference, but you could try it. (I tried it in casper, but it didn't work).

I can confirm that it only works on the beta live if "respawn" (without arguments) is declared after "exec".

my tty file were corrputed..
I solved changing them in
respawn
exec /sbin/getty 38400 tty1

thanks

I'm sorry, i didn't notice that my manually applied changes to 25configure_init didn't have any effect over /etc/event.d/tty*. I'm not sure how to test this, i tried using chroot dpkg -i over uncompressed filesystem.squashfs and rebuilding the cd, but still the same.
Anyway, this fix should work, thanks.

I am having the same problem on the Beta live-cd. I can test a proposed fix if my help is needed.

@Juan Pablo Salazar Bertín:
95210 is marked as a duplicate of this, but the system configuration is different: It's an installed, fully upgraded Feisty system. I've no idea of the cause, but I thought it might help to add another non-LiveCD report.

This bug bit me earlier tonight. I saw the same "unknown stanza" messages after an apt-get upgrade when I booted my formerly-working feisty partition with nosplash.

Workaround is the /etc/event.d/tty# fix described above. No further problems.

On the machine that manifested this, I would never see it unless GDM fails to start, which only happens after kernel updates, so I have no idea how long it has been lurking.

@Justin Bowes:
You're right, bug #95210 is in fact a duplicate of bug #89314, since it's an upgrade and not a LiveCD report. Thanks.