@Gruber
No I don't think my xorg.conf is involved.
Now on the ps -aux output: I can confirm that when X startup is 'sane' (works first time around) then the vt7 param is indeed passed. If X ends up on vt2, it is not:
/root$ ps -ef | grep X | tee -a vts.log
root 1274 1252 0 16:57 tty2 00:00:02 /usr/bin/X :1 -br -verbose -auth /var/run/gdm/auth-for-gdm-nPB6b1/database -nolisten tcp
However, I'd be very interested to found out exactly _where_ the necessary vty param comes from, because I can't find a reference to it from upstart (/etc/init), nor can I see it being passed directly or indirectly to gdm:
@Gruber
No I don't think my xorg.conf is involved.
Now on the ps -aux output: I can confirm that when X startup is 'sane' (works first time around) then the vt7 param is indeed passed. If X ends up on vt2, it is not:
/root$ ps -ef | grep X | tee -a vts.log gdm/auth- for-gdm- nPB6b1/ database -nolisten tcp
root 1274 1252 0 16:57 tty2 00:00:02 /usr/bin/X :1 -br -verbose -auth /var/run/
However, I'd be very interested to found out exactly _where_ the necessary vty param comes from, because I can't find a reference to it from upstart (/etc/init), nor can I see it being passed directly or indirectly to gdm:
`- gdm-binary gdm/gdm- simple- slave --display-id /org/gnome/ DisplayManager/ Display1 gdm/gdm- session- worker gdm/gdm- session- worker gdm/gdm- simple- slave --display-id /org/gnome/ DisplayManager/ Display1 gdm/auth- for-gdm- GED924/ database -nolisten tcp vt7
| `- gdm-binary
| `- /usr/lib/
| `- /usr/lib/
| | `- /usr/lib/
| `- /usr/lib/
| `- /usr/bin/X :0 -br -verbose -auth /var/run/
Hope someone can point me in the right direction so I can have a stab at a fix