[opensuse-factory] remote logins have strange keyboard setting... mostly latin, but not sure what? after fact update
I upgraded and rebooted my server this yesterday and have some oddness when I login to it remotely now -- at least until I type "reset". The most noticeable feature is some keys on my keyboard are remapped to some foreign keys...but NOT that many. Specifically, on the left, tilda and at sign ~@ => ߧ On the left side it's the brack/brace /backslash and vertical bar -> []\ => ÄÜÖ {}| => äüö ---- My keyboard/terminal is still set to a 'linux' terminal, and locale settings look like: LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ---- If I type "reset", the terminal goes back to "normal". If I start an X11 app like gvim from the terminal BEFORE I reset it, the X11 app catches the weird characters as well. But if I type 'reset' (ncurses-utils-5.9 in /usr/bin/), it resets the term and then if I launch an X util, it's "normal". Anyone have an idea about what might be going on? Nothing in the environment before/after seems strange (this is how a pre-reset v. post reset looks from diff: GPG_TTY=/dev/ttyp2 ö GPG_TTY=/dev/ttyp1 HISTFILE=/home/law/.histIshtar_ttyp2 ö HISTFILE=/home/law/.histIshtar_ttyp1 PIPESTATUS=(Ä0Ü="0" Ä1Ü="0") ö PIPESTATUS=(Ä0Ü="0" Ä1Ü="0" Ä2Ü="0") PPID=79754 ö PPID=78347 SSH_AUTH_SOCK=/tmp/ssh-2FyrkLSyYB/age ö SSH_AUTH_SOCK=/tmp/ssh-lwihqyNyKw/age SSH_CLIENT='192.168.4.12 49606 22' ö SSH_CLIENT='192.168.4.12 49605 22' SSH_CONNECTION='192.168.4.12 49606 19 ö SSH_CONNECTION='192.168.4.12 49605 19 SSH_TTY=/dev/ttyp2 ö SSH_TTY=/dev/ttyp1 TTY=/dev/ttyp2 ö TTY=/dev/ttyp1 TTY_NAME=ttyp2 ö TTY_NAME=ttyp1 tty=/dev/ttyp2 ö tty=/dev/ttyp1 Even though the chars are displaying 'funny', they still seem to have their normal meaning and function. If I use a windows dumb term to ssh in, I don't see the problem, but it doesn't know how to switch charsets or do whatever "securecrt" or xterm is doing... I tried it from a different computer... same thing. it's definitely an update on the server that is causing this... its very weird. but fortunately not that difficult to get around... Any ideas? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2013-06-02 03:42, Linda Walsh wrote:
Nothing in the environment before/after seems strange (this is how a pre-reset v. post reset looks from diff: GPG_TTY=/dev/ttyp2 ö GPG_TTY=/dev/ttyp1 SSH_TTY=/dev/ttyp2 ö SSH_TTY=/dev/ttyp1 TTY=/dev/ttyp2 ö TTY=/dev/ttyp1 TTY_NAME=ttyp2 ö TTY_NAME=ttyp1 tty=/dev/ttyp2 ö tty=/dev/ttyp1
ttyp2 is strange. Why would you want to go back to ancient BSD ptys? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
On Sunday 2013-06-02 03:42, Linda Walsh wrote:
Nothing in the environment before/after seems strange (this is how a pre-reset v. post reset looks from diff: GPG_TTY=/dev/ttyp2 ö GPG_TTY=/dev/ttyp1 SSH_TTY=/dev/ttyp2 ö SSH_TTY=/dev/ttyp1 TTY=/dev/ttyp2 ö TTY=/dev/ttyp1 TTY_NAME=ttyp2 ö TTY_NAME=ttyp1 tty=/dev/ttyp2 ö tty=/dev/ttyp1
ttyp2 is strange. Why would you want to go back to ancient BSD ptys?
---- Not thought it was strange. Go back? What else would they have looked like...? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2013-06-02 19:50, Linda Walsh wrote:
Jan Engelhardt wrote:
On Sunday 2013-06-02 03:42, Linda Walsh wrote:
Nothing in the environment before/after seems strange (this is how a pre-reset v. post reset looks from diff: GPG_TTY=/dev/ttyp2 ö GPG_TTY=/dev/ttyp1 SSH_TTY=/dev/ttyp2 ö SSH_TTY=/dev/ttyp1 TTY=/dev/ttyp2 ö TTY=/dev/ttyp1 TTY_NAME=ttyp2 ö TTY_NAME=ttyp1 tty=/dev/ttyp2 ö tty=/dev/ttyp1
ttyp2 is strange. Why would you want to go back to ancient BSD ptys?
Not thought it was strange. Go back? What else would they have looked like...?
Every sane system would likely use Unix98 ptys aka /dev/pts/N. (Not that I think it makes a difference with regard to the "Latin issue", but it's always funny to see how you disconfigure your system in various ways.) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
Every sane system would likely use Unix98 ptys aka /dev/pts/N. (Not that I think it makes a difference with regard to the "Latin issue", but it's always funny to see how you disconfigure your system in various ways.)
Huh...interesting... thanks for pointing this out. Since in looking into it...
du .hist* 14908 .histIshtar_pts 4 .histIshtar_tty1 12 .histIshtar_ttyp0 12 .histIshtar_ttyp1 4 .histIshtar_ttyp2 4 .histIshtar_ttyp3 4 .histIshtar_ttyp4 8 .histIshtar_ttyp5 4 .histIshtar_ttyp6 4 .hist_ 4 .history
Seems like it's something peculiar to this latest reboot. I have a mount for /dev/pts in my /etc/fstab, but apparently it didn't happen because /dev/pts wasn't created. Hrumph. Some new boot frobnobulication. hhmmmm... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Linda Walsh wrote:
Jan Engelhardt wrote:
Every sane system would likely use Unix98 ptys aka /dev/pts/N.
>> (Not that I think it makes a difference with regard to the "Latin <<<<<< >> issue", <<<<<<
It does! creating /dev/pts and mounting it, now remote logins goto /dev/pts/XX again, and no more funny characters! That's weird! Wonder what's up w/ "/dev/ttypxx"... Interesting. I always left those ttyp's in my kernel for compat cases, but apparently they aren't getting tested very much and can come up w/some strange settings. Double interesting... something had to have deleted it on boot, since a new mount of "devtmpfs" includes it. Hmmm... In addition to that mystery -- still don't know what initialization is missing from the /dev/ttyp case that is likely causing it's acting strange, but if it hadn't been config'ed into my kernel, I wouldn't have been able to remotely log in, and that would have been a real drag... (can't sit in spare room where server is, for very long... starts to hurt back and wrists.... -- which is why I always prefer sshd to come up no matter what, so I can manage the sys from living room where my desktop is)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 02/06/13 16:04, Jan Engelhardt escribió:
On Sunday 2013-06-02 19:50, Linda Walsh wrote:
Jan Engelhardt wrote:
On Sunday 2013-06-02 03:42, Linda Walsh wrote:
Nothing in the environment before/after seems strange (this is how a pre-reset v. post reset looks from diff: GPG_TTY=/dev/ttyp2 ö GPG_TTY=/dev/ttyp1 SSH_TTY=/dev/ttyp2 ö SSH_TTY=/dev/ttyp1 TTY=/dev/ttyp2 ö TTY=/dev/ttyp1 TTY_NAME=ttyp2 ö TTY_NAME=ttyp1 tty=/dev/ttyp2 ö tty=/dev/ttyp1
ttyp2 is strange. Why would you want to go back to ancient BSD ptys?
Not thought it was strange. Go back? What else would they have looked like...?
Every sane system would likely use Unix98 ptys aka /dev/pts/N. (Not that I think it makes a difference with regard to the "Latin issue", but it's always funny to see how you disconfigure your system in various ways.)
I wonder how she ended there... systemd will mount /dev/pts ..it is a fatal error if systemd cannot mount it for whatever reason... another good question is why the kernel still has CONFIG_LEGACY_PTYS=y when nothing should be using that ever.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez wrote:
El 02/06/13 16:04, Jan Engelhardt escribió:
Every sane system would likely use Unix98 ptys aka /dev/pts/N. (Not that I think it makes a difference with regard to the "Latin issue", but it's always funny to see how you disconfigure your system in various ways.)
(what was even more funny is that it really was the cause for the Latin issue; I think the older style terms weren't being initialized properly, since in every case, typing 'reset' on the terminal to reset the tty state set them back to normal.
I wonder how she ended there... systemd will mount /dev/pts ..it is a fatal error if systemd cannot mount it for whatever reason...
---- I don't think systemd ever made it up...I had brought up the computer from 'S' by hand...not the first time since the systemd début.
another good question is why the kernel still has CONFIG_LEGACY_PTYS=y when nothing should be using that ever..
---- I never took it out? Unless something is deprecated, or I know all the things that use it, I tend to leave legacy alone -- it tends to cause less problems and tends to provide more stability. Anyway, I assure you I didn't delete the pts directory -- can't say for sure, but I thought the basic linux devtmpfs, had it precreated on boot(?). I also seem to be missing my alt-console tty's can't ALT-TAB to other consoles. Wouldn't have bothered to mention that except it seems in this case, I'm not the only one with that problem. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Cristian Rodríguez -
Jan Engelhardt -
Linda Walsh