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

Monitor doesn't turn on when moving control to Apple Silicon Mac #59

Open
francosolerio opened this issue Dec 6, 2020 · 6 comments
Open
Labels
bug-report Unverified bug report

Comments

@francosolerio
Copy link

Main Mac is an Intel MacBook Pro running Catalina.
Controlled Mac is a MacMini with M1 running Big Sur.

Controlled Mac had the display turned off by energy saving features, but is not in standby ("Prevent computer from sleeping automatically when the display is off" is checked in system preferences).

When trying got move control from the main Mac the controlled Mac the monitor doesn't turn back on.
Additionally the transparent HUD appears on the main Mac's display, but it's not possible to move the mouse pointer back to the main Mac, so everything is stuck. The only way to unlock and return control to the user is pressing the power button on the controlled Mac, or connecting to the controlled Mac from a third device via screen sharing. This makes the display turn on and makes Teleport resume activity.

When the controlled Mac is an Intel MacMini running Catalina with the same settings, the display turns on as soon as I try to move control from the main Mac to the controlled Mac.

Teleport version: 1.2.2 (built from commit 1792137)

@francosolerio francosolerio added the bug-report Unverified bug report label Dec 6, 2020
@johndbritton
Copy link
Owner

Thanks for the detailed report.

Are you able to reproduce the issue on an intel Mac with Big Sur? Trying to determine if it's just an OS issue or related to running under Rosetta.

@francosolerio
Copy link
Author

I'm sorry I have no Intel Mac with Big Sur available at this time.

@tomads
Copy link

tomads commented Dec 9, 2020 via email

@okdt
Copy link

okdt commented Dec 11, 2020

No troubles between Catalina/Intel and Big Sur/M1.
big thanks.

@reaperhulk
Copy link
Contributor

I can replicate this issue (although I'm Big Sur x86_64 -> Big Sur arm64) with a copy of teleport built natively for arm64 (using #61) so it doesn't appear to be an arch issue.

@johndbritton
Copy link
Owner

I can replicate this issue (although I'm Big Sur x86_64 -> Big Sur arm64) with a copy of teleport built natively for arm64 (using #61) so it doesn't appear to be an arch issue.

Thanks for reporting and also for the PR.

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

Successfully merging a pull request may close this issue.

5 participants