-
Notifications
You must be signed in to change notification settings - Fork 93
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
Can't see desktop on multiple MacOS devices when "locked" #247
Comments
To anyone with this issue - I've managed to fix having the screen being black while locked by connecting to the Mac first via theTerminal in MeshCentral and running the command "caffeinate -u" It would be great if there was a way to have MeshAgent run the caffeinate command when it first connects, but automating that is currently beyond my skillset. |
@si458 I'm sure you are crazy busy with maintaining this project, but is this something that could be integrated into MeshAgent relatively easily? |
@pretenzo in theory meshagent already does this. When u connect we run the caffeine command to wake up the screen Also u can run |
Ah perfect! I believe my MeshCentral install is a few versions behind so I didn't realize that. Sorry to bother you! It's incredibly helpful to know you can do it from the console as well. Thank you for your help! |
@pretenzo refer to above post #247 (comment) |
@pretenzo, the only issue we haven't fixed yet is that u can't access the login screen when u first turn a Mac on! So u must have auto-login enabled so get it into the desktop, then when it sleeps later, u can still access the login screen :) |
MeshCentral: 1.1.24
One device is on MacOS 12.7.1, second device is on MacOS 14.5. When attempting to view the desktop of either device while it's on login/lock screen, the result is always a black screen and the input is not registered. Once logged in/unlocked the desktop shows up fine only after disconnecting and reconnecting and then input also works correctly.
Posting in both MeshCentral and MeshAgent as I'm not sure what is at fault here, feel free to close the one in the wrong category.
The text was updated successfully, but these errors were encountered: