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

Mojave: Cannot change screens after changing Spaces #44

Closed
stanger opened this issue Oct 23, 2018 · 4 comments
Closed

Mojave: Cannot change screens after changing Spaces #44

stanger opened this issue Oct 23, 2018 · 4 comments
Labels
bug-report Unverified bug report

Comments

@stanger
Copy link

stanger commented Oct 23, 2018

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:

screen shot 2018-10-23 at 9 11 37 am

Here are steps to replicate the issue using the machine names from my setup:

  1. Move the mouse from cascade to dopplebock.
  2. Change the Space on dopplebock.
  3. Attempt to move the mouse back to cascade.

I am currently running a locally compiled version of Teleport from the current head on GitHub.

@amouro
Copy link

amouro commented Nov 16, 2018

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.

@johndbritton
Copy link
Owner

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.

@johndbritton johndbritton added the bug-report Unverified bug report label Nov 19, 2020
@stanger
Copy link
Author

stanger commented Nov 19, 2020

This does appear to be be resolved. I'll close the ticket.

@stanger stanger closed this as completed Nov 19, 2020
@johndbritton
Copy link
Owner

Thanks for the report and for following up @stanger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-report Unverified bug report
Projects
None yet
Development

No branches or pull requests

3 participants