-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Comments
Do you have PowerToys installed? |
(This could be a XAML platform bug -- that's the only thing in common between that set of applications. Hmm.) |
@DHowett Yes, I updated to PowerToys Do you think that's involved? Would closing PowerToys when this issue happens fix it? |
It's worth a shot! |
I'll report back. You made me wonder if this could be caused by FancyZones use, but that didn't cause any issues yet. |
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 |
I have the same issue. And when I exit PowerToys, it works fine now. |
@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? |
@crutkas I don't have PowerToys installed. |
@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. |
@hectormz. Did you drag the window with fancyzones at any time before? |
@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. |
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). Killing the windowsterminal process and relaunching resolves the issue. |
@muzzar78 do you have PowerToys installed? |
No, I don't. |
I also don't have Power Toys installed, and experience the same issue. |
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. |
I have the same issue. Exiting PowerToys restores functionality - Terminal doesn't even need to be restarted after PowerToys is exited. |
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 |
Hey all, just a follow up on this thread - if you're hitting this, could you try providing any of the following information:
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
|
So, I just encountered this again (since you posted this @zadjii-msft ). 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 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. |
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. |
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 |
Just noticed this behavior for the first time this AM. Thank god for this thread or I'd be climbing the walls rn.
Don't know - Samsung 27" curved 1080p gaming monitor.
Dragging it to an identical, non-primary display does restore functionality.
It's considered display #2 by the system (LT screen is #1), but it IS my main display.
It does indeed.
Yup. It sure doesn't.
Yup.
Not sure - I typically only have the shortcut keys pop up by accident. Did not try it this AM.
No.
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! |
Just happened to me.
No, but the resolution is 2560x1080
Yes
I can't test unfortunately
Yes, it doesn't respond to mouse input
Yes
No, it doesn't
No |
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? |
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. |
You know what, I'm just gonna close this in favor of /dup #3325, to try and keep the discussion in one place. Thanks! |
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! |
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. |
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. |
Environment
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.
The text was updated successfully, but these errors were encountered: