VT420 SSH session recording has sometimes keyboard disabled

[marianolopezcortes]

Hello. While recording a SSH session, at login screen sometimes I can't type anything (keyboard icon is on disabled mode). I don't know which condition produces this behavior.
Event if the cursor blinking is visible I can't type anything.

Here is my log:

2024-06-24 09:21:17,374 DEBUG c.b.j.r.r.RTERecorder: Start recording
2024-06-24 09:21:17,374 DEBUG o.a.j.g.GuiPackage: Updating current node bzm - RTE Recorder
2024-06-24 09:21:17,375 DEBUG o.a.j.g.GuiPackage: Gui retrieved = com.blazemeter.jmeter.rte.recorder.RTERecorderGui[bzm - RTE Recorder,0,0,1457x573,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=javax.swing.border.EmptyBorder@4a184f4b,flags=9,maximumSize=,minimumSize=,preferredSize=]
2024-06-24 09:21:17,375 DEBUG o.a.j.g.AbstractJMeterGuiComponent: setting element to enabled: true
2024-06-24 09:21:17,375 DEBUG o.a.j.g.GuiPackage: Gui retrieved = com.blazemeter.jmeter.rte.sampler.gui.RTEConfigGui[bzm-RTE-config,0,0,1457x957,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=javax.swing.border.EmptyBorder@140fceee,flags=9,maximumSize=,minimumSize=,preferredSize=]
2024-06-24 09:21:17,375 DEBUG o.a.j.g.AbstractJMeterGuiComponent: setting element to enabled: true
2024-06-24 09:21:17,375 DEBUG o.a.j.g.GuiPackage: Gui retrieved = com.blazemeter.jmeter.rte.recorder.RTERecorderGui[bzm - RTE Recorder,0,0,1457x573,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=javax.swing.border.EmptyBorder@4a184f4b,flags=9,maximumSize=,minimumSize=,preferredSize=]
2024-06-24 09:21:17,376 DEBUG o.a.j.g.GuiPackage: Updating gui to new node
2024-06-24 09:21:19,737 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_PRESSED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)
2024-06-24 09:21:19,737 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_TYPED,keyCode=0,keyText=Unknown keyCode: 0x0,keyChar='a',keyLocation=KEY_LOCATION_UNKNOWN,rawCode=0,primaryLevelUnicode=0,scancode=0,extendedKeyCode=0x0] on Terminal)
2024-06-24 09:21:19,866 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_RELEASED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)
2024-06-24 09:21:19,986 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_PRESSED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)
2024-06-24 09:21:19,986 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_TYPED,keyCode=0,keyText=Unknown keyCode: 0x0,keyChar='a',keyLocation=KEY_LOCATION_UNKNOWN,rawCode=0,primaryLevelUnicode=0,scancode=0,extendedKeyCode=0x0] on Terminal)
2024-06-24 09:21:20,120 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_RELEASED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)
2024-06-24 09:21:20,208 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_PRESSED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)
2024-06-24 09:21:20,208 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_TYPED,keyCode=0,keyText=Unknown keyCode: 0x0,keyChar='a',keyLocation=KEY_LOCATION_UNKNOWN,rawCode=0,primaryLevelUnicode=0,scancode=0,extendedKeyCode=0x0] on Terminal)
2024-06-24 09:21:20,347 DEBUG c.b.j.r.r.e.CharacterBasedEmulator: Processing key: (java.awt.event.KeyEvent[KEY_RELEASED,keyCode=65,keyText=A,keyChar='a',keyLocation=KEY_LOCATION_STANDARD,rawCode=65,primaryLevelUnicode=97,scancode=30,extendedKeyCode=0x41] on Terminal)

Do you have any idea?

Thank you!! Great tool!!

[marianolopezcortes]

I noticed that you have to press TAB before login to unlock the keyboard.
But then my login is incorrect and I can't log in.

[Baraujo25]

Hello @marianolopezcortes,

Glad you like the tool!

We haven't faced this issue before. Mostly the VT420 recording uses the response as a signal to unlock the keyboard. Given the information you have provided I'll assume that you hadn't even interacted with the application when the issue ocurred.

In order to be able to replicate the issue I will encourage you to provide a TCP Dump of the recording you are trying to achieve.

Here you will find the instructions on how to do that. Please feel free to request guidance.

Bests