bashrc is stty -ctlecho so I do not get the ^C all the time (which otherwise prevents me from using copy/paste!) So it feels like that specific like does not get executed since I see the ^D when typing the Ctrl- d key in the console. Ctrl-V was recognised as was all other dual key combinations. The Control key was recognised, the C key was recognised but the combination Ctrl-C was not. I downloaded the Passmark Keyboard Test app to help diagnose the problem. Start by restarting everything: Computer(s), Printer, Router - switch off any. My Ctrl-C combination stopped working today on all applications other than CMD Prompt. The first time I hit that one, I get a ^D in the console and it does not get killed.Īs a side note, one thing that I do in my. If this is still an issue: The problem may just be a communication glitch. That terminal window gets opened automatically whenever I open my X session.Īnother thing that does not work either is Ctrl- d. At the same time, if I close that tab and reopen a new one, that new one works as expected. In this video, you will learn the solution of keyboard control keys which are not working. Some other software is intercepting Ctrl+Shift+P. That leaves three main possibilities: There is a bug in the operating system or keyboard driver.
Since it works in the other 5 tabs, my idea would be that's because it is the last tab. Given the additional information (in a comment) that Firefox also cannot see Ctrl+Shift+P, it seems clear that the problem does not lie with VSCode itself. That one loses the Esc- p / Alt- P functionality. Somehow, when I start my X session in Ubuntu 16.04, I get a Gnome Terminal window with 6 tabs and they all works as expected except for the last tab.
