Open tolgraven opened 8 years ago
dmitshur
commented
8 years ago This has happened to me a few times too, but it's not very frequent.
It usually happens when there's wi-fi connectivity trouble or something unusual along those lines.
When it does happen, it is very problematic because I can't even shutdown teleport in that case.
tolgraven
commented
8 years ago If you don't have physical input access to the other computer you can always just ssh in from your phone though. Not very convenient but a lot better than having to reboot :)
abyssoft
commented
8 years ago Yeah happens to me about once a week, and I agree it's annoying.
lvl99
commented
8 years ago I just had this happen to me as the screensaver kicks in when I spend too much time on the slave, then it zings me back to the master to log in to get out of the screensaver.
Usually I can type in password and go back from master to slave and resume work, but this time I've lost control of master (although I can move mouse on screen, just can't click or type in anything on keyboard either).
Is there some kind of hot corner or "abort, abort!" kind of gesture I could set up to get the master to get back control of its keyboard? This is the first and only time this has happened to me, and I've been using Teleport off and on since 2012.
radj
commented
7 years ago @lvl99 On a Mac, you can press CTRL+ALT+SHIFT+ESC to go back to master.
Back on topic, how do you prevent the master from going into screensaver? It is a little inconvenient to have to go back to master to get out of screensaver before I can continue working on slave again.
johndbritton
commented
3 years ago I've released a new version of Teleport, v1.2.2. It's working well for me on macOS Big Sur.
I haven't had this happen to me, but leaving this open for a bit to see if anyone can provide steps to reproduce.
I also created https://github.com/abyssoft/teleport/issues/58 as a separate issue to provide some sort of solution to keeping the machines awake.
Sometimes while network is unreliable teleport seemingly hands off control from the main machine to the other, seemingly not realising it doesn't arrive. And since it never arrives it also doesn't come back, only fix seems to be to ssh back in from the other machine and pkill teleport. Seems to happens rather frequently for me, although mostly in the form of smaller hickups where the machines eventually manage to communicate and the pointer can be brought back.
Very serious issue in my opinion, but seemingly not very common? Probably has to do with my network issues, but either way it's a very large design flaw in my opinion - it really ought to bail and return control if packets aren't coming through... I take it teleport is not under very active development so I might try to look into it if I manage to get some spare time.