Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Terminal: Loss of Mouse Interactivity (PowerToys) #6120

Closed
hectormz opened this issue May 21, 2020 · 38 comments
Closed

Windows Terminal: Loss of Mouse Interactivity (PowerToys) #6120

hectormz opened this issue May 21, 2020 · 38 comments
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-1 A description (P1) Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@hectormz
Copy link

Environment

Windows build number: [Version 10.0.19041.264]
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?

Steps to reproduce

This seems to happen when I leave Windows Terminal running long enough. I haven't been able to nail down the exact situation that leads to it happening. I started noticing this recently, which may be due to a new problem, or just more use of Windows Terminal.

I'm certain that leading up to the unresponsiveness, my machine has been locked and/or asleep at some point. But I have put my computer asleep, or locked it without reproducing the problem.

Expected behavior

Normal mouse interactivity.

Actual behavior

At least once a day now, my Windows Terminal become unresponsive to mouse interactions. This includes selecting text, pasting text with right click, clicking tabs and dropdown menu, minimize/maximizing the window etc. The only mouse interaction that works is grabbing the title bar and moving the window.

I am seeing this behavior with Windows Terminal, but I have a feeling it might be UWP related. I don't (knowingly) use many UWPs, but when the Windows Terminal is like this, I've tested the Microsoft Store application as well. I'm able to minimize/maximize Microsoft Store, but cannot drag it around via the title bar. When Windows Terminal is behaving properly, the Microsoft Store is fine.

When Windows Terminal has been misbehaving, I've opened Windows Terminal (Preview), and it was acting similarly unresponsive.

This issue is not resolved by closing and reopening Windows Terminal. I have to restart my computer to fix it.

If I can provide any more info, or narrow down what leads to this happening, I'll report back.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 21, 2020
@DHowett
Copy link
Member

DHowett commented May 22, 2020

Do you have PowerToys installed?

@DHowett DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 22, 2020
@DHowett
Copy link
Member

DHowett commented May 22, 2020

(This could be a XAML platform bug -- that's the only thing in common between that set of applications. Hmm.)

@hectormz
Copy link
Author

@DHowett Yes, I updated to PowerToys v0.18.0 this week. Before that, I was several versions behind (v0.13.0).

Do you think that's involved? Would closing PowerToys when this issue happens fix it?

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 22, 2020
@DHowett
Copy link
Member

DHowett commented May 22, 2020

It's worth a shot!

@hectormz
Copy link
Author

I'll report back.

You made me wonder if this could be caused by FancyZones use, but that didn't cause any issues yet.

@DHowett DHowett added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels May 22, 2020
@softwarenerd
Copy link

softwarenerd commented May 22, 2020

I am experiencing this, too. It's random and happens when Windows Terminal has been running for a little while. I always have two Windows PoweShell tabs open There are no steps to reproduce this other than to start Windows Terminal and open two Windows PoweShell tabs.

Windows Terminal
Version: 1.0.1401.0

@Domain
Copy link

Domain commented May 22, 2020

I have the same issue. And when I exit PowerToys, it works fine now.

@zadjii-msft
Copy link
Member

@softwarenerd do you have powertoys installed as well?

@crutkas We're still seeing some intermittent mouse issues with the Terminal and PowerToys, even on updated versions of PowerToys, anything we can do to get logging from these users to debug?

@softwarenerd
Copy link

softwarenerd commented May 22, 2020

@crutkas I don't have PowerToys installed.

@hectormz
Copy link
Author

hectormz commented May 23, 2020

@zadjii-msft @crutkas @DHowett

This morning I lost mouse function again.

Closing PowerToys did the trick. I closed it and all was fine again. I opened PowerToys again and it's still fine.

I also updated to v.0.18.1 some time before this happened.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 23, 2020
@crutkas
Copy link
Member

crutkas commented May 23, 2020

@hectormz. Did you drag the window with fancyzones at any time before?

@hectormz
Copy link
Author

@crutkas I did drag other windows into FancyZones last night, but not Terminal.

Last night everything was okay, and computer was asleep over night. Some time after waking the computer today and doing work, I noticed Terminal not responding again.

@muzzar78
Copy link

I have experienced the same issue and it occurred when I unlocked my laptop from sleep. I had two tabs open and I don't have powertoys installed. If I right click close from the taskbar, I get close tabs dialogue but it is unresponsive too. This has happened several times over the last month (both prior to v1 and now on v1).

image

Killing the windowsterminal process and relaunching resolves the issue.

@crutkas
Copy link
Member

crutkas commented May 25, 2020

@muzzar78 do you have PowerToys installed?

@muzzar78
Copy link

@muzzar78 do you have PowerToys installed?

No, I don't.

@SergioMorchon
Copy link

I also don't have Power Toys installed, and experience the same issue.
Also to close it, even if I right-click on the task bar icon with the mouse, anc select "Close", the terminal shows the dialog (that warns about having multiple tabs that will be closed) but if I click over the dialog buttons, it just do nothing.
I have to close it from the Windows task manager

@ihor-sviziev
Copy link

I also getting issue with dialog on Ubuntu 20.04 WSL2 with following command:

HEIGHT=0
WIDTH=0
dialog \
    --backtitle "System Information" \
    --title "Menu" \
    --clear \
    --cancel-label "Exit" \
    --menu "Please select:" $HEIGHT $WIDTH 4 \
    "1" "Display System Information" \
    "2" "Display Disk Space" \
    "3" "Display Home Space Utilization"

It just stops reacting on mouse clicks just after few clicks to different options. Also I hadn't this issue on Terminal Preview versions.
Windows Terminal Version: 1.0.1401.0
Windows Version 2004 (OS Build 19041.264)

@arntj
Copy link

arntj commented May 27, 2020

I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears.

I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification:
image

@transiient
Copy link

I have the same issue. Exiting PowerToys restores functionality - Terminal doesn't even need to be restarted after PowerToys is exited.

@leandrowilliam
Copy link

I have the same issue... But when I close PowerToys it run good again without restarting the Terminal. The issued started with the v0.18.1 of powerToys, that ask to intall/update the netFramework too

@crutkas
Copy link
Member

crutkas commented May 28, 2020

I'm having the same issue. When it happens, it persists when I close and re-open Terminal. But if I shut down Powertools, then it disappears.

I also noticed that if I run Terminal as administrator while PowerTools is running then I get this notification:
image

If terminal is run as admin, we can't resize the terminal window since PT runs at a lower permission. This is PowerToys telling you 'hey, you're in a state odd stuff may happen'

@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 23, 2020
@zadjii-msft zadjii-msft removed the Needs-Attention The core contributors need to come back around and look at this ASAP. label Jun 23, 2020
@zadjii-msft zadjii-msft added this to the Terminal v2.0 milestone Jun 23, 2020
@zadjii-msft zadjii-msft changed the title Windows Terminal: Loss of Mouse Interactivity Windows Terminal: Loss of Mouse Interactivity (PowerToys) Jun 24, 2020
@zadjii-msft
Copy link
Member

zadjii-msft commented Jun 24, 2020

Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information:

  • Are you using the Terminal on a high DPI display?
    • If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal?
  • Similarly, are you using the Terminal on your primary display?
    • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?
  • Does the PowerToys settings app similarly not respond to mouse input?
  • Do you have the Shortcut Guide enabled in PowerToys?
    • If so, does it actually work if you long press Win?
  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful.

See also:

If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then

  • can you fix the issue by disabling "Shortcut Guide" in PowerToys?

@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 26, 2020
@hectormz
Copy link
Author

So, I just encountered this again (since you posted this @zadjii-msft ).
I normally am using my laptop which has a high DPI display, which is off, and is connected to a high DPI monitor. (Scaling is set to recommended 250%)

I was using my laptop without an external monitor and couldn't interact with Windows Terminal with mouse.

I opened the powertoys settings, but couldn't click anything. But I do have the shortcut guide enabled, and it did come up after holding Win key.

After this, I went back to PowerToys settings which were now working, and I went back to Windows Terminal which was also back to normal. Seemingly just from bringing up the shortcut guide.

I have not uninstalled any IME to my knowledge.

@masterashu
Copy link

I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app.

@crutkas
Copy link
Member

crutkas commented Jun 30, 2020

I had this same issue with Windows Terminal Version: 1.0.1401.0. I also experienced loss of mouse interactivity in the Twitter PWA Store app.

Do you have PowerToys installed. If so what is enabled.

@masterashu
Copy link

Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run.

@crutkas
Copy link
Member

crutkas commented Jun 30, 2020

Yes Powertoys (v0.18.2) is installed. The enable features are: Image Resizer, Power Rename, and PowerToys Run.

But not shortcut guide or fancyzones? Interesting

@mike-loux-planview
Copy link

mike-loux-planview commented Jul 24, 2020

Just noticed this behavior for the first time this AM. Thank god for this thread or I'd be climbing the walls rn.

Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information:

  • Are you using the Terminal on a high DPI display?

Don't know - Samsung 27" curved 1080p gaming monitor.

  • If so, and if possible, does dragging the window to a 100% scaling display magically restore mouse functionality to the Terminal?

Dragging it to an identical, non-primary display does restore functionality.

  • Similarly, are you using the Terminal on your primary display?

It's considered display #2 by the system (LT screen is #1), but it IS my main display.

  • If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?

It does indeed.

  • Does the PowerToys settings app similarly not respond to mouse input?

Yup. It sure doesn't.

  • Do you have the Shortcut Guide enabled in PowerToys?

Yup.

  • If so, does it actually work if you long press Win?

Not sure - I typically only have the shortcut keys pop up by accident. Did not try it this AM.

  • By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

No.

I just hit this yesterday, and although we don't have exact repro steps yet, we're trying to figure out anything that could be useful.

See also:

If you're experiencing this, and you can interact with the PowerToys settings app (you might need to drag it to another monitor), then

  • can you fix the issue by disabling "Shortcut Guide" in PowerToys?

Yup. That did the trick. I use Mouse in Windows Terminal for selecting text in PS several hundred times a day, so this is a good workaround for me. Thank you!

@matteocontrini
Copy link

Just happened to me.

Are you using the Terminal on a high DPI display?

No, but the resolution is 2560x1080

Similarly, are you using the Terminal on your primary display?

Yes

If so, and if possible, does dragging the window to another display magically restore mouse functionality to the Terminal?

I can't test unfortunately

Does the PowerToys settings app similarly not respond to mouse input?

Yes, it doesn't respond to mouse input

Do you have the Shortcut Guide enabled in PowerToys?

Yes

If so, does it actually work if you long press Win?

No, it doesn't

By any chance, did you recently uninstall any sort of IME (like a Chinese/Japanese/Korean language IME)?

No

@zadjii-msft
Copy link
Member

Oh my goodness, would you look at that. There's also #3325 which is another (much older) thread about this exact same issue. Maybe we should close this thread and link the two up?

@vlovich
Copy link

vlovich commented Nov 14, 2020

For me, dragging to a second monitor fixes it but it's still broken on the primary monitor when I drag it back. Turning off the powertoys shortcut guide re-enabled mouse again for me in the broken terminal.

@zadjii-msft
Copy link
Member

zadjii-msft commented Jan 29, 2021

You know what, I'm just gonna close this in favor of /dup #3325, to try and keep the discussion in one place. Thanks!

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Jan 29, 2021
@zadjii-msft zadjii-msft removed this from the Terminal v2.0 milestone Jan 29, 2021
@ghost
Copy link

ghost commented Jan 29, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Tag-Fix Doesn't match tag requirements labels Jan 29, 2021
@julie777
Copy link

julie777 commented Oct 8, 2022

I just discovered the same issue. I am running fancy zones. If I use the windows key shortcut to move the terminal to a different location the mouse works. If I use the shortcut to move it back the mouse stops working.

@endrelovas
Copy link

Did anyone got a resolution to this? I do not have Powertoys installed. Never had. Killing the process won't help. Dragging to another screen won't help. No high res. Nothing fancy here except for oh-my-posh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Input Related to input processing (key presses, mouse, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-1 A description (P1) Product-Terminal The new Windows Terminal. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests