ssh: not work the "d" key

nox

Active Member
Jan 26, 2010
10
0
41
San Marino
Hello everybody,

my first post here as something strange happen here:
trhu ssh connection I cannot digit the "d" letter,
only uppercase as "D" work.

I try using putty under win and even using a linux box
with same results, so I cannot launch commands like
apt-get udate for example...

I try change keyboard layout even try using ascii table
but really cannot digit this letter!

May be this has been treat before but cannot found results
by forum search I'm sorry if I'm writing about something note.

Any suggestion about that? :(
 
Hello everybody,

my first post here as something strange happen here:
trhu ssh connection I cannot digit the "d" letter,
only uppercase as "D" work.

I try using putty under win and even using a linux box
with same results, so I cannot launch commands like
apt-get udate for example...

I try change keyboard layout even try using ascii table
but really cannot digit this letter!

May be this has been treat before but cannot found results
by forum search I'm sorry if I'm writing about something note.

Any suggestion about that? :(

do you work on a notebook and you got some function keys enabled?
 
do you work on a notebook and you got some function keys enabled?

No, just in office with my intel dual core 32bit client that, of course, able to digit the "d" key into every applications and even trhu ssh to any other server.

To give a try I used another client amd 64bit, new as installed one week ago and, of course, the keyboard work perfectly but not in putty ssh direct to the Proxmox VE 1.4 kernel 2.6.24-8-pve :confused:
 
Sounds strange. PuTTY is working here (even VNC-Console after setting the right keyboard-layout in System>Options). Have you maybe installed from a template and use some special term or encoding (which is not included in the template and so not installed out of the box in the VM now)? Have you tried with TERM=linux, LANG=en_US.UTF-8?

Greetings,
user100
 
At prompt login the key work:

PuTTY
login as: ddddd

after root login don't work :(

You have some keyboards command or suggestion file to edit?
(please that not have "d" inside, for example I can write "nano" but not "read")
 
If you have physical access to server, try a
Code:
dpkg-reconfigure console-data
with root shell

[]'s
 
After console login not work the "d" key

If you have physical access to server, try a
Code:
dpkg-reconfigure console-data
with root shell

[]'s

With a physical access to server have the same problem!

Cannot digit the "d" key even using the ALT+100 ascii code,
no way: the server buzzer reply me with a error bip.

Before login can digit everything, after root login cannot use
the "d" key so cannot digit your code...

I fear to format the server for this "little" problem only :(
 
Re: After console login not work the "d" key

With a physical access to server have the same problem!

Cannot digit the "d" key even using the ALT+100 ascii code,
no way: the server buzzer reply me with a error bip.

Before login can digit everything, after root login cannot use
the "d" key so cannot digit your code...

I fear to format the server for this "little" problem only :(

Hi,
you can try following:
create a file consolconfig on another linux-box with following content:
dpkg-reconfigure console-data
Make the file executable:
chmod +x consolconfig
scp consolconfig root@proxmox_ip

Then can you login at the proxmox-host and start the file with
./consolconfig

If that dont work, you can try to add another user with sudo-rights with the same procedure.

Udo
 
Re: After console login not work the "d" key

Hi,
you can try following:
create a file consolconfig on another linux-box with following content:
dpkg-reconfigure console-data
Make the file executable:
chmod +x consolconfig
scp consolconfig root@proxmox_ip

Then can you login at the proxmox-host and start the file with
./consolconfig

If that dont work, you can try to add another user with sudo-rights with the same procedure.

Udo

Nothing to do, with your trick (thank you) I used scp to transfer many config files and the dpkg-reconfigure console-data didn't work as try many keyboard set and for sure is not about key set as the ascii code not work as I wrote...

With the files wrote in another linux box and passed into proxmox system I had been able to update & upgrade but the "d" problem still remain under login and outside login the key work perfectly under bios and everywhere even ssh on virtual machines on that server.

Try to add user it's a mess and quite boring to cannot use the "d" key (note that "D" key work!) and cannot even launch pwd command and the chmod files trick boring, too.

Then I will surrender and remain with the "vital" executable command files in the root home folder.
 
Re: After console login not work the "d" key

Nothing to do, with your trick (thank you) I used scp to transfer many config files and the dpkg-reconfigure console-data didn't work as try many keyboard set and for sure is not about key set as the ascii code not work as I wrote...

With the files wrote in another linux box and passed into proxmox system I had been able to update & upgrade but the "d" problem still remain under login and outside login the key work perfectly under bios and everywhere even ssh on virtual machines on that server.

Try to add user it's a mess and quite boring to cannot use the "d" key (note that "D" key work!) and cannot even launch pwd command and the chmod files trick boring, too.

Then I will surrender and remain with the "vital" executable command files in the root home folder.

Hi,
try if another user has the same problem:
create the file user_plus on a second linux-box with following content:
Code:
apt-get install sudo
useradd -d /home/support support
mkdir /home/support
chown support /home/support
echo "support:secretpw" | /usr/sbin/chpasswd
echo "support ALL=(ALL) ALL" >> /etc/sudoers
chmod +x user_plus
scp the file to the proxmoxhost and execute user_plus.
Then you can login with support ans secretpw to the host. Perhaps you can type then the "d" - and you can "sudo su".

Udo
 
If you can make "D" then you can make a workaround like this (to try to solfe the problem finaly otherwise) ;):

For example:

Code:
server01:~# `echo DF | tr [:upper:] [:lower:]`
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md0               9614052   7793040   1332644  86% /
tmpfs                   258456         0    258456   0% /lib/init/rw
udev                     10240        96     10144   1% /dev
tmpfs                   258456         0    258456   0% /dev/shm
/dev/md1              75798248  69545792   2402084  97% /vol1
/dev/md2             218690876 202888252   4693688  98% /vol2
server01:~#
server01:~#
server01:~#
or

Code:
server01:~# `echo CHMOD 755 ./SOMESCRIPT.SH | tr [:upper:] [:lower:]`
or

Code:
server01:~# `echo DPKG-RECONFIGURE CONSOLE-DATA |  tr [:upper:] [:lower:]`


Greetings,
user100
 
Thank you Udo but the problem is persistant even with the new user:

Code:
support@mox:~$ suo su
can digit, but of course not work, this only :(

Code:
support@mox:~$ suDo su
-sh: suDo: command not found
 
If you can make "D" then you can make a workaround like this (to try to solfe the problem finaly otherwise) ;):

For example:

Code:
server01:~# `echo DF | tr [:upper:] [:lower:]`
[CUT]
user100

Thank to user100 suggestion I will insert in bash rules that D=d just to be able to digit all the commands, yeah is not the final solution but a good idea to not format in the near future... :rolleyes:
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!