starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Null key and g spontaneously sent when headphones are connected #680

New Issue
Closed
opened 2026-01-30 21:59:20 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 21:59:20 +00:00
Owner
Copy Link

Originally created by @odedp on GitHub (May 7, 2019).

  • Your Windows build number: Microsoft Windows [Version 10.0.17763.475]

  • What you're doing and what's happening: I installed WSL and Ubuntu 18.04 from Microsoft store. When I use the terminal, sometimes things seem very strange. I eventually traced it to null keys being spontaneously sent. If I just open the Ubuntu shell and run showkey -a, it seems that every second or two a null key is sent. After a few seconds I get:

<user>@<hostname>:~$ showkey -a

Press any keys - Ctrl-D will terminate this program

^@        0 0000 0x00
^@        0 0000 0x00
^@        0 0000 0x00
^@        0 0000 0x00
^@        0 0000 0x00

Moreover, when I run an X server (I use VcXsrv) it seems the spontaneous keys are g and not the null key. If I open xterm and then run showkey -a, after a few seconds I get this:

<user>@<hostname>:~$ showkey -a

Press any keys - Ctrl-D will terminate this program

g       103 0147 0x67
g       103 0147 0x67
g       103 0147 0x67
g       103 0147 0x67
g       103 0147 0x67

This seems somewhat similar to #215, but I am not pressing any key (i.e., not the shift key), and I also do not have a touch keyboard. I'm running on a ThinkPad X1 Carbon 6th laptop. It does not have a touch screen.

  • What's wrong / what should be happening instead: See above.
Originally created by @odedp on GitHub (May 7, 2019). * Your Windows build number: Microsoft Windows [Version 10.0.17763.475] * What you're doing and what's happening: I installed WSL and Ubuntu 18.04 from Microsoft store. When I use the terminal, sometimes things seem very strange. I eventually traced it to null keys being spontaneously sent. If I just open the Ubuntu shell and run `showkey -a`, it seems that every second or two a null key is sent. After a few seconds I get: ``` <user>@<hostname>:~$ showkey -a Press any keys - Ctrl-D will terminate this program ^@ 0 0000 0x00 ^@ 0 0000 0x00 ^@ 0 0000 0x00 ^@ 0 0000 0x00 ^@ 0 0000 0x00 ``` Moreover, when I run an X server (I use VcXsrv) it seems the spontaneous keys are `g` and not the null key. If I open `xterm` and then run `showkey -a`, after a few seconds I get this: ``` <user>@<hostname>:~$ showkey -a Press any keys - Ctrl-D will terminate this program g 103 0147 0x67 g 103 0147 0x67 g 103 0147 0x67 g 103 0147 0x67 g 103 0147 0x67 ``` This seems somewhat similar to #215, but I am not pressing any key (i.e., not the shift key), and I also do not have a touch keyboard. I'm running on a ThinkPad X1 Carbon 6th laptop. It does not have a touch screen. * What's wrong / what should be happening instead: See above.
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@odedp commented on GitHub (May 7, 2019):

After further experimentation, it seems that the issue only arises if the headphones are connected. I tried this with two different sets of wired headphones (connected to the 3.5mm jack), and also with Bluetooth headphones, and it happened in all three cases. With the headphones --- null key every second or two, without headphones --- no null keys for a few minutes.

@odedp commented on GitHub (May 7, 2019): After further experimentation, it seems that the issue only arises if the headphones are connected. I tried this with two different sets of wired headphones (connected to the 3.5mm jack), and also with Bluetooth headphones, and it happened in all three cases. With the headphones --- null key every second or two, without headphones --- no null keys for a few minutes.
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 7, 2019):

Well this is totally insane. I've never seen a set of headphones that'll spontaneously send keystrokes like that.

Unfortunately I don't really have a way of repro'ing this, so I'm not sure there's much else we can do.

Perhaps you could build openconsole.exe from source (now that we're opensource) and get a debugger attached to it. all the keystrokes go through HandleGenericKeyEvent, so maybe that would help.

@zadjii-msft commented on GitHub (May 7, 2019): Well this is totally insane. I've never seen a set of headphones that'll spontaneously send keystrokes like that. Unfortunately I don't really have a way of repro'ing this, so I'm not sure there's much else we can do. Perhaps you could build openconsole.exe from source (now that we're opensource) and get a debugger attached to it. all the keystrokes go through `HandleGenericKeyEvent`, so maybe that would help.
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@odedp commented on GitHub (May 7, 2019):

I'm happy to try, could you send me a pointer to instructions on how to do that?

It's really weird. But it happened with 3 different types of headphones (both wired and Bluetooth), so it may be something more systematic.

@odedp commented on GitHub (May 7, 2019): I'm happy to try, could you send me a pointer to instructions on how to do that? It's really weird. But it happened with 3 different types of headphones (both wired and Bluetooth), so it may be something more systematic.
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 8, 2019):

Sure, there's an enormous amount of resources in #489.

Basically, clone the repo, make sure to init git submodules, then open it up in VS. The project that builds openconsole.exe is Host.EXE, so if you launch that from VS, you'll have an openconsole (conhost) with a debugger attached.

@zadjii-msft commented on GitHub (May 8, 2019): Sure, there's an enormous amount of resources in #489. Basically, clone the repo, make sure to init git submodules, then open it up in VS. The project that builds openconsole.exe is `Host.EXE`, so if you launch that from VS, you'll have an openconsole (conhost) with a debugger attached.
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@martinmasse commented on GitHub (Jul 29, 2019):

I was searching for a solution to this problem and found this issue.

This is not related to Microsoft Terminal.

I also have a Thinkpad Carbon X1 6th Gen and this problem is present in all apps when connected to a RDP session. I open notepad or VS and the letter 'g' is added every few seconds.

Very annoying

@martinmasse commented on GitHub (Jul 29, 2019): I was searching for a solution to this problem and found this issue. This is not related to Microsoft Terminal. I also have a Thinkpad Carbon X1 6th Gen and this problem is present in all apps when connected to a RDP session. I open notepad or VS and the letter 'g' is added every few seconds. Very annoying
claunia commented 2026-01-30 21:59:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 22, 2021):

@odedp Is this still happening for you? If it is, could you try getting a debug tap trace of this happening? Might help identify the keys they're sending.

I also have a Thinkpad Carbon X1 6th Gen and this problem is present in all apps when connected to a RDP session. I open notepad or VS and the letter 'g' is added every few seconds.

That's certainly a helpful data point here, for what is a wild bug report 😄

@zadjii-msft commented on GitHub (Nov 22, 2021): @odedp Is this still happening for you? If it is, could you try getting a [debug tap trace](https://github.com/microsoft/terminal/wiki/Enabling-the-debug-tap) of this happening? Might help identify the keys they're sending. > I also have a Thinkpad Carbon X1 6th Gen and this problem is present in all apps when connected to a RDP session. I open notepad or VS and the letter 'g' is added every few seconds. That's certainly a helpful data point here, for what is a _wild_ bug report 😄
claunia commented 2026-01-30 21:59:23 +00:00
Author
Owner
Copy Link

@odedp commented on GitHub (Nov 22, 2021):

I haven't encountered this in a while (at least 6 months), so I assumed some update fixed it

@odedp commented on GitHub (Nov 22, 2021): I haven't encountered this in a while (at least 6 months), so I assumed some update fixed it
claunia commented 2026-01-30 21:59:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 22, 2021):

Well, that's good to hear! Thanks for confirming!

@zadjii-msft commented on GitHub (Nov 22, 2021): Well, that's good to hear! Thanks for confirming!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Input Issue-Bug Needs-Attention Needs-Repro Needs-Tag-Fix Product-Conhost Resolution-No-Repro
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#680
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?