You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that due to some changes with Spaces in Mojave you cannot move your mouse from a remote machine to the local machine unless you are on the same space as when you moved your mouse to that machine. Here is my setup:
Here are steps to replicate the issue using the machine names from my setup:
Move the mouse from cascade to dopplebock.
Change the Space on dopplebock.
Attempt to move the mouse back to cascade.
I am currently running a locally compiled version of Teleport from the current head on GitHub.
The text was updated successfully, but these errors were encountered:
My current alternative workaround is using the binding key to return the mouse control from remote machine. This sometimes makes the cursor disappear for a while until some click or move.
I cannot replicate this issue on the latest release v1.2.2 while running macOS Big Sur.
I have experienced a similar issue in the past that I think was caused by connecting and disconnecting a display which then made teleport display my two screens as overlapped so that I could only go from one computer to the other but not back.
I cannot recreate this issue by switching spaces, however.
If this is still an issue, please update and provide more detail about reproduction. I'm not sure what about your setup might be causing this issue.
It appears that due to some changes with Spaces in Mojave you cannot move your mouse from a remote machine to the local machine unless you are on the same space as when you moved your mouse to that machine. Here is my setup:
Here are steps to replicate the issue using the machine names from my setup:
I am currently running a locally compiled version of Teleport from the current head on GitHub.
The text was updated successfully, but these errors were encountered: