View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006676 | Kali Linux | Kali Package Improvement | public | 2020-08-24 15:15 | 2020-09-30 11:28 |
Reporter | wordeater | Assigned To | daniruiz | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | 2020.3 | ||||
Summary | 0006676: /etc/skel/.zshrc missing bindkeys for numpad | ||||
Description | The /etc/skel/.zshrc file is missing some bindings that would allow the numpad and the home and end keys to work properly.
| ||||
Steps To Reproduce | Have an older version of Kali Linux such as 2020.2.Follow the quick upgrade instructions.
| ||||
Additional Information | I am SSHing into my Kali VM using SecureCRT. This particular VM has been running the 'rolling' distribution for about a year and has nightly updates run with 'cron-apt'. I also have Kali on WSL2 on my personal laptop which I will try when I am off work later today. | ||||
Attached Files | |||||
I'm attaching screenshots of the possibly relevant SecureCRT terminal emulation settings. |
|
I tried to recreate the issue on my WSL2 install of Kali last night and I was not able to. I also tested on the first system again using the VMware remote console instead of SecureCRT over SSH. Even without the bindings present in the .zshrc file, the numpad keys work. The only time I have problems is when I SSH into the VMware Kali linux system. I tried KiTTY and was able to reproduce the problem I had with SecureCRT. |
|
I don't know why you're having this issue with the numpad, but it is working perfectly for me. The keybindings that you are using are actually forcing the keys with the numlock enabled to behave as the numlock is disabled, which isn't correct. For example, if you have the numlock enabled, if you press the key '7' your terminal receives the code '7', so there's no need for a keybinding for it. If you have the numlock disabled, pressing the key '7' sends the code '^[OH', which is already binded by Maybe your issue is caused by the fact that you're SSHing to kali and the terminal you're using is not sending the codes properly |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2020-08-24 15:15 | wordeater | New Issue | |
2020-08-24 15:20 | wordeater | File Added: SecureCRT-TerminalSettings01.jpg | |
2020-08-24 15:20 | wordeater | File Added: secureCRT-TerminalSettings02.jpg | |
2020-08-24 15:20 | wordeater | File Added: secureCRT-TerminalSettings03.jpg | |
2020-08-24 15:20 | wordeater | Note Added: 0013315 | |
2020-08-25 14:46 | wordeater | Note Added: 0013319 | |
2020-09-02 12:31 | daniruiz | Note Added: 0013377 | |
2020-09-02 12:31 | daniruiz | Assigned To | => daniruiz |
2020-09-02 12:31 | daniruiz | Status | new => assigned |
2020-09-30 11:28 | daniruiz | Status | assigned => closed |
2020-09-30 11:28 | daniruiz | Resolution | open => won't fix |