[OpenIndiana-discuss] OI and console switching

[Jim Klimov]

Hello all,

   I tried to enable the vtdaemon (and vt[23456]) services on the
oi_151a5 laptop, and found that (Ctrl+)Alt+F# keys don't switch
me to other text consoles. From X11 I can use Ctrl+Alt+F1 to get
into the text mode, however there is no console text nor any
chance to get out of this "console" back into X11 nor blindly
type anything, so I can only poweroff and poweron the laptop
with the power button (no reset). This is consistent with my
recent attempts at suspend-resume which also left me at unusable
text mode. I also tried GNOME user switching, which did present
a login screen, but led me to a similarly unusable system when I
entered the same user credentials as the already-running session.

   Does anyone else see such behavior? Do multiple text or X
consoles work for other people in recent OI builds?

Details:

   In "ps" I see that these vt login programs are running:

admin at nbofh:~$ ps -ef | grep vt
     root  9938    10   0 13:09:49 vt/4        0:00 /usr/lib/saf/ttymon 
-g -d /dev/vt/4 -l console -m ldterm,ttcompat -h -p nbofh v
     root  9962    10   0 13:09:49 vt/2        0:00 /usr/lib/saf/ttymon 
-g -d /dev/vt/2 -l console -m ldterm,ttcompat -h -p nbofh v
    admin 10362 10361   1 13:10:56 vt/7        0:25 /usr/bin/Xorg :0 
-nolisten tcp -br -auth /tmp/gdm-auth-cookies-Rmaapu/auth-for-
     root  9951    10   0 13:09:49 vt/5        0:00 /usr/lib/saf/ttymon 
-g -d /dev/vt/5 -l console -m ldterm,ttcompat -h -p nbofh v
     root 10094    10   0 13:10:02 vt/6        0:00 /usr/lib/saf/ttymon 
-g -d /dev/vt/6 -l console -m ldterm,ttcompat -h -p nbofh v
     root  9964    10   0 13:09:49 vt/3        0:00 /usr/lib/saf/ttymon 
-g -d /dev/vt/3 -l console -m ldterm,ttcompat -h -p nbofh v
     root  9896    10   0 13:09:38 vt/1        0:00 /usr/lib/vtdaemon -k 
-c 16

   As the laptop is currently in X11, the 7th console is properly
owned by the non-root user "admin":

admin at nbofh:~$ ls -la /dev/vt
total 10
drwxr-xr-x  20 root  sys        0 2012-10-27 12:51 .
drwxr-xr-x 263 root  sys      263 2012-10-27 12:51 ..
crw-------   1 root  root 110,  0 2012-10-27 12:53 0
crw-------   1 root  root 110,  1 2012-10-27 12:53 1
crw-------   1 root  root 110, 10 2012-10-27 12:53 10
crw-------   1 root  root 110, 11 2012-10-27 12:53 11
crw-------   1 root  root 110, 12 2012-10-27 12:53 12
crw-------   1 root  root 110, 13 2012-10-27 12:53 13
crw-------   1 root  root 110, 14 2012-10-27 12:53 14
crw-------   1 root  root 110, 15 2012-10-27 12:53 15
crw--w----   1 root  tty  110,  2 2012-10-27 13:09 2
crw--w----   1 root  tty  110,  3 2012-10-27 13:09 3
crw--w----   1 root  tty  110,  4 2012-10-27 13:09 4
crw--w----   1 root  tty  110,  5 2012-10-27 13:09 5
crw--w----   1 root  tty  110,  6 2012-10-27 13:10 6
crw--w----   1 admin tty  110,  7 2012-10-27 12:53 7
crw-------   1 root  root 110,  8 2012-10-27 12:53 8
crw-------   1 root  root 110,  9 2012-10-27 12:53 9
lrwxrwxrwx   1 root  root       1 2012-10-27 12:53 active -> 7
lrwxrwxrwx   1 root  root       0 2012-10-27 13:10 console_user -> 7

   On older (SXCE) systems I'm pretty sure virtual terminals
worked as expected. At least,  the default text console did
present me with a randomly picked vt[23456] greeting, while
the one I see now is the default (vt1) greeting - which may
be a symptom or the culprit.

   I did also try to disable vtdaemon security so as to allow
the unprivileged user to use any console, no luck.

Ideas (or confirmations/disprovals) are welcome,
//Jim Klimov