Haines Brown via Dng <dng@???> writes:
> Off hand no luck using vitual keyboard: a) I don't use a desktop
> enviropnment. The Florcence application is not available for
> installation. matchbox-keyboard is for touchscreen devices.
> maliit-keyboard need Malit Frameworl/
The xvkbd package provides a virtual keyboard for X (there are
doubtlessly others, that just the first I found).
[...]
> It was suggested I log into a text console and run it from there. I normally
> run things from a mlterm console. That is not a text console. In any case,
> dong Clt-Alt F2-6 merely blanked my scree and did not raise a console.
> Perhaps that is a useful clue.
Not really, It just suggests that your init/ system is not configured to provide
text consoles. Mine is because I always login via text console and then
start X manually (most of the time).
> I ran it under strace and it returned:
>
> ...
> close(4) = 0
> lseek(3, 0, SEEK_SET) = 0
> write(3, "\0\0\0\0\1\0\1\0\0\0\0\0", 12) = 12
> close(3) = 0
> --- SIGCONT {si_signo=SIGCONT, si_code=SI_KERNEL} ---
> unlink("/tmp/lltmpr68ql6") = 0
> clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, 0x7fffff7b05a0) = 0
> write(1, "\33[24;1H\33[?1049l\33[23;0;0t\r\33[?1l\33>", 32) = -1 EIO (Input/output error)
> ioctl(1, TCGETS, 0x7fffff7b0580) = -1 EIO (Input/output error)
> ioctl(1, SNDCTL_TMR_STOP or TCSETSW, {c_iflag=BRKINT|IGNPAR|ICRNL|IXON,
> c_oflag=NL0|CR0|TAB0|BS0|VT0|FF0|OPOST|ONLCR, c_cflag=B38400|CS8|CREAD,
> c_lflag=ISIG|ICANON|ECHO|ECHOE|ECHOK|IEXTEN|ECHOCTL|ECHOKE, ...})
> = -1 EIO (Input/output error)
> newfstatat(1, "", {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x13), ...}, AT_EMPTY_PATH) = 0
> write(1, "signal 1: HANGUP\n", 17) = -1 EIO (Input/output error)
> newfstatat(0, "", {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x13), ...}, AT_EMPTY_PATH) = 0
> read(0, "", 1024) = 0
> write(1, "\377", 1) = -1 EIO (Input/output error)
> exit_group(1) = ?
> +++ exited with 1 +++
This shows the program exiting/ being terminated by a hangup signal
after losing access to its tty. That's not helpful. You can run it in
one terminal and use strace -p <pid> in another to get a system call
trace from it. It should cover the "weird input handling" situation you
described.