Middle click stopped working in the built-in terminal

[kyselejsyrecek]

Type: Bug

After the last update of VS Code or the one before it, the selected text in the built-in Bash terminal is no longer copied and pasted into the command prompt when clicked with the middle button.

Ubuntu 24.04.2 LTS

VS Code version: Code 1.98.1 (2fc07b8, 2025-03-10T15:38:08.854Z)
OS version: Linux x64 6.8.0-55-lowlatency snap
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 3499)
GPU Status	2d_canvas: unavailable_software canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: disabled_software multiple_raster_threads: enabled_on opengl: disabled_off rasterization: disabled_software raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: disabled_software video_encode: disabled_software vulkan: disabled_off webgl: unavailable_software webgl2: unavailable_software webgpu: disabled_off webnn: unavailable_software
Load (avg)	1, 1, 1
Memory (System)	30.96GB (16.36GB free)
Process Argv	--no-sandbox --force-user-env --crash-reporter-id 67ae3122-9d6f-450c-9e97-13d71cc24d09
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

Extensions (15)

Extension	Author (truncated)	Version
vscode-bad-code-highlighter	bha	0.1.6
shell-syntax	bma	1.0.5
overtype	DrM	0.5.0
todo-tree	Gru	0.0.226
linuxkerneldev	mic	0.6.1
vscode-language-pack-cs	MS-	1.98.2025031209
cpptools	ms-	1.19.8
cpptools-extension-pack	ms-	1.3.1
hexeditor	ms-	1.11.1
vscode-serial-monitor	ms-	0.13.1
incrementor	nms	1.0.3
command-variable	rio	1.67.0
memento-inputs	spa	1.0.0
debug	web	0.27.0
qf	Wsc	6.8.122

(1 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
f5992895:31259995
jda6j935:31233686
pythoneinst12cf:31257680
bgtreat:31257678
fh1c7952:31258891
6h6a5794:31257591
31787653:31256342
0339e702:31259951

[meganrogge]

what are your terminal settings?

does it reproduce in the Insiders build?
/label info-needed

[kyselejsyrecek]

Well, I can say that settings of the integrated terminal have not changed for about two years already. Not from my side at least. The setting you may be interested in the most is:

"terminal.integrated.middleClickBehavior": "default"

Of course, the second option (paste) does not work the way it had worked originally which is copying and pasting of a selected text. How should I export all terminal settings if that is what you need? Are you saying that the error is not reproducible?

In what concerns the Insider build, I am not able to help there. Sorry.

[meganrogge]

I cannot repro an issue, when I set that setting to paste and middle click , it works.

[kyselejsyrecek]

@meganrogge, excuse me, you are being too quick with your refusal. You have misunderstood what was the functionality that stopped working recently. It was clearly stated in the description that:

the selected text in the built-in Bash terminal is no longer copied and pasted into the command prompt when clicked with the middle button.

Also, as explained in my previous comment, my middle button settings are "terminal.integrated.middleClickBehavior": "default", not paste. These are two different values and functionalities!

[kyselejsyrecek]

I am attaching two screen recordings so that you can easily grasp how does the middle button work in the Terminal window in Ubuntu. It used to work this way in VS Code too, until it recently started doing what is recorded in the second video. Sorry for the brief flashes of the blue selection. It was selected for a longer period of time but it seems that the recording SW did not capture that properly.

https://github.com/user-attachments/assets/40f3d974-6e56-4718-8bdf-b9e11cfccf73
https://github.com/user-attachments/assets/b3588bfe-4d2d-467b-b037-654ca23d0c2e

[meganrogge]

Thanks for the recordings.

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 @vscode/vscode-bisect@latest
• follow the instructions until you found the offending build
• report back the commit range in this issue

Thanks!

/label info-needed