Ctrl + Space not working

[FabioReact]

Type: Bug

Hello,

Default mapping Ctrl+I works to show autocompletion but Ctrl+Space doesn't. I tried on VSCode to binding again to Ctrl+Space but it doesn't get the combination.
I put it back to default and it didn't work either. Even on basic HTML, Ctrl+Space doesn't work (again, Ctrl+I works without troubles).

VS Code version: Code 1.78.2 (b3e4e68, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (6 x 3696)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	31.85GB (19.02GB free)
Process Argv	--crash-reporter-id 459edf77-c5da-48ec-98c6-b406dcbca1d4
Screen Reader	no
VM	0%

Extensions (18)

Extension	Author (truncated)	Version
better-comments	aar	3.0.2
vscode-tailwindcss	bra	0.9.11
vscode-eslint	dba	2.4.0
githistory	don	0.6.20
es7-react-js-snippets	dsz	4.4.3
prettier-vscode	esb	9.12.0
rest-client	hum	0.25.1
vscode-env	Iro	0.1.0
vsliveshare	ms-	1.0.5864
vsliveshare-pack	ms-	0.4.0
reload	nat	0.0.6
material-icon-theme	PKi	4.27.0
prisma	Pri	4.14.1
vs-code-prettier-eslint	rve	5.1.0
autoimport	ste	1.5.4
quokka-vscode	Wal	1.0.541
vscode-import-cost	wix	3.3.0
material-theme	zhu	3.15.13

(3 theme extensions excluded)

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
pythonfmttext:30731395
fixhidewlkth:30730051
pythongtdpath:30739704

[gjsjohnmurray]

/confirmPlease

[vscodenpa]

Thanks for creating this issue! To help narrow it down, please take the time to follow below steps. Thanks a lot and happy coding 🙏

Is the issue caused by an Extension?

Stop VS Code and from the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If it still reproduces, jump to the next chapter.

If you see it is an issue with the extension, please run the command Start Extension Bisect and follow the instructions to find the extension that is causing this issue.

Please report the issue to the extension causing this.

Is the issue caused by VS Code Core?

If the issue is not caused by an extension, it is maybe caused by your configuration. Try to run code --disable-extensions --user-data-dir <directory> where <directory> is an empty folder. This will ensure Code is starting with a fresh data directory, e.g. no specific settings and without any extensions running.

If it still reproduces, it was maybe fixed already in our nightly release. Please download from https://code.visualstudio.com/insiders/ and see if you can reproduce the issue.

Finally, to help us narrow down what change caused the issue, please run the following command to find the build. It will start previous releases of VS Code insiders to see where the regression was introduced:

• npx --yes vscode-bisect@latest
• follow the instructions until you found the offending build
• report back the commit range in this issue

Thanks!

[chronos1970]

I can confirm this issue appeared right after updating vs code. Disabling extensions doesn't fix it.

[gjsjohnmurray]

Please use the advice at https://github.com/microsoft/vscode/wiki/Keybinding-Issues to gather more information.

[chronos1970]

After activating Developer: Toggle Keyboard Shortcuts Troubleshooting and pressing ctrl + space

2023-05-24 11:33:37.429 [info] [KeybindingService]: / Soft dispatching keyboard event
2023-05-24 11:33:37.480 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2023-05-24 11:33:37.481 [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control
2023-05-24 11:33:37.481 [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl')
2023-05-24 11:33:37.481 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2023-05-24 11:33:37.821 [info] [KeybindingService]: + Ignoring single modifier ctrl due to it being pressed together with other keys.

Additionally, when going to Preferences: Open Keyboard Shortcuts and pressing the Record Keys button ctrl + space the input only registers ctrl.
Other shortcuts like ctrl + B work normally.

[chronos1970]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

[garvageart]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Can confirm this too. Updated my PowerToys last night and found the Ctrl+Space shortcut suddenly not working in the morning. You can just turn it off or change the shortcut

[AdrianSchmidt91]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Can confirm this too. Updated my PowerToys last night and found the Ctrl+Space shortcut suddenly not working in the morning. You can just turn it off or change the shortcut

Originally posted by @garvageart in #183278 (comment)

I can confirm this, turning it off made the suggestions in vs code work again.

[pipecosme123]

I am happy to confirm that you have identified an issue related to updating Power Tools in Windows 11. After disabling the "Peek" functionality, everything is working fine again in VS Code.

[FJanza]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

YOU SAVE MY LIFE, I AM COMPLETELY GRATEFUL TO YOU!!

[victorssr]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Omg, i would never think that. Thanks a lot.

[Selimfigenkaplan]

I wouldn't have thought it was due to powertoys. Thank guys. :)

[lindstrm]

Thank you! 👏

[idirmosh]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Thanks! This was my case too. after uninstalling Power Toys ctrl +space is functioning in my vscode again

[victorssr]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Thanks! This was my case too. after uninstalling Power Toys ctrl +space is functioning in my vscode again

Hi!

If you want, you dont need to uninstall it. You can just disable the peek feature and it returns to work again.

[antpowell]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Thank you! This solved my problem too. you rock! 🚀

[primado]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Can confirm this too. Updated my PowerToys last night and found the Ctrl+Space shortcut suddenly not working in the morning. You can just turn it off or change the shortcut

Originally posted by @garvageart in #183278 (comment)

I can confirm this, turning it off made the suggestions in vs code work again.

Thank you, I was experiencing this issue with VS Code, I have disabled Peek, and it's now working.

[StianWiu]

Yep, had the same problem. I now need to remember to toggle that off every time I reset my pc...

[DevScholar]

In the Simplified Chinese version of Windows, the Ctrl+Space shortcut key does not work by default because it is occupied by the Microsoft Pinyin input method.

[kurogai]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

LMAO, same here, had to deactivate

[DoisKoh]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Piling on more thanks.

[TiagoSilvaPereira]

Just to register: updating PowerToys to 0.70.1 solves the problem without the need to disable Peek

[ouhzee]

I realized the issue was caused by the latest Power Toys version (v0.70.0). ctrl +space is bound by default to the new Peek widget.

Wow, thank you so much I didn't realize PowerToys causing vscode Intellisense shortcut not working.
I tried using PowerToys v0.70.0 it needs to turn Peek feature off. When updating to v0.70.1 we don't need to turn it off