no virtual terminals on lucid

This implies that the runlevel/rc scripts have not yet been run.

Could you reboot, I assume you end up in gdm as usual? From there, run "sudo initctl list" and attach the output

Thanks

icon@compaq-laptop:~$ sudo initctl list
[sudo] password for icon:
alsa-mixer-save stop/waiting
avahi-daemon start/running, process 818
mountall-net stop/waiting
nmbd start/running, process 1530
rc stop/waiting
rpc_pipefs start/running
rsyslog start/running, process 568
tty4 stop/waiting
udev start/running, process 415
upstart-udev-bridge start/running, process 375
ureadahead-other stop/waiting
apport stop/waiting
console-setup stop/waiting
hwclock-save stop/waiting
irqbalance stop/waiting
plymouth-log stop/waiting
smbd start/running, process 413
tty5 stop/waiting
statd start/running, process 736
atd stop/waiting
dbus start/running, process 743
failsafe-x stop/waiting
plymouth stop/waiting
portmap start/running, process 585
ssh start/running, process 768
control-alt-delete stop/waiting
hwclock stop/waiting
network-manager start/running, process 830
usplash stop/waiting
module-init-tools stop/waiting
cron stop/waiting
mountall stop/waiting
acpid stop/waiting
plymouth-stop stop/waiting
rcS
stop/waiting

ufw
start/running

mounted-varrun stop/waiting
rc-sysinit stop/waiting
anacron stop/waiting
tty2 stop/waiting
udevtrigger stop/waiting
mounted-dev stop/waiting
tty3 stop/waiting
udev-finish stop/waiting
hostname stop/waiting
kdm start/running, process 756
mountall-reboot stop/waiting
gssd stop/waiting
mountall-shell stop/waiting
mounted-tmp stop/waiting
network-interface (lo) start/running
network-interface (pan0) start/running
network-interface (eth0) start/running
network-interface (eth1) start/running
plymouth-splash stop/waiting
tty1 stop/waiting
udevmonitor stop/waiting
dmesg stop/waiting
network-interface-security start/running
networking stop/waiting
procps stop/waiting
tty6 stop/waiting
idmapd start/running, process 829
ureadahead start/running, process 351

Thanks.

Please add "--verbose" to your kernel command-line, then after booting
attach /var/log/boot.log /var/log/syslog and /var/log/messages

Scott
--
Scott James Remnant
<email address hidden>

So as to not potentially complicate this, I should tell you that I have
edited /etc/init/tty[2-6].conf on the advice of people in ubuntu IRC
support. I changed them all to be similar to tty1.conf, adding runlevels 4
and 5:

start on runlevel [2345]
stop on runlevel [!2345]

These edits made no difference; still no tty's.

Please let me know if I should revert those edits and reattach the log files
you requested.

On Thu, 2010-04-22 at 05:52 +0000, mefisto wrote:

> Please let me know if I should revert those edits and reattach the log files
> you requested.
>
No need; those edits are perfectly fine.

Thanks for the logs - these show that the "lo" device never comes up
(but I see the process that should run "ifup lo").

Could you attach your /etc/network/interfaces file for me?

Scott
--
Scott James Remnant
<email address hidden>

The last line in /etc/network/interfaces was the problem. I commented it out
and all tty's start.

I don't really remember where I got that line from, but I think in karmic I
was trying to set default sink for pulseaudio on boot.

On Thu, 2010-04-22 at 18:43 +0000, mefisto wrote:

> The last line in /etc/network/interfaces was the problem. I commented it out
> and all tty's start.
>
Sweet - yeah, no idea what that line is trying to do but it'll certainly
break things (it stops the /etc/network/if-up.d scripts running for lo)

You could accomplish the same thing much better with an Upstart job.

Glad your problem is solved.

 status invalid

Scott
--
Scott James Remnant
<email address hidden>